In my cucumber files there are multiple tests (cucumber scenarios) in one browser session, that all do some routing, some with UI5, some without (e.g. login page -> access launchpad -> access app -> check -> logout page, login page -> access launchpad…
The first test runs fine but subsequent tests fail due to some wdi5 internal error (_context is not set and thus _context.waitForUI5() fails).
I got things running with a custom command, but reseting the internals from the outside doesn’t seem the best way to go:
Maybe you can add a similar command that makes it possible to fully reinitialize wdi5 or make waitForUI5 check if all the internals are still valid and if not, do some automated reinitialization.
In my cucumber files there are multiple tests (cucumber scenarios) in one browser session, that all do some routing, some with UI5, some without (e.g. login page -> access launchpad -> access app -> check -> logout page, login page -> access launchpad… The first test runs fine but subsequent tests fail due to some wdi5 internal error (_context is not set and thus _context.waitForUI5() fails). I got things running with a custom command, but reseting the internals from the outside doesn’t seem the best way to go:
Maybe you can add a similar command that makes it possible to fully reinitialize wdi5 or make waitForUI5 check if all the internals are still valid and if not, do some automated reinitialization.