I ran Firefox against a new profile (created by "mach run") and saw 5 different exceptions logged to stdout and the Browser Console: * bug 1205819 * bug 1205827 * bug 1205833 * bug 1205837 * bug 1205840 Do we have enough test coverage of Firefox first-run?
Tests not failing on exceptions/error messages is the bigger problem, new profiles are just a good way to suss out such errors
Summary: We need a regression test that runs Firefox against a fresh profile and fails if any exceptions are logged → We need a regression test that launches Firefox and fails if any exceptions are logged
< RyanVM> vladan: maybe related - bug 910614 < RyanVM> vladan: and hanging off that - bug 920191 < vladan> RyanVM: thanks. interesting angle about errors not getting propagated to onerror handlers < RyanVM> sadly, we've seen real bugs missed care of bug 920191
Ted / Chris: any idea what, if any, framework would be best for this? (Feel free to pass on needinfos, I'm not entirely sure where best to start...)
Component: General → General
Product: Firefox → Testing
I think we ought to be able to do this with the Marionette harness, but I'm not 100% sure. I don't think any of our other harnesses really offer anything close to this.
Right, Marionette is probably our only harness that can launch the browser as part of a test.
You need to log in before you can comment on or make changes to this bug.