SoftwareTestPilot

A bug's journey from New to Closed. Simulated in your browser, free, no sign-in.

Defect Life Cycle

Step 1 of 5

Now simulating · step 1 of 5

Tester reports the defect

Paused

Simulated lesson: the defect, people and builds are fictional, and records stay in this page only.

Correct fix: closed - now New

NewTriagedIn ProgressReady for QAClosed
Failed retest:Ready for QAReopenedIn Progress
Other outcomes:Needs infoDuplicateDeferredNot a Bug

One sample team's workflow. Other organisations use different states and names.

Evidence and activity

  1. #1 [system] Defect workspace opened (simulated, local to this lesson).
  2. #2 [Tester] Reproduced on the current build: discount -8.00 shown, total 80.00 (expected 72.00). Screenshot attached.

Tip: click a coloured area or an edge line to see what it does.

Text description of this step
  • Scenario: Correct fix: closed. Current state: New.
  • #1 system: Defect workspace opened (simulated, local to this lesson).
  • #2 tester: Reproduced on the current build: discount -8.00 shown, total 80.00 (expected 72.00). Screenshot attached.
Speed

Keyboard: Space plays or pauses (when not typing).

Learning objective: Move a defect through a sample workflow, write a reproducible report, and decide when a fix may be closed.

Step 1 · Beginner

Tester reports the defect

The tester reproduces the problem and writes steps, expected and actual results. The defect starts as New.

Expected outcome: A clear report in New.

This is one team's workflow (New, Triaged, In Progress, Ready for QA, Closed, with Reopened, Needs info, Duplicate, Deferred and Not a Bug). Your team may use other states.

The defect

  • Fictional shop. Code SAVE10 gives 10% off orders over 50.00.
  • The cart shows the discount line (-8.00) but charges the full 80.00.
  • Every customer using the code is overcharged. A promotion using SAVE10 starts this week.
  • A workaround exists only via a manual refund by support.
About this lesson

You will learn to

  • Name each state and who moves the defect there in this sample workflow.
  • Write a complete defect report and set severity and priority from business context.
  • Retest a fix, choose a relevant regression check, and close or reopen with evidence.

Before you start

  • Know what a test case and a bug are.

Your progress on this topic

Explored
0 of 5 guided steps viewed
Practiced
  • Not yet: Perform a workflow action in the lab
  • Not yet: Record a failing retest
Challenges passed
  • Beginner: 0 of 3 · hints 0 · wrong answers 0
  • Practitioner: 0 of 3 · hints 0 · wrong answers 0
  • Advanced: 0 of 2 · hints 0 · wrong answers 0

Watching the walkthrough only counts as explored. Practice needs you to use the lab yourself, and a challenge passes only when your answer meets its criteria.

Practise more

Intentional failure: Incomplete fix: the retest fails and it reopens

Nothing is posted anywhere. You choose where to paste the link or summary.

How to explain this in an interview

"A good report has a clear title, numbered steps, expected and actual results with real values, the environment and evidence. Severity is the impact on users; priority is how soon the business needs it fixed. I only close after retesting the original steps and the related risk areas the fix touched; otherwise I reopen with new evidence."

Next recommended topicBoundary Values & Equivalence Partitioning

Progress is saved on this browser only. It is not linked to your account and other devices will not see it.