A test automation library based on common other best practice open source libraries. It adds missing functionalities but does not reinvent the wheel. Just glues stuff together nicely and adds some sprinkles.
MIT License
80
stars
11
forks
source link
Use different browser instances for before/after methods #231
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.
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.