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
Requested feature: Concrete playback should generate tests for all kind of failures, even those that trigger a UB.
Use case: Users wanting to debug a failure that is not related to a user assertion, such as invalid memory access, could run the generated test case under valgrind or miri to detect the issue.
Link to relevant documentation (Rust reference, Nomicon, RFC):
This test should generate at least 3 different tests. One for our of bound access (e.g.: new_len = 10), one for unwrap() a none object (new_len = 0), and one for the assertion failure (new_len = 1).
For the out of bounds case, the test would likely succeed in a regular execution, but it would fail when running it with MIRI or valgrind.
Note: Since these failures might not be so trivial, we may want a different structure or name schema for them to differentiate from things that should fail in a simple execution.
The text was updated successfully, but these errors were encountered:
Requested feature: Concrete playback should generate tests for all kind of failures, even those that trigger a UB.
Use case: Users wanting to debug a failure that is not related to a user assertion, such as invalid memory access, could run the generated test case under valgrind or miri to detect the issue.
Link to relevant documentation (Rust reference, Nomicon, RFC):
Dummy test case:
This test should generate at least 3 different tests. One for our of bound access (e.g.:
new_len = 10
), one for unwrap() a none object (new_len = 0
), and one for the assertion failure (new_len = 1
).For the out of bounds case, the test would likely succeed in a regular execution, but it would fail when running it with MIRI or valgrind.
Note: Since these failures might not be so trivial, we may want a different structure or name schema for them to differentiate from things that should fail in a simple execution.
The text was updated successfully, but these errors were encountered: