tape-run with pantomjs does not show unhadled exceptions about stampit HOT 8 CLOSED

But even if you see the error message, you won't see the stack trace. Am I doing something wrong?

I miss stack trace very much. It is really a time-consuming job if you don't have an exception call stack. :(

from stampit.

In fact, simple node test/stampit-specs.js runs tests smoothly even without phantomjs.

I might not know something. But would someone explain me why we need phantomjs to run tests locally?

from stampit.

I have experienced the same problems with tape-run/phantomjs. But yeah, there really is no need for stampit tests to be ran in a browser. I'm just executing tests directly over at react-stampit.

from stampit.

Let's skip phantomjs. If we want to test in-browser, we should just use Sauce Labs.

You should get all your errors if you run tape without Stampit. Does that work for you?

from stampit.

Testing locally, if I force a test to fail, I'm seeing:

# tests 114
# pass 113
# fail 1

If I put in a TypeError, e.g. stampit.doesNotExist(), it does hang. Not sure why.

from stampit.

There are 171 tests in the init-making-stampit-flexible branch. Which is soon to be merged into v2_0. I've removed phantomJS there. So, as soon as in 12 hours all the issues mentioned here will be resolved. :)

from stampit.

👍

from stampit.

The issue got resolved in branch 2.0 with node test/index.js instead of tape-run. :)

I confirm exception stack traces are being printed. Tape assertions print the file name and line number on fails.

All good.

from stampit.