Use different browser instances for before/after methods #231
Labels
codeReadyForMerge
The issue was implemented and the branch is ready to be reviewed and merged into develop
docsNeeded
The documenttion needs to be checked if there are changes needed and if so, adaptions should be made
Milestone
If during a test case the browser is crashing, the after method will not be able to do it's cleanup, which might leave the target system in an unstable state, affecting all other tests. (Had this case recently)
Since the cleanup before/after a test case is crucial to keep the general test suite running, it would be good to have them run in separate browser instances by default.
Since it also might be important to do the cleanup on the same browser instance (session, local storage etc.), this should be configurable, maybe via an annotation on the test case.
A unit test which actively kills the browser would be nice.
The text was updated successfully, but these errors were encountered: