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
The builtin assertions are lackluster for testing in that they only cover assert_eq, assert_ne, assert, and assert_match (nightly). Ideally we should have the full collection of unit test assertion helpers like mature unit test libraries have, such as GTest.
This is to track adding assertions for eq, ne, true, false, regex, match, etc.
These should make use of the test-return-types, which also enables adding simple succeed!() and fail!() macros.
The text was updated successfully, but these errors were encountered:
Blocked by #6
The builtin assertions are lackluster for testing in that they only cover
assert_eq
,assert_ne
,assert
, andassert_match
(nightly). Ideally we should have the full collection of unit test assertion helpers like mature unit test libraries have, such as GTest.This is to track adding assertions for
eq
,ne
,true
,false
,regex
,match
, etc.These should make use of the test-return-types, which also enables adding simple
succeed!()
andfail!()
macros.The text was updated successfully, but these errors were encountered: