Another test.
After examining the existing tests, I note that the difference here is that it's specifically an uncaught exception, so there's no Exception object. The other fast/js/exception* tests are examining the properties of the Exception produced.
Created attachment 25692 [details] New test + result This test is not suited to the JS wrapper, because the uncaught exception halts parsing. The test also currently doesn't produce the right output, instead saying the exception was thrown on line 0. Unfortunately, there's no good way to mark it as an expected failure (no way to have FAIL come up in the expected results). All in all, not an ideal test, but I don't know of a better way to check what it's looking at. The line-number error looks like bug 5206.
Comment on attachment 25692 [details] New test + result No harm in having this test checked in. r=me
Landed r39054