Description:
Introduce code coverage tracking that measures how much of the WT codebase is exercised when running the existing test suite (python, test/format, test/checkpoint), including both existing WT components and newly added Disagg components. The goal is to run the current tests, see which areas of the codebase they actually cover, and use this data to identify gaps and guide future testing. Coverage reporting should run as part of the normal test flow.
Outcome:
- Coverage results are generated for Disagg (utise test/format, python test, test/checkpoint) as we do for classic WT (here).
- Corresponding coverage task added to Evergreen under [Failure Expected] (ARMV9) Amazon 2023 Disagg Stress Tests.
- is related to
-
WT-16182 test_timestamp26.py failed in disagg mode running non-diagnostic build
-
- Open
-
-
WT-16184 Add disagg testing coverage for release build
-
- Backlog
-
- related to
-
WT-16197 Add more Python disagg tests to code coverage tracking
-
- Backlog
-
-
WT-16198 Generate disagg-only coverage report
-
- Backlog
-
-
WT-16226 Use the --skip-tests-in-file Python runner flag to replace Evergreen unit_test_ignore variable
-
- Backlog
-
-
WT-15025 Measure code coverage by test/model related to recovery
-
- Open
-