Details
-
New Feature
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
Description
As a developper writing tests, I'd like the local browser to stay open after a failed test during development (or possibly after all tests). This will allow me to play with the browser content, open the console, inspect dom, etc, and understand why my test failed.
This feature could be restricted to "local" browser mode only, unless the remote/docket setup allows for multiple browsers to be opened (which would be the case with a full-blown grid). However, usefulness of that feature in a remote setup is questionable...
We could introduce two new configuration properties that would drive this feature:
- holdBrowserOpen: instructs the framework to keep the browser open after any test, irrespective of the test outcome (similar to Selenide's selenide.holdBrowserOpen property).
- holdBrowserOpenAfterFailedTest: tells the framework to keep the browser open only after failed tests
A new browser would be opened for subsequent tests if the previous had to be left open.
Checklists
Acceptance criteria