|
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 |
|||
|
|
|
You might be calling selenium.stop() at the end of the test. You need to comment out that line of code and make sure that your selenium object is not destroyed at the end of the test. This will keep the window open. Same question has been answered here |
|||
|
|
|
Regarding the answer about -browserSessionReuse at http://stackoverflow.com/a/6904808/654026, keep in mind that you will have to deal with cleaning the cookies between tests executions. Otherwise you may have difficult to debug errors. |
|||
|
|
