when the tests fail, the browser that the selenium tests were running on closes. this is unhelpful when trying to debug. i know i have the option of a screen shot upon failure, but that doesn't help without the entire context. with the browser still available, i can hit back and inspect what was going on.
is there a way to keep the browser open even when asserts fail or elements aren't found?
figured it out randomly many weeks later.
when starting the server, use the option -browserSessionReuse at the end. this will keep one browser session open throughout the tests and not close on failure
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With