mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
e0fe1d6008
rust/tests/coverage-map
History
Zalathar 86a66c8171 coverage: Store each BCB's code regions in one coverage statement 
If a BCB has more than one code region, those extra regions can now all be
stored in the same coverage statement, instead of being stored in additional
statements.
2023-10-03 13:03:39 +11:00
..
status-quo coverage: Store each BCB's code regions in one coverage statement 2023-10-03 13:03:39 +11:00
if.cov-map
if.rs
long_and_wide.cov-map
long_and_wide.rs
README.md
trivial.cov-map
trivial.rs
unreachable.cov-map coverage: Regression test for functions with unreachable bodies 2023-10-01 14:44:27 +11:00
unreachable.rs coverage: Regression test for functions with unreachable bodies 2023-10-01 14:44:27 +11:00

README.md

The tests in ./status-quo were copied from tests/run-coverage in order to capture the current behavior of the instrumentor on non-trivial programs. The actual mappings have not been closely inspected.

Maintenance note

These tests can be sensitive to small changes in MIR spans or MIR control flow, especially in HIR-to-MIR lowering or MIR optimizations.

If you haven't touched the coverage code directly, and the run-coverage test suite still works, then it should usually be OK to just --bless these coverage mapping tests as necessary, without worrying too much about the exact changes.