Open wurzelkuchen opened 1 year ago
As agreed on, we'll change the ticket requirements: This feature is not supposed to be activated by default, because it may break existing test suites. The user has to activate it.
Also in the current implementation we have to many browsers run in parallel. Currently the browser from the test method opens (too early) at the same time as the browser from the before method and it closes at the same time as the browser from the after method (too late).
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.