State the test.See the outcome.
Reproduction steps
Scope
Identify the scenario and environment so a reviewer can try the same conditions.
Defect packet ↗Steps
Use ordered actions. An instruction such as “test the page” leaves too much to infer.
Defect packet ↗Expected
Keep the expected result tied to the criterion, not to the suspected implementation.
Defect packet ↗Actual
State the observed behaviour without exaggerating frequency or impact.
Defect packet ↗Impact
Describe the user consequence. Let the team decide priority with business context.
Defect packet ↗Follow-up
Unknown causes and missing artefacts should remain explicit until checked.
Defect packet ↗Make the path repeatable
- Same starting state
- Same ordered actions
- Expected and actual beside each other
A report helps someone reproduce a problem without guessing its cause.
Defect packet
Name the affected path, enter repeatable steps, expectation and observation, then copy the packet for review. No ticket is filed from this page.
Follow the work
Could you repeat it?
A drafted test, an observed result and a release decision are different events. Keep each one tied to the product you actually checked.