Way to leave browser open at end of tests?

[dmwyatt]

I've got a few tests that are causing chrome to just return a 500 Internal Server Error but work fine in Firefox. It would be extremely helpful to be able to leave browser open at end of tests so I can inspect in the browser what is going wrong.

[mantoni]

Yes, I would like to support that 👍

The way I would prefer it work is a new option in the min-webdriver API, maybe closeOnFailure: true. The default should be true because most people use remote machines with Selenium Grid and would have to log into them to close any "leaking" browser sessions manually.

The new option could then be exposed in the Mochify API and as a command line option.

Would you have some free cycles to look into this?

[dmwyatt]

Sure, I'll look at it today. I'll take any further discussion to an issue or pull request on min-webdriver

[mantoni]

Now that this is supported by min-webdriver, there could be an API enhanceent and a command line option in Mochify that sets both values to false. This would allow users to quickly run a debugging session without the need the change the configs. What do you think @dmwyatt?

[dmwyatt]

This makes a lot of sense to me.

On Wed, Mar 25, 2015 at 2:45 AM Maximilian Antoni [email protected]
wrote:

Now that this is supported by min-webdriver, there could be an API
enhanceent and a command line option in Mochify that sets both values to
false. This would allow users to quickly run a debugging session without
the need the change the configs. What do you think @dmwyatt
https://github.com/dmwyatt?

—
Reply to this email directly or view it on GitHub
#77 (comment).