Coverage — Markdown Pull-Request Summary
The Markdown comment a coverage bot posts on a pull request: a headline percentage, a per-file table and the uncovered line numbers. Useful for testing Markdown table rendering and for checking that a bot's generated comment matches the machine-readable report it claims to summarise. 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.
# Coverage — Novus Checkout Service
Overall line coverage **90.71%** (127/140 lines), branch coverage **70.83%** (17/24), function coverage **90.00%** (18/20).
| File | Lines | Hit | Line % | Branches | Hit | Branch % |
| --- | ---: | ---: | ---: | ---: | ---: | ---: |
| `src/cart/pricing.js` | 44 | 40 | 90.91% | 8 | 6 | 75.00% |
| `src/cart/discounts.js` | 33 | 28 | 84.85% | 6 | 4 | 66.67% |
| `src/checkout/session.js` | 39 | 36 | 92.31% | 6 | 4 | 66.67% |
| `src/checkout/receipt.js` | 24 | 23 | 95.83% | 4 | 3 | 75.00% |
| **TOTAL** | **140** | **127** | **90.71%** | **24** | **17** | **70.83%** |
Uncovered lines by file:
- `src/cart/pricing.js`: 11, 20, 30, 39
- `src/cart/discounts.js`: 8, 13, 19, 25, 31
- `src/checkout/session.js`: 12, 23, 33
- `src/checkout/receipt.js`: 16
Specifications
- Seed
- 61200
- Source Files
- 4
- Lines Found
- 140
- Lines Hit
- 127
- Line Pct
- 90.71
- Branches Found
- 24
- Branches Hit
- 17
- Branch Pct
- 70.83
- Functions Found
- 20
- Functions Hit
- 18
- Line Endings
- LF
- Format
- GitHub-flavoured Markdown
- Has Table
- true
- Table Rows
- 5
- Lists Uncovered Lines
- true
Testing contract
Reference control- Scenario
- Check a generated coverage comment against the machine-readable report it summarises.
- Expected result
- The headline 90.71% and every table row match the LCOV, Cobertura, JaCoCo and Istanbul twins in this group.
What is a .md file?
Markdown (MD) is a lightweight plain-text markup language that uses simple punctuation conventions to denote headings, lists, links, emphasis, and code. It is designed to be readable as-is and to convert cleanly to HTML. It is widely used for documentation, READMEs, and content authoring.
How to use this file
Use an example Markdown file to test parsers and renderers, verify GitHub-Flavored Markdown extensions like tables and fenced code, and exercise HTML-conversion pipelines.
How to use this file for testing
“Coverage — Markdown Pull-Request Summary” is a deterministic Novus Examples fixture for Conversion testing, Editor testing, 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 · LF · GitHub-flavoured Markdown. 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.
Code examples
import markdown # pip install markdown
html = markdown.markdown(open("coverage-summary.md").read())
print(html[:200])Related files
- jsonCycloneDX 1.6 Application SBOM (JSON)A complete CycloneDX 1.6 SBOM in JSON for a fictional application and its nine dependencies, with purls, SHA-256 hashes, supplier records, external references and an explicit dependency graph. Every package, version, hash and licence is fictional — the tree describes nothing real.
- xmlCycloneDX 1.6 Application SBOM (XML)The same fictional CycloneDX 1.6 SBOM serialised as XML against the cyclonedx.org/schema/bom/1.6 namespace — the JSON twin of this file carries identical components and edges, so a converter can be diffed exactly. Every package, version, hash and licence is fictional — the tree describes nothing real.
- jsonSPDX 2.3 Application SBOM (JSON)An SPDX 2.3 SBOM in JSON describing the same fictional tree as the CycloneDX documents in this category, with SPDXIDs, purl external references, SHA-256 checksums and DESCRIBES/DEPENDS_ON relationships. Every package, version, hash and licence is fictional — the tree describes nothing real.
- 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.
Generated by generation/testing.py. Free for any use, no attribution required — license.