Testacular prevents error messages from being logged in browser console

[mpj]

In my testacular.conf.js, I'm loading a test-runner.js, which in turn requires my tests using a custom-made require function. This works fine, but if test-runner.js or any of the tests it loads through require has a syntax error, that error does ONLY show up in the Testacular command line tool, not the browser. I'd like it to show up in the browser in addition to the command line, just like errors that occur after the tests start runnung.

The reason I need this is because I want source maps to work (the require does some stuff that messes up the line numbers). If the error is handled by the browser, it will be able to use the source map and produce a correct line number, which Testacular does not.

[dignifiedquire]

We could change this behavior so that these errors get printed in the browser too, but in the meantime you should be able to work around this if you don't throw the error but use console.error which gets logged to the browser.

[vojtajina]

You can work around it as well, by overriding the window.onerror handler:

window.onerror = function(msg, url, line) {
  window.__testacular__.error(msg, url, line);
  return false;
};