Skip to content

Main content

Development: LCOV Function Call Record Parser Tool

Parse one bounded LCOV FNDA function-execution record, preserving commas within the function name; no coverage aggregation.

Loading tool…

Description

Parse one LCOV function-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 LCOV function-hit record.

When to use this tool

Use Development: LCOV Function Call Record Parser when inspecting one bounded coverage-record token.

How to use the tool and how it works

  1. Enter line. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read result. Expand result to inspect the returned fields.

Parse one LCOV function-hit record. Accept FNDA: followed by a 1-9-digit count, comma and nonempty function name without CR/LF; return callCount and functionName.1

Input fieldMeaning and unitsAccepted input
lineLineRequired. Text. Implementation limit: 8192 Unicode code points and 16384 UTF-16 code units.
Output fieldInterpretationReturned shape
resultReturned object; expand its named members below.Required. Object.
result.callCountCall CountCalculated result member: number.
result.functionNameFunction NameCalculated result member: string.
json
{
  "input": {
    "line": "FNDA:12,foo,bar"
  },
  "output": {
    "result": {
      "callCount": 12,
      "functionName": "foo,bar"
    }
  }
}

Limitations and assumptions

  • Function names may contain commas; no function existence or coverage completeness is verified.
  • Outputs are nested inside result. 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

  1. Calculation and input contract: development/lcov-function-call-record-parser — tool.io

Similar or alternative tools