| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-11-07 | coverage: Migrate `tests/coverage-map` into `tests/coverage` | Zalathar | -28/+0 | |
| 2023-11-07 | coverage: Flatten `coverage-map/status-quo/` into its parent directory | Zalathar | -0/+28 | |
| 2023-11-07 | coverage: Remove `tests/coverage-map/if.rs` | Zalathar | -9/+0 | |
| There is another test named `if.rs` in `tests/coverage-map/status-quo/`, so this test stands in the way of flattening that directory into its parent. Fortunately both tests are more-or-less equivalent, so removing this one is fine. | ||||
| 2023-09-05 | Add test suite `coverage-map` to test coverage mappings emitted by LLVM | Zalathar | -0/+9 | |
| We compile each test file to LLVM IR assembly, and then pass that IR to a dedicated program that can decode LLVM coverage maps and print them in a more human-readable format. We can then check that output against known-good snapshots. This test suite has some advantages over the existing `run-coverage` tests: - We can test coverage instrumentation without needing to run target binaries. - We can observe subtle improvements/regressions in the underlying coverage mappings that don't make a visible difference to coverage reports. | ||||
