Test, Diagnose, and Revise

Work through the explanation, apply it to the example, and complete the quick check before continuing.

Text description of the visual

The figure shows a capstone test and revision log. The safe test set includes a normal case, a missing-information case, and a conflicting-information case where relevant. The revision log records expected result, actual result, defect found, likely cause, targeted change, and retest result. A defect example area lists unsupported claim, omitted need, wrong tool, unclear handoff, inaccessible format, and missing stop condition. The decision area says that if retests remain unsuitable, learners should change the method or reject the workflow. The final reminder says that the test must expose at least one meaningful defect, and that honest failure is stronger than hidden defects.

Run the workflow on safe material. Include normal, missing-information, and conflicting-information cases where relevant.

Record expected result, actual result, defect, likely cause, targeted change, and retest result. Do not change everything at once.

Your test must expose at least one meaningful defect. Examples include an unsupported claim, omitted requirement, wrong tool, unclear handoff, inaccessible format, excessive permission, or missing stop condition.

If repeated tests remain unsuitable, change the method or reject the workflow. Honest failure and a justified stop are stronger than hidden defects.