You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am loving the integrated test running, it has made my workflow much more efficient, but I've been running into major problem, I cannot see the stack trace if one of my tests throw an error. Compare this to running circleci.test/run-tests and I do see a stack trace, which is very helpful when developing tests or doing TDD. It would be great to have this in the test runner!
This is a bit of a contrived example:
(testing "uncaught exception"
(is (throw (Exception. "I have no stack trace"))))
Calva says:
ERROR in:upload-helpers-test: upload_helpers_test.clj, line 20: create-s3-key-test: uncaught exception:
error: java.lang.Exception: I have no stack trace + "
expected: (throw (Exception. "I have no stack trace"))
I am loving the integrated test running, it has made my workflow much more efficient, but I've been running into major problem, I cannot see the stack trace if one of my tests throw an error. Compare this to running
circleci.test/run-tests
and I do see a stack trace, which is very helpful when developing tests or doing TDD. It would be great to have this in the test runner!This is a bit of a contrived example:
Calva says:
REPL terminal with CircleCI
The text was updated successfully, but these errors were encountered: