Working on E2E tests using mocha and selenium-webdriver has been quite a challenge for me. Although I have implemented async/await functions to handle most of the tests smoothly, I am facing an issue where none of the tests are completing successfully. Here is a snippet of my current code:
describe('Some test', function () {
before(function () {
driver.navigate().to('http://localhost:3000')
})
after(function () {
driver.quit()
})
it('should display element', async function () {
let elementFound = false
try {
await driver.wait(until.elementIsVisible(driver.findElement(By.className('element'))), 1000)
assessForm = await driver.findElement(By.className('element')).isDisplayed()
assert.ok(elementFound)
console.log('elementFound', elementFound)
} catch (err) {
console.log(err)
assert.fail(err)
}
})
})
The main problem appears to be that the after function gets executed before the test can complete properly. The error logs indicate:
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
{ NoSuchSessionError: no such session (Driver info: chromedriver=2.36.540469 (1881fd7f8641508feb5166b7cae561d87723cfa8),platform=Mac OS X 10.13.3 x86_64) at Object.checkLegacyResponse (/Users/me./myproject/node_modules/selenium-webdriver/lib/error.js:585:15) at parseHttpResponse (/Users/me./myproject/node_modules/selenium-webdriver/lib/http.js:533:13) at Executor.execute (/Users/me./myproject/node_modules/selenium-webdriver/lib/http.js:468:26) at at process._tickCallback (internal/process/next_tick.js:188:7) name: 'NoSuchSessionError', remoteStacktrace: '' }
Even without the after() function, the timeout error persists,
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves.
but, interestingly, my console.log confirms that the element was found.
Trying to make after() async as well:
after(async function () {
await driver.quit()
})
resulted in encountering the same initial error.
It's worth mentioning that I've come across sources claiming not needing to use done() with async/await, yet the errors persist regardless. How do I resolve this situation? Everything seems to be set up correctly, but the tests just won't run smoothly without interfering with each other.