-
-
Notifications
You must be signed in to change notification settings - Fork 645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cider test reporting errors under specific conditions #1379
Comments
(deftest test-1
(throw (ex-info "bad error" {}))
(is (= 1 1))) This is actually enough to get the error reporting to fail for me with |
@expez I do get an error, but it's not |
I get the same as you now. Guess we fixed the problem in the process filter while sorting out other issues / doing general refactoring. |
Anyone still seeing an error here? Neither of the repro cases above cause any misbehavior for me. |
I just updated to latest cider and still see the error with the macro generated test.
for reference here's the macro code used to generate the
|
Ok, reproduced it. The |
@RadicalZephyr Congrats. You were apparently the first person to run a (non-passing) test that didn't have whitespace before the form. |
Enable test fail/error highlighting for forms at the beginning of a line with no preceding whitespace.
Enable test fail/error highlighting for forms at the beginning of a line with no preceding whitespace.
Fun! thanks @jeffvalk |
Currently, while cider is running tests, if an error is thrown from inside a macro-generated test, but not by an assertion (i.e. an
is
), CIDER errors withIt's a fairly edge case, but it's important to me right now. I have a minimal reproduction repo available.
I spent some time trying to chase this down myself, but I just got lost in the bowels of CIDER. The ideal resolution to this would be to find all the errors correctly, but it would be a big win if CIDER didn't just totally give up, and still printed the errors that were not directly inside of generated tests.
Tested under:
and
The text was updated successfully, but these errors were encountered: