Running a single mochitest keeps test browser open after completion.

RESOLVED DUPLICATE of bug 1052211

Status

Testing
Mochitest
RESOLVED DUPLICATE of bug 1052211
3 years ago
3 years ago

People

(Reporter: markh, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Bug 1014062 is a little confusing, but I'm convinced that in the past, running "mach mochitest-browser path/to/single_test_file" would run the test and automatically terminate the process.  Now it acts as if --keep-open was specified, and there seems to be no way to have the process terminate automatically.

CC bz, ted and gijs as they were involved in that discussion in bug 1014062.  CC unfocused as he was also wondering why --keep-open seemed to recently become the default.

I can't see a reason for the new behaviour given --keep-open exists and seems to work.  Bug 990289 (referenced by bug 1014062) implies that explicitly specifying --keep-open is fine for the people who want this new behaviour.

Can anyone offer insights into why things are now done this way, and a way forward so this behaviour isn't forced on those of us who don't want it?
> explicitly specifying --keep-open is fine for the people who want this new behaviour

If by "fine" you mean "a huge PITA"....  The normal usage for me of running a single mochitest is when debugging/editing it, and having the browser quit is never what I want in that situation, personally.

I agree that there should be a way to get the behavior you want _and_ the behavior I want by default (via a setting in some config file) without having to sprinkle command-line flags all over, though.
I suspect the default before bug 1014062 was keep-open for mochitest-plain/mochitest-chrome and !keep-open for mochitest-browser. I have no idea why, and I've not verified that, but that would tally with everyone's memories, it seems.
For mochitest-chrome and mochitest-browser there is not much point to the --keep-open behavior by default, since you have to restart the browser to rerun a modified version of the test.
Fwiw, I filed a similar bug 1052211. There it was decided to add a --autoclose command-line flag.
(Reporter)

Comment 5

3 years ago
(In reply to Martijn Wargers [:mwargers] (QA) from comment #4)
> Fwiw, I filed a similar bug 1052211. There it was decided to add a
> --autoclose command-line flag.

Good enough for me, thanks!
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1052211
You need to log in before you can comment on or make changes to this bug.