Decide whether to trust the report
Check a subtotal in your report and read the evidence from your build.
This full-text reading copy does not save answers. Open the interactive lesson for saved browser notes.
Open the report you built
Use the HTML file and saved task from lesson 2.
Open $PRACTICE/activity-report.html in your browser. Find the entry count, total minutes and Orion subtotal. Keep the briefing from Come back tomorrow open.
Follow along with the sample
Open the sample HTML report and archived 1.7.0 check record. The archived checks describe the recorded 1.7.0 run.
Check one answer yourself
Derive one expected answer from the CSV before comparing it with the report.
- Open
$PRACTICE/project/data/activity.csv. - Add the four Orion entries: 90 + 30 + 45 + 15 = 180 minutes.
- Compare that result with the Orion subtotal in your HTML report.
For the sample route, use the supplied CSV. The full sample has six entries and totals 270 minutes.
Your arithmetic check
Write your answer in your own notes, or use the interactive lesson.
This optional note stays in your browser profile and site.
Read the evidence from your build
Use the saved briefing to see which checks ran and what happened.
In the briefing, find probe:change and probe:final under Host checks. Check that both passed and read any recorded reviewer findings. If you closed the briefing, refresh it with the command from Come back tomorrow.
The probes test the selected reporting cases. Your independent subtotal checks one result against the input.
Optional test and reference details
Inspect the text checks and HTML checks. The compatibility results record the course’s checked runtimes.
evidence inspection prompt
Compare my Orion subtotal with the input and HTML report. Read the saved task’s change and final probes and any reviewer findings. Explain what this evidence supports and any open concern. Stop after inspection.Investigate a mismatch
If your independent answer and report differ, identify which rows explain the gap.
Compare the CSV rows with the project totals in the HTML. Keep the input, report and expected subtotal together so the mismatch is easy to reproduce.
If the results agree, continue with the saved checks and the evidence you have.
Choose a focused response
Use a confirmed mismatch to choose a check or a small correction.
Write the expected answer from the original input. If the output disagrees, capture a check that exposes the discrepancy. Inspect the evidence and review the scope before authorizing any correction.
Try the missing-row example
Use this hypothetical case to see how a plausible total can still be wrong.
Imagine the report omitted Orion’s last 15-minute Testing entry. It would show 5 entries, 255 minutes overall and 165 minutes for Orion. Which comparison would expose the omission?
The sample matches the six-row arithmetic and its selected checks pass. Which conclusion is supported?
The recorded checks support the sample and tested cases within the stated source and environment; other behavior may still need evidence. Correct. Connect the conclusion to the actual checks and keep untested cases visible.
Every possible input, platform and future change is now proven correct. The evidence covers the selected inputs, cases, source and environment. Broader claims need their own checks.
Record what the evidence supports
State what you checked, what agreed and what needs another look.
Example: “The CSV and HTML agree on 180 minutes for Orion. The saved probes passed the reporting checks. I can hand off this sample and its evidence.” Adjust the wording to reflect your results.
Your review decision
Write your answer in your own notes, or use the interactive lesson.
This optional note stays in your browser profile and site.
Next: Open Make the tool usable to hand off your report.