Description
Parse one bounded LCOV line-hit record.
Coverage records distinguish source locations, hit counts and unknown observations. Parsing one LCOV line or branch token preserves its metadata but does not establish that source mapping, collection or overall coverage is correct.
Parse one bounded LCOV line-hit record.
When to use this tool
Use LCOV Line Hit Record Fields when inspecting one bounded coverage-record token.
How to use the tool and how it works
- Enter record. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read line, hits, checksum. Use the output convention below.
Parse one bounded LCOV line-hit record. Accept DA: with positive 1-9-digit line, 1-12-digit hits and optional nonempty checksum without comma or newline; return numeric line/hits and checksum or empty text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| record | Record | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| line | Line | Required. Safe integer. |
| hits | Hits | Required. Safe integer. |
| checksum | Checksum | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"record": "DA:42,3,abc"
},
"output": {
"line": 42,
"hits": 3,
"checksum": "abc"
}
}Limitations and assumptions
- Checksum content and source correspondence are not verified; this is not a full coverage report.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Use the complete coverage report and matching source revision for aggregation, validation and meaningful testing conclusions.
References
Similar or alternative tools
- Development: LCOV Branch Record Line Parser
Parse one bounded LCOV branch record.
- Development: LCOV Function Call Record Parser
Parse one LCOV function-hit record.