How to Test AI-Generated Code: Beginner Debugging Guide

Verify stage · Module 11 of 15

Outcome for this lesson

Reproduce failures, isolate changes, rerun critical journeys, and preserve regression evidence.

Bring forward: Bring the secured working slice, acceptance tests, accessibility record, and known limits.

Produce: A test matrix plus one complete bug record from reproduction through verified regression testing.

0 of 15 core modules complete

Progress is saved on this browser. Create a free membership to sync across devices.

Recommended prerequisite: complete Module 10, “Apply Security and Privacy Boundaries,” and bring its artifact. You may still use this page as a reference.

Verify stage

Build the next result

You now have requirements, a working slice, accessibility evidence, and security boundaries. Testing connects those promises to observable behavior and debugging prevents one repair from breaking another.

Your result for this module

A test matrix plus one complete bug record from reproduction through verified regression testing.

Continuous case study

Worked example: Inquiry disappears after refresh

Reproduction: begin with an empty list, add a valid inquiry, refresh, and observe an empty list instead of the saved entry. Hypothesis: the save function writes memory but not persistent storage. One isolated change is made, then save, reload, edit, invalid-date, keyboard, and recovery journeys are rerun.

Do the work

Build the test matrix
Include ordinary, edge, invalid, failure, accessibility, privacy, recovery, and previously working journeys.
Capture one exact failure
Record starting state, environment, steps, input, expected result, actual result, time, and useful evidence without secrets.
Change one hypothesis at a time
Make the smallest plausible repair and avoid upgrades or refactors unrelated to the cause.
Prove repair and regressions
Rerun the failing case and critical journeys. Save results, changed version, remaining limits, and rollback point.

Copy-and-complete template

Create your module artifact

Test matrix reference:

Bug starting state and environment:

Steps and input:

Expected and actual result:

Hypothesis:

Isolated change:

Failure retest:

Regression results:

Evidence and known limits:

Keep sensitive information, passwords, API keys, payment data, and private customer details out of course notes and AI prompts.

Quality gate

Check the result before the quiz

Every important requirement has a test.
The bug can be reproduced by another person.
The repair is tied to one hypothesis.
Regression evidence covers critical journeys.

How this moves the project forward

Module 12 uses the verified design and operating needs to calculate the real cost of delivering it.

Evidence checkpoint and lesson summary

Confirm the artifact, then answer the key questions

The questions cover a core idea, a realistic decision, and evidence from the lesson. Incorrect answers identify concepts to review; they are not a complete measure of your experience or ability.

Artifact checkpoint I created the module artifact, checked it against the quality gate, and recorded any remaining limitation.

This is an honest self-check. Do not enter private data here; keep the artifact in your own approved workspace.

1. Which report gives another person enough information to reproduce a failure? Login is broken on mobile and needs immediate attention, using the same rule throughout the first release Starting state, device, actions, input, expected result, actual result, and timestamp A screenshot of the final error message with no preceding actions

2. The cause is still unknown. What change is appropriate? A broad refactor of every file involved in the user journey, followed by a review at the next project checkpoint A dependency upgrade combined with new validation behavior The smallest plausible change tied to one explicit hypothesis

3. Which evidence supports the claim that the bug is fixed? The reproduction now passes, critical regressions pass, and the change and logs are recorded The failing case passed once after several files were changed, with that decision recorded in the project evidence The model explains why the revised implementation should be stable

Confirm the artifact and answer all three questions correctly to unlock the recommended next step.

Test, Debug, and Prove the Important Journeys

Outcome for this lesson

Build the next result

Your result for this module

Worked example: Inquiry disappears after refresh

Do the work

Build the test matrix

Capture one exact failure

Change one hypothesis at a time

Prove repair and regressions

Create your module artifact

Check the result before the quiz

How this moves the project forward

Confirm the artifact, then answer the key questions

About the author