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
This is something we should do in a separate issue, when a test should fail, but it passes. There is no red line to tell us what passed that should not have passed. This is in comparison to the opposite. To illustrate, run nargo test on these two pieces of code:
#[test]fnfoo(){assert(1 == 2);}
#[test(should_fail)]fnfoo(){assert(1 == 1);}
and quoting @phated "I think we can follow on with more descriptive error messages (such as what kev mentioned or noting that a test failed because it succeeded but was expected to fail)"
Problem
Copying from #2418 (comment)
This is something we should do in a separate issue, when a test should fail, but it passes. There is no red line to tell us what passed that should not have passed. This is in comparison to the opposite. To illustrate, run
nargo test
on these two pieces of code:and quoting @phated "I think we can follow on with more descriptive error messages (such as what kev mentioned or noting that a test failed because it succeeded but was expected to fail)"
i also think this error message is not printed https://github.com/noir-lang/noir/blob/master/crates/nargo_cli/src/cli/test_cmd.rs#L134-L141. might be wrong about this. didn't take a very close look at it.
Happy Case
more descriptive, better formatted error messages for tests
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
Maybe
Support Needs
No response
The text was updated successfully, but these errors were encountered: