mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
rust/tests/coverage/README.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

17 lines
767 B
Markdown
Raw Permalink Normal View History

coverage: Register `test::Coverage` as the test suite for `tests/coverage` This restores the ability to run a coverage test by specifying its path, e.g. `./x.py test tests/coverage/if.rs`. This runs the test in both modes.
2023-11-01 05:07:07 -05:00
The tests in this directory are shared by two different test modes, and can be
run in multiple different ways:
- `./x.py test coverage-map` (compiles to LLVM IR and checks coverage mappings)
coverage: Rename the `run-coverage` test mode to `coverage-run` This makes it more consistent with the `coverage-map` mode and the shared `tests/coverage` test directory.
2023-11-01 22:27:22 -05:00
- `./x.py test coverage-run` (runs a test binary and checks its coverage report)
- `./x.py test coverage` (runs both `coverage-map` and `coverage-run`)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
## 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.
coverage: Register `test::Coverage` as the test suite for `tests/coverage` This restores the ability to run a coverage test by specifying its path, e.g. `./x.py test tests/coverage/if.rs`. This runs the test in both modes.
2023-11-01 05:07:07 -05:00
If you haven't touched the coverage code directly, and the tests still pass in
coverage: Rename the `run-coverage` test mode to `coverage-run` This makes it more consistent with the `coverage-map` mode and the shared `tests/coverage` test directory.
2023-11-01 22:27:22 -05:00
`coverage-run` mode, then it should usually be OK to just re-bless the mappings
coverage: Register `test::Coverage` as the test suite for `tests/coverage` This restores the ability to run a coverage test by specifying its path, e.g. `./x.py test tests/coverage/if.rs`. This runs the test in both modes.
2023-11-01 05:07:07 -05:00
as necessary with `./x.py test coverage-map --bless`, without worrying too much
about the exact changes.
Reference in New Issue Copy Permalink