Coverage — LCOV with Several TN: Test Names
Three named test runs in one tracefile, each covering a different part of the tree, reported via the TN: record most tools quietly discard. Keeping the name is what lets a report answer which suite covered a given line.
TN:unit
SF:src/cart/pricing.js
FN:2,unitPrice
FN:8,quantityMultiplier
FN:13,roundHalfUp
FN:19,applyTax
FN:25,bulkRate
FN:31,convertCurrency
FNDA:25,unitPrice
FNDA:8,quantityMultiplier
FNDA:9,roundHalfUp
FNDA:37,applyTax
FNDA:35,bulkRate
FNDA:0,convertCurrency
FNF:6
FNH:5
BRDA:5,0,0,11
BRDA:5,0,1,2
BRDA:15,1,0,2
BRDA:15,1,1,13
BRDA:24,2,0,2
BRDA:24,2,1,-
BRDA:33,3,0,6
BRDA:33,3,1,-
BRF:8
BRH:6
DA:2,13
DA:3,21
DA:4,23
DA:5,10
DA:6,8
DA:8,2
DA:9,47
DA:10,2
DA:11,0
DA:12,29
DA:13,41
DA:15,14
DA:16,36
DA:17,40
DA:18,5
DA:19,33
DA:20,0
DA:22,47
DA:23,18
DA:24,29
DA:25,18
DA:26,42
DA:27,17
DA:29,33Specifications
- Seed
- 61200
- Format
- LCOV tracefile
- Records
- 4
- Test Names
- 3
- Test Name Values
- unit, contract, e2e
- Line Endings
- LF
Testing contract
Expected to pass- Scenario
- Attribute coverage to the named suite that produced it.
- Expected result
- Three distinct TN: values are preserved and each source record is attributed to the run named immediately above it.
What is a .lcov file?
LCOV is a plain-text code-coverage tracefile format originally produced by the Linux Test Project's front end for gcov and now emitted by tooling across many languages. Records are grouped per source file between an `SF:` line and an `end_of_record` line, with `DA:` lines giving per-line hit counts, `FN:`/`FNDA:` lines covering functions, `BRDA:` lines covering branches, and `LF`/`LH`, `FNF`/`FNH`, `BRF`/`BRH` summary counters.
How to use this file
Use an example .lcov file to test coverage viewers, merge tools, and CI coverage gates — verifying that summary counters match the detail lines, that multiple source records are merged rather than overwritten, and that branch data survives conversion to Cobertura or JSON.
How to use this file for testing
“Coverage — LCOV with Several TN: Test Names” is a deterministic Novus Examples fixture for Conversion testing, Code parsing, Schema validation. The same content exported across many formats and linked as a group, so you can convert one and diff against the expected twin.
Documented properties for this file: seed 61200 · 4 records · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Test and coverage reports document their totals (suites, cases, passes, failures, skips, covered lines) in the spec table. Point your CI dashboard, coverage gate, or report converter at the file and assert those counts survive; format twins carry identical numbers so a conversion can be scored exactly.
Related files
- xmlCoverage — Clover XMLThe Clover serialisation, whose <metrics> element rolls statements, conditionals and methods into a single elements/coveredelements pair. Anything reading only that pair reports a blended percentage that matches none of the other three formats unless the components are separated first. Every file in this group describes the same four-file source tree and reports 127/140 lines, 17/24 branch outcomes and 18/20 functions, so a converter can be diffed against a known answer.
- xmlCoverage — Cobertura at Zero CoverageA structurally complete Cobertura report in which line-rate and branch-rate are 0.0 everywhere. The counterpart to the zero-coverage LCOV file, for checking that a converter keeps the class and method structure when there is nothing covered to describe.
- xmlCoverage — Cobertura Condition-Coverage AttributesCobertura with a condition-coverage attribute on every branching line, written in the "50% (1/2)" form. The percentage and the fraction can disagree in real reports, so a parser should read the fraction and treat the percentage as derived.
- xmlCoverage — Cobertura with One Package per DirectoryThe same coverage split into one package per source directory with dotted names, the layout a JVM project produces. Reports that key on class name alone collide as soon as two packages hold a class of the same name, which this file is shaped to expose.
- xmlCoverage — Cobertura with Several Source RootsThree <source> roots with class filenames given relative to them, which is how Cobertura represents a multi-root project. A viewer must try each root in turn to resolve a file; one that assumes a single root shows "source not found" for most of the report.
- xmlCoverage — Cobertura XMLThe Cobertura serialisation of the same run, with packages, classes, per-method line rates and condition-coverage attributes on every branching line. Cobertura expresses coverage as rates rather than counts, so this is the file that catches converters rounding a percentage into a hit count. Every file in this group describes the same four-file source tree and reports 127/140 lines, 17/24 branch outcomes and 18/20 functions, so a converter can be diffed against a known answer.
Generated by generation/testing.py. Free for any use, no attribution required — license.