Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
  • Jan 31 2019 19:00
    tfaron commented #5133
  • Jan 31 2019 07:28
    cnishina closed #5135
  • Jan 31 2019 07:28
    cnishina commented #5135
  • Jan 30 2019 16:23
    ThabisoGithub closed #5136
  • Jan 30 2019 16:23
    ThabisoGithub edited #5136
  • Jan 30 2019 16:23
    ThabisoGithub edited #5136
  • Jan 30 2019 16:21
    ThabisoGithub opened #5136
  • Jan 30 2019 16:18
    IgorSasovets commented #4177
  • Jan 30 2019 15:05
    andrewchan-clover commented #4177
  • Jan 30 2019 13:43
    IgorSasovets commented #5135
  • Jan 30 2019 12:37
    EnzDev edited #5125
  • Jan 30 2019 11:47
    akshaymondal opened #5135
  • Jan 29 2019 14:33
    uinest commented #4822
  • Jan 28 2019 21:38
    cnishina commented #5132
  • Jan 28 2019 21:37
    cnishina commented #5134
  • Jan 28 2019 21:37
    cnishina closed #5134
  • Jan 28 2019 21:36

    cnishina on selenium4

    chore(release): bumpb version t… (compare)

  • Jan 28 2019 11:30
    think4ideas opened #5134
  • Jan 28 2019 11:01
    toniedzwiedz commented #2735
  • Jan 28 2019 09:42
    azorrozua commented #4786
I read that using directConnect only works with Firefox and Chrome, and it will run against the local browser installation. And the selenium server it's like a Selenium Grid, is that information correct?
Konstantin Bläsi
is it possible to tell chrome to not use client certificates that are installed on the machine running the tests? I want it to behave as if they didn't exist

It`s been a while since the last update for 6.0 version and looks like repo is dead now with lots of open PRs((
I use protractor on several projects and really interested in migrating to 6.0, but unable to do it due to several issues. Few months ago I already submitted PR to fix several issues. It successfully was merged, but still, the new version has not been published yet.
Do you need help with the maintenance of this project, and in general, will it be supported in the future?

Hi guys, is there any new news?


I am facing one issue in protractor with angular 7(e2e). I am not able to open the app on IE.

I have version :-
protractor 5.4.2

webdriver-manager version is 12.1.7

steps to run our app on IE:-

  1. run webdriver-manager update --ie
    IEdriverserver.exe is 3.150.1 ,
    standalone service is 3.14.59 jar

    2 run webdriver-manager start --ie

    open the another terminal and run ng e2e

    the error was :-
    Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/
    i 「wdm」: Compiled successfully.
    [12:05:28] I/launcher - Running 1 instances of WebDriver
    [12:05:28] I/local - Starting selenium standalone server...
    [12:05:29] I/local - Selenium standalone server started at
    [12:05:29] E/launcher - Unable to create new service: InternetExplorerDriverService
    os.name: 'Windows 10', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_201'
    Driver info: driver.version: unknown
    [12:05:29] E/launcher - SessionNotCreatedError: Unable to create new service: InternetExplorerDriverService

can you help me why I am receiving this error and how I can fix this?

Hi all, is there anyone facing this error when running the tests on CI runner :
" (unknown error: DevToolsActivePort file doesn't exist)"
@konstantinblaesi maybe
exports.config = {
  capabilities: {
    acceptInsecureCerts: true

@yenilmez_gitlab https://stackoverflow.com/questions/50642308/webdriverexception-unknown-error-devtoolsactiveport-file-doesnt-exist-while-t

Try some of those answers. If I remember correctly, I think I actually fixed this by temporarily disabling my anti-virus software

@Juani-Canete , if you're using directConnect, then protractor will automatically start new browser instance for the tests. If you declared seleniumAddress, protractor will use existing driver session
@IgorSasovets Thanks for response that!
Gökhan Öner
Hi all, trying AWS DeviceFarm Browser Test. when calling from Selenium Java, I can start a session, but not from Protractor. What I realized is that Selenium Java sends W3C compatible request, like this:
  "desiredCapabilities": {
    "browserName": "chrome"
  "capabilities": {
    "firstMatch": [
        "browserName": "chrome"
is it possible to achieve same in Protractor 5.4.2 ??
the capabilities key is missing in the Protractor request
Hi All,
I want to validate css color change in my e2e using protractor. I can see the color is changed in DB, but it is not reflecting in the UI, I tried to clear the cache using browser.actions().keyDown(protractor.Key.CONTROL).sendKeys(protractor.Key.F5).perform(); but still it is not bringing up the changes. How can I achieve this?
Avik Hazra
is there any way to run protractor in two browser but different test cases (like thread type concept) . I m using protractor + cucumber
Another question if we run protractor test cases in diff break point what needs to be change in code (not in cong.js)
Vivek krishna Varma
Any idea how we can identify based on some simple criteria(element attr, some meta info etc that need to be generic ) the hosted/deployed/running web-app is made of using react.
By looking / inspect / analyze we can say that the application running based on react application partially or fully.
e.g. like every angular app is identified using ng-version attribute ?
Vivek krishna Varma
one way i found window.REACT_DEVTOOLS_APPEND_COMPONENT_STACK var . looks like this is available only in case of react apps is this the good criteria ?
Craig Nishina
Hi it's been a while since I logged into Gitter
Just wanted to say hi. I will have
Hi @cnishina :) As you're most likely aware - a lot of the questions I see lately are wondering about the future of protractor (maintainers, v6, jasmine3, etc). Any updates on your end? Or is there a good thread to follow? Thanks!!
Craig Nishina
Yup sorry I went on an airplane.
We also are trying to figure that out with the angular team.
We will keep everyone posted
Alright well I need to catch another flight soon. Happy testing.
IE browser is not working with protractor e2e
Bastien Michaux Bellomo
I get this error when compiling my TypeScript. I followed the repo's Typescript example, but to no avail. What is going wrong ?
node_modules/protractor/built/index.d.ts:5:10 - error TS2440: Import declaration conflicts with local declaration of 'PluginConfig'.

5 import { PluginConfig, ProtractorPlugin } from './plugins';

node_modules/protractor/built/index.d.ts:5:24 - error TS2440: Import declaration conflicts with local declaration of 'ProtractorPlugin'.

5 import { PluginConfig, ProtractorPlugin } from './plugins';
Hi guys, I don't know if anyone can help me, I want to run protractor against differents browser but I want to send the browser by command line, I can't find documentation or examples about that can you help me?
Bastien Michaux Bellomo
Regarding my previous post, this is caused by a breaking TypeScript change, fix your project by compiling TS using npx tsc and downgrading your TS version to ~3.6
Hi All, anyone able to point me at some documentation that works for a JS project that calls protractor and cucumber. We have been using allure but can't seem to get it top output to allure.

Hi @mourasman / @All , It would be very grateful if you help me in this

// Every test case structure

describe("Login Suite", () => {
beforeEach(async function () {

//browser instance initialization & application navigation is happening here


it('Test case name', async function () {
    try {

    // Include test steps        

    } catch (e) {
        browser.logger.info("Test SWM-2019065 failed with exception: " + e)
        expect(true).toBe(false, e)

afterEach(async function () {
    //await browser.restart();
//await browser.close();




//Programming language used is javascript (promises flow disabled) : using async await to disable the asynchronous nature of javascript

My evrery test case in test suite has strcuture like above. Now, How can i want every test case belonging to test suite to be run in a sequence following the trend like

  1. Opening of browser instance for a first test case & running the whole test case which is happening
  2. then closing the above instance of first test case irrespective of the failure/success run.
  3. Now opening the new browser instance for 2nd test case-->>running whole test case--->>closing the browser instance of this particular test case--->>
  4. Now opening the new browser instance for 3rd test case-->>running whole test case--->>closing the browser instance of this particular test case--->>

Is this advisable to run the test suite in this way ? If yes, then how should i manage with the commands like browser.close() or whatever your approach is. I have tried this but getting such errors like "AfterAll Failed: invalid session id" . Kindly provide your inputs.

Does anybody have knowledge about this ???????????????????????
Hi all setting up Protractor for first time with an AngularJS app
I get following StackTrace when running

E:\DemoApp>protractor test/protractor.conf.js

[16:36:25] I/launcher - Running 1 instances of WebDriver
[16:36:25] I/hosted - Using the selenium server at http://localhost:4444/wd/hub
[16:36:45] E/launcher - Timed out waiting for driver server to start.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'APC', ip: 'x.x.x.x', os.name: 'Windows Server 2016', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_231'
Driver info: driver.version: unknown
[16:36:45] E/launcher - WebDriverError: Timed out waiting for driver server to start.
Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53'
System info: host: 'APC', ip: 'x.x.x.x', os.name: 'Windows Server 2016', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_231'
Driver info: driver.version: unknown
at Object.checkLegacyResponse (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\error.js:546:15)
at parseHttpResponse (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
at C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\http.js:441:30
at processTicksAndRejections (internal/process/task_queues.js:93:5)
From: Task: WebDriver.createSession()
at Function.createSession (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\lib\webdriver.js:769:24)
at Function.createSession (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\chrome.js:761:15)
at createDriver (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:170:33)
at Builder.build (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\selenium-webdriver\index.js:626:16)
at Hosted.getNewDriver (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\built\driverProviders\driverProvider.js:53:33)
at Runner.createBrowser (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\built\runner.js:195:43)
at C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\built\runner.js:339:29
at _fulfilled (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:834:54)
at C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:863:30
at Promise.promise.promiseDispatch (C:\Users\btime\AppData\Roaming\npm\node_modules\protractor\node_modules\q\q.js:796:13)
[16:36:45] E/launcher - Process exited with error code 199

Not sure what issue is as I've ran webdriver-manager update and webdriver-manager start before running protractor command.
I'm starting to implementing e2e tests on a project and i'll be using protractor/jasmine (the setup that comes from the cli). Can someone share a project with a decent organization of the tests?
Brandon Gibbons
@nunofreitasbotelho I don't have any full examples of test structure, but there are some resources to help out on the website: http://www.protractortest.org/#/page-objects, http://www.protractortest.org/#/style-guide
Rick van der Meij
supports angular 8 and angular 9 RC11
Thank you both @GibbsB & @rickvandermey , i'll take a look on that

Hey guys, I have a problem with running my script. For some reason node_modules folder in my App Data folder is being targeted instead of the one in my project folder when using VS Code terminal. Also it keeps saying my chromedriver is outdated even though i updated it globally and locally.
Using Protractor with Jasmine


Any help would be appreciated

Brandon Gibbons
@Dzanan91 That error is a mismatch between the chromedriver (v74.0.3729.6) and the chrome browser, which are different things. Try to see which version your chrome browser is in Help -> About Google Chrome. If you have multiple versions of Chrome Browser in your project, you will have to target the right one to match your chromedriver. https://chromedriver.storage.googleapis.com/74.0.3729.6/notes.txt Your chromedriver version only supports Chrome Browser v74. The latest of chromedriver should 80.x.x.x, so you might not be getting the latest with your webdriver-manager update command.
I have latest version of chrome browser
And have installed latest chromedriver stable version ( 79 )
still for some reason doesnt read the latest chromedriver version
and returns error as shown in screenshot above
so weird
Brandon Gibbons
First thing I would do is remove that global install from that roaming/npm/node_modules directory. Chromedriver 79 definitely shouldn't be returning an error related to Chrome 74
okay let me try that