rust/tests/coverage-map
2023-09-18 22:33:05 +10:00
..
status-quo coverage: Regression test for inconsistent handling of closure spans 2023-09-18 22:33:05 +10:00
if.cov-map Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
if.rs Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
long_and_wide.cov-map Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
long_and_wide.rs Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
README.md Copy most of tests/run-coverage into tests/coverage-map/status-quo 2023-09-05 11:55:34 +10:00
trivial.cov-map Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
trivial.rs Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00

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.