Coverage — Gate Configuration (JSON)
The threshold configuration the three boundary tracefiles in this group are meant to be judged against: global minimums, one per-path override and an explicit >= comparison. Publishing the comparison operator is the point — leaving it implicit is what makes an at-the-gate report ambiguous.
{
"$comment": "Gate configuration for the three boundary tracefiles in this group.",
"coverageThreshold": {
"global": {
"lines": 80,
"statements": 80,
"functions": 75,
"branches": 65
},
"src/checkout/": {
"lines": 85
}
},
"comparison": ">=",
"failOnDecreaseFromBaselinePct": 0.5,
"baseline": {
"lines": 90.71,
"branches": 70.83,
"functions": 90.0
},
"reportPaths": [
"threshold-at-gate.lcov",
"threshold-below-gate.lcov",
"threshold-above-gate.lcov"
]
}
Specifications
- Seed
- 61200
- Format
- JSON
- Global Line Minimum
- 80
- Global Branch Minimum
- 65
- Path Overrides
- 1
- Comparison
- >=
- Line Endings
- LF
Testing contract
Reference control- Scenario
- Apply a declared coverage gate to the boundary tracefiles in this group.
- Expected result
- With comparison >= and a global line minimum of 80, the at-gate and above-gate tracefiles pass and the below-gate one fails.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“Coverage — Gate Configuration (JSON)” is a deterministic Novus Examples fixture for Config parsing, JSON parsing, Schema validation. TOML and INI configuration files with nested sections and typed values — for testing config parsers and loaders.
Documented properties for this file: seed 61200 · LF · JSON. 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.
Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.
Code examples
import json
with open("coverage-gate-config.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- jsonCoverage — Istanbul JSON SummaryThe compact json-summary reporter output: a total block plus one block per file, each with lines, statements, functions and branches as total/covered/skipped/pct. This is what coverage badges and pull-request comments are generated from. 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.
- jsonCucumber JSON — Passing Checkout ReportThe legacy cucumber.json report for the same run — the format nearly every BDD dashboard still ingests. Durations are in nanoseconds here and in a nested {seconds, nanos} object in the messages twin, which is the single most common unit bug when converting between the two.
- ndjsonCucumber Messages — Passing Checkout Run (NDJSON)The machine twin of checkout.feature: the cucumber-messages envelope stream a runner emits, with meta, source, gherkinDocument, one pickle per expanded scenario, and paired testStepStarted/testStepFinished envelopes carrying nanosecond durations. Written as NDJSON because that is the format's actual wire shape — one envelope per line, not a JSON array.
- jsonPerformance Budget — Page and API Limits (JSON)A budget file pairing per-path resource-size and timing limits with API latency budgets, including a glob path that must be matched rather than compared for equality. It is the configuration side of the load-test results in this group: the limits a run is judged against.
- yamlAttestation Verification Policy (YAML)The policy an admission controller evaluates before an artifact is allowed through: required predicate types, an allowed-builder list, a minimum SLSA level, a transparency-log requirement and one dated exception. Every package, version, hash and licence is fictional — the tree describes nothing real.
- jsonAttestation With a Full SPDX PredicateAn in-toto statement whose predicate is an entire SPDX 2.3 document — the nesting that makes attestation payloads large and that a size-limited verifier has to cope with. Every package, version, hash and licence is fictional — the tree describes nothing real.
Generated by generation/testing.py. Free for any use, no attribution required — license.