Open Bug 551856 Opened 10 years ago Updated 2 years ago
Script type errors in JS components should be treated as errors inside the browser chrome test suite
hm, the harness has already a listener on the console service that prints TEST-INFO... was that printed?
No, I don't think that JS errors in components are printed to the console (I may be wrong, I didn't have a GUI display when I was debugging that problem.)
(In reply to comment #2) > No, I don't think that JS errors in components are printed to the console If they're not, something's very wrong. The console listener will catch anything that shows up in the error console, and that includes all JS exceptions.
(In reply to comment #3) > (In reply to comment #2) > > No, I don't think that JS errors in components are printed to the console > > If they're not, something's very wrong. The console listener will catch > anything that shows up in the error console, and that includes all JS > exceptions. I agree, that was why I filed this bug! :-)
I discovered a bunch of JS errors hidden in some mochitests just now in bug 652494. Is the fact that these errors and the one reported in this bug are not being reported as test failures a regression of bug 481406?
Component: BrowserTest → Mochitest
You need to log in before you can comment on or make changes to this bug.