Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

uncaught exceptions #136

Closed
Raynos opened this Issue · 7 comments

2 participants

@Raynos

They do not show up in testem error tab.

@airportyh
Owner

A specify exception?

@Raynos

Something like

var foo = undefinedVariable

test(function () {
    assert(1 === 1)
})

Basically all errors outside the test runners control. i.e. something that would make a node process crash and print to STDERR

@airportyh
Owner

Works for me using the tape example. You should see this

Screen Shot 2012-12-29 at 11 06 29 PM

Do you have a gist that can demonstrate this?

@Raynos

That's node, not browsers.

@airportyh airportyh referenced this issue from a commit
@airportyh Switched order of the testem.js script vs bundle.js, this allows test…
…em to register for window.onerror before the bundle.js has a chance to run so that top level errors can but reported back to testem #136.
7672dc4
@airportyh
Owner

I think I have the answer, assuming you are using tape and using my example as the starting template, the bug can be fixed in the custom test page by including /testem.js before bundle.js. Please confirm this and then close.

@Raynos

This may be the issue. I'll see whether I can reproduce this.

@Raynos

This problem is probably fixed. Works in node at least.

@Raynos Raynos closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.