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();
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
- Opening of browser instance for a first test case & running the whole test case which is happening
- then closing the above instance of first test case irrespective of the failure/success run.
- Now opening the new browser instance for 2nd test case-->>running whole test case--->>closing the browser instance of this particular test case--->>
- 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.
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
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
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.
navBarGrupos = new NavBarGrupos();
await navBarGrupos.clickOnCrieNovoGrupo();
grupoUpdatePage = new GrupoUpdatePage();
grupoCabecalhoPage = new GrupoCabecalhoPage();
await grupoUpdatePage.setNomeInput('nome'),
await grupoUpdatePage.setDescricaoInput('descricao')nomeInput = this.editForm.element(by.id('field_nome'));
descricaoInput = this.editForm.element(by.id('field_descricao'));
await this.nomeInput.sendKeys(nome);
}