about summary refs log tree commit diff
path: root/tests/coverage/branch
AgeCommit message (Collapse)AuthorLines
2025-08-04coverage: Remove `-Zcoverage-options=no-mir-spans`Zalathar-202/+0
This flag turned out to be less useful than anticipated, and interferes with work towards expansion support.
2025-06-30Remove let_chains featureCameron Steffen-4/+4
2025-05-06coverage: Only merge adjacent coverage spansZalathar-143/+236
This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-05-06coverage-dump: Dump filenames instead of global file IDs (and bless)Zalathar-28/+28
2025-04-01coverage: Don't split bang-macro spans, just truncate themZalathar-40/+40
2025-04-01coverage: Shrink call spans to just the function nameZalathar-22/+22
This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-01-16coverage: Completely overhaul counter assignment, using node-flow graphsZalathar-390/+389
2024-12-23Revert "Auto merge of #130766 - clarfonthey:stable-coverage-attribute, ↵Zalathar-54/+72
r=wesleywiser" This reverts commit 1d35638dc38dbfbf1cc2a9823135dfcf3c650169, reversing changes made to f23a80a4c2fbca593b64e70f5970368824b4c5e9.
2024-12-16Stabilize #[coverage] attributeltdk-72/+54
2024-12-07coverage: Prefer to visit nodes whose predecessors have been visitedZalathar-167/+154
2024-12-04coverage: Add an extra "transcribe" step after counter creationZalathar-177/+160
2024-12-04coverage: Extract `subtracted_sum` in counter creationZalathar-4/+6
2024-11-08coverage: Restrict empty-span expansion to only cover `{` and `}`Zalathar-11/+11
2024-10-11coverage: Include the highest counter ID seen in `.cov-map` dumpsZalathar-0/+28
When making changes that have a large impact on coverage counter creation, this makes it easier to see whether the number of physical counters has changed. (The highest counter ID seen in coverage maps is not necessarily the same as the number of physical counters actually used by the instrumented code, but it's the best approximation we can get from looking only at the coverage maps, and it should be reasonably accurate in most cases.)
2024-06-17coverage: Add debugging flag `-Zcoverage-options=no-mir-spans`Zalathar-0/+191
When set, this flag skips the code that normally extracts coverage spans from MIR statements and terminators. That sometimes makes it easier to debug branch coverage and MC/DC coverage, because the coverage output is less noisy. For internal debugging only. If other code changes would make it hard to keep supporting this flag, remove it.
2024-05-14coverage: Simplify counter expressions using simple algebraZalathar-199/+114
Some of these cases currently don't occur in practice, but are included for completeness, and to avoid having to add them later as branch coverage and MC/DC coverage start building more complex expressions.
2024-04-30coverage: Add branch coverage support for if-let and let-chainsZalathar-7/+25
2024-04-30coverage: Add branch coverage support for let-elseZalathar-3/+9
2024-04-22coverage: Branch coverage tests for match armsZalathar-0/+401
2024-04-22coverage: Branch coverage test for if-let and let-chainsZalathar-0/+161
2024-04-22coverage: Branch coverage test for let-elseZalathar-0/+90
2024-04-17coverage: Branch coverage tests for lazy boolean operatorsZalathar-0/+370
2024-04-17coverage: Move branch coverage tests into a subdirectoryZalathar-0/+863