1428910 - --keep-open and/or --jsdebugger don't work properly with --verify

Status: NEW

(Testing :: Mochitest, enhancement)

Description

[:Gijs (he/him)]

I see errors when running a test with --verify.

For some reasons, the errors have no stack trace.

This is very unfortunate so I've added a debugger; keyword to the test, and run with --jsdebugger, but for some reason the debugger doesn't break, and when the test then fails the browser (as well as the debugger) is killed.

So I added --keep-open as well, and the browser is still killed immediately after the test.

This is very annoying and basically stops me fixing the issues I'm seeing with this test.

Comment 1

[Geoff Brown [:gbrown] (pto Apr 11-18)]

--verify sets --keep-open to False:

https://dxr.mozilla.org/mozilla-central/rev/739484451a6399c7f156a0d960335606aa6c1221/testing/mochitest/runtests.py#2425

As I recall, that's because keep-open is automatically set when running one test: normally (non-debug scenarios) when running "some-test.html --verify" it would be very inconvenient if each browser had to be closed manually.

Comment 2

[:Gijs (he/him)]

(In reply to Geoff Brown [:gbrown] from comment #1)
> As I recall, that's because keep-open is automatically set when running one
> test

OK, this at least explains why it behaves this way, though of course an explicit --keep-open entered on the commandline should override this behaviour...

Note that the behaviour you cite only occurs with mochitest-plain.