Test repeatable and failed runs
See this course’s project requirements
A local command-line converter that validates fictional attendance CSV, writes JSON to a chosen output and reports rejected rows without altering input.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- A converter contract with two accepted and two rejected records.
- A CSV-to-typed-record trace with invalid-value evidence.
- A failure report distinguishing rejected rows from failed runs.
- A checked JSON output with 2 accepted and 2 rejected entries.
- A reusable command contract and a missing-argument test.
- A repeatable local CSV converter with failure and preservation evidence.
Review and revise
Use these criteria to check your work and choose what to improve.
- The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
- Normal, boundary and rejected cases are recorded with expected versus observed results.
- The changed case has a correct explanation and does not rely on hidden state.
- The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Want more background?
The idea in everyday life
Use the supplied 4 rows, a changed D,0 row, a wrong-header fixture and a missing-input path. Keep all files within a fresh practice folder.
Repeatability includes unchanged input, correct regenerated output and declared failures. Running twice is useful only if the second output is actually compared and hidden state is excluded.
Test repeatable and failed runs — original worked practice
Repeatability includes unchanged input, correct regenerated output and declared failures. Running twice is useful only if the second output is actually compared and hidden state is excluded.
Use the supplied 4 rows, a changed D,0 row, a wrong-header fixture and a missing-input path. Keep all files within a fresh practice folder.
1. Step 1
Convert baseline twice to two fresh outputs.
You should see: Both parsed results match 2 accepted and 2 rejected.
This keeps the rule and its observable result together.
2. Step 2
Add D, 0 in a separate changed input.
You should see: Three accepted and two rejected records.
This keeps the rule and its observable result together.
3. Step 3
Try the same input/output path and wrong headers.
You should see: Both fail without replacing the input.
This keeps the rule and its observable result together.
4. Step 4
Package the tool, fixtures, output and four-case run record.
You should see: A repeatable local CSV converter with failure and preservation evidence.
This keeps the rule and its observable result together.
What to finish
A repeatable local CSV converter with failure and preservation evidence.
Watch for this
Calling a repeated run reproducible without comparing accepted records, rejected rows, and unchanged source bytes.
How can I tell I understand it?
Explain and demonstrate the required distinction: Repeatability includes unchanged input, correct regenerated output and declared failures. Running twice is useful only if the second output is actually compared and hidden state is excluded. Show a changed input and the expected result without weakening this contract.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.