## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
• 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
Craig Nishina
@cnishina
Hi it's been a while since I logged into Gitter
Just wanted to say hi. I will have
Luke
@luker2
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
@cnishina
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.
bhavika
IE browser is not working with protractor e2e
Bastien Michaux Bellomo
@bmchx_gitlab
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';
~~~~~~~~~~~~~~~~
Trabu
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
@bmchx_gitlab
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
mort2007
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.
manpreets11
@manpreets11

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

//===================================================================================================
// Every test case structure

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();
or
//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.

manpreets11
@manpreets11
Bmoe
@bmoes-coderoom
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 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.
nunofreitasbotelho
@nunofreitasbotelho
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
@GibbsB
@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
@rickvandermey
supports angular 8 and angular 9 RC11
nunofreitasbotelho
@nunofreitasbotelho
Thank you both @GibbsB & @rickvandermey , i'll take a look on that
Dzanan91
@Dzanan91

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

https://d.pr/i/taX0zP

Any help would be appreciated

Brandon Gibbons
@GibbsB
@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.
Dzanan91
@Dzanan91
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
@GibbsB
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
Dzanan91
@Dzanan91
okay let me try that
Thanks
Aasim Anwar
@aasimali
Hi, Would like to know that, can we automate a PDF loaded in browser using Protractor?
hfsoares
@hfsoares
Hello guys, I need some debugging tips. I am using Angular 8, and Google Chrome 80.x.x.x.x
I have a test that logs in the system, by sendKeys for login and password, press a button, and then try to fill 2 more form fields, name and description also with sendKeys.
The script goes well until the last description field, when it freezes.
I have switched the order, filling description first, and the system freezes at the name. So, it seems that my finder is correctly designed.
I am using async and await pattern
Thomas
@selenium4466_gitlab
@hfsoares could you post snippet of code
hfsoares
@hfsoares
Sure
navBarGrupos = new NavBarGrupos();
await navBarGrupos.clickOnCrieNovoGrupo();
grupoUpdatePage = new GrupoUpdatePage();
grupoCabecalhoPage = new GrupoCabecalhoPage();
await grupoUpdatePage.setNomeInput('nome'),
await grupoUpdatePage.setDescricaoInput('descricao')
this is the test.spec (the names are in portuguese)
this is the page finder elements
editForm = element(by.name('editForm'));
nomeInput = this.editForm.element(by.id('field_nome'));
descricaoInput = this.editForm.element(by.id('field_descricao'));
I have tried whitout the editForm, and it behaves the same way
async setNomeInput(nome: string): Promise<void> {
await this.nomeInput.sendKeys(nome);
}
this is the "typer"
Thomas
@selenium4466_gitlab
async setNomeInput(nome: string): Promise<boolean> { await this.nomeInput.sendKeys(nome).then(()=>{ }); }
await grupoUpdatePage.setNomeInput('nome').then(async (value)=>{ await expect(value).toBe(true) });
hfsoares
@hfsoares
I will try that... but why would work?
Thomas
@selenium4466_gitlab
@hfsoares also check element the one you performing an action on
hfsoares
@hfsoares
check?