uncaught exceptions #136

Closed
Raynos opened this Issue Dec 20, 2012 · 7 comments

Comments

Projects
None yet
2 participants
@Raynos
Contributor

Raynos commented Dec 20, 2012

They do not show up in testem error tab.

@airportyh

This comment has been minimized.

Show comment Hide comment
@airportyh

airportyh Dec 20, 2012

Collaborator

A specify exception?

Collaborator

airportyh commented Dec 20, 2012

A specify exception?

@Raynos

This comment has been minimized.

Show comment Hide comment
@Raynos

Raynos Dec 20, 2012

Contributor

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

Contributor

Raynos commented Dec 20, 2012

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

This comment has been minimized.

Show comment Hide comment
@airportyh

airportyh Dec 30, 2012

Collaborator

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?

Collaborator

airportyh commented Dec 30, 2012

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

This comment has been minimized.

Show comment Hide comment
@Raynos

Raynos Dec 30, 2012

Contributor

That's node, not browsers.

Contributor

Raynos commented Dec 30, 2012

That's node, not browsers.

airportyh added a commit that referenced this issue Jan 5, 2013

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.
@airportyh

This comment has been minimized.

Show comment Hide comment
@airportyh

airportyh Jan 5, 2013

Collaborator

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.

Collaborator

airportyh commented Jan 5, 2013

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 comment has been minimized.

Show comment Hide comment
@Raynos

Raynos Jan 5, 2013

Contributor

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

Contributor

Raynos commented Jan 5, 2013

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

@Raynos

This comment has been minimized.

Show comment Hide comment
@Raynos

Raynos Aug 16, 2013

Contributor

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

Contributor

Raynos commented Aug 16, 2013

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

@Raynos Raynos closed this Aug 16, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment