Typorithm · medium
Step 1 of 4 · intro card
Report what was checked, what failed and what remains unknown.
A regression set should follow the changed behavior and important neighboring risks. For a combined-filter change, include the new conjunction, each individual filter and an empty result. Re-running unrelated checks can consume time while leaving the changed contract poorly observed.
State the decision context and unresolved risks. A test report supports a release decision; it does not turn a finite suite into proof that no defects remain. Keep passed, failed, blocked and not-run outcomes distinct.
The worked report has ten planned checks: seven passed, one failed, one blocked and one not run.
The worked report has ten planned checks: seven passed, one failed, one blocked and one not run. The pass rate among executed checks is seven of eight, while execution coverage is eight of ten. These answer different questions and must not share an unlabeled percentage.
Blocked and not-run checks still represent missing evidence. Do not add them to passed because the suite completed its command. Describe the reason and affected risk so a reviewer can decide whether the missing evidence is acceptable.
json
{
"planned": 10,
"passed": 7,
"failed": 1,
"blocked": 1,
"notRun": 1,
"executed": 8,
"passRateOfExecuted": 0.875,
"executionCoverage": 0.8
}The weak report calls the release 100 percent tested because every executed passing check is listed and failures are omitted.
The weak report calls the release 100 percent tested because every executed passing check is listed and failures are omitted. A denominator that silently changes can make an incomplete investigation look comprehensive. Preserve the planned scope and all outcome categories.
Avoid equating assertion count with coverage of requirements. One hundred similar assertions may all target one successful path. Connect important checks to named risks and keep the claim proportional to the actual evidence.
json
{
"passed": 7,
"reportedPassRate": 1,
"omitted": [
"failed",
"blocked",
"not run"
]
}Write a report for twelve planned checks: nine passed, one failed, one blocked and one not run.
Write a report for twelve planned checks: nine passed, one failed, one blocked and one not run. Calculate executed count, pass rate among executed and execution coverage. Begin with the counts before formatting any percentage.
Add a short release note identifying the failed risk and missing evidence. Optional extension: define a project-specific release threshold. Do not claim that one numerical threshold should decide every release regardless of severity.
Step 1: Reconcile all twelve planned outcomes. Step 2: Calculate and label both denominators.
json
{
"planned": 12,
"passed": 9,
"failed": 1,
"blocked": 1,
"notRun": 1,
"executed": "TODO",
"passRateOfExecuted": "TODO",
"executionCoverage": "TODO"
}The solution reports ten executed, a 90 percent executed pass rate and approximately 83.33 percent execution coverage.
The solution reports ten executed, a 90 percent executed pass rate and approximately 83.33 percent execution coverage. It keeps the failing check visible. The arithmetic is reproducible, but the release decision still depends on impact and context.
The verifier checks the denominators and rejects a calculation that counts blocked checks as executed successes. A reviewer assesses whether the accompanying risk explanation supports the chosen action. Numeric correctness alone cannot make that judgment.
json
{
"planned": 12,
"passed": 9,
"failed": 1,
"blocked": 1,
"notRun": 1,
"executed": 10,
"passRateOfExecuted": 0.9,
"executionCoverage": 0.8333333333333334,
"decision": "Review the failed risk and missing evidence before deciding; percentages alone are insufficient."
}In interviews, explain two different denominators and why blocked work matters.
In interviews, explain two different denominators and why blocked work matters. Describe how you would select regression checks for one concrete change. Avoid presenting a green dashboard as a universal release guarantee.
The foundations capstone now combines requirements, data selection, API observations and a concise report around one small local catalogue.
Optional stretch — after the core task works: Propose a threshold for one explicit risk context.
Computer practice: download the companion lab at https://applydjinn.com/typorithm/qa-lab-20261105.zip. Read its README, install the pinned tools and run the accepted examples before attempting a starter. The mobile reader preserves your reading and self-check progress; the local lab runs browser tests separately.
Report what was checked, what failed and what remains unknown.