Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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