Bug life cycle and writing bug reports
Severity vs priority, the stages a bug moves through, and a bug report developers can act on.
A bug report is only useful if a developer can reproduce the problem quickly. Clear reports get fixed faster.
Fields of a good bug report
- Title — what fails, where, under which condition.
- Environment — app version, browser/device, OS, test environment.
- Steps to reproduce — numbered and minimal.
- Expected vs actual result.
- Severity and priority.
- Attachments — screenshot, screen recording, logs.
Severity vs priority
Severity is the impact on the system (set by QA): critical, major, minor, trivial. Priority is how soon it must be fixed (usually set by the product owner). A spelling mistake in the company name on the home page is low severity but high priority; a crash in a rarely used admin report may be high severity but lower priority.
Bug life cycle
New → Assigned → Open (in progress) → Fixed → Retest → Closed. Side paths: Rejected (not a bug), Duplicate, Deferred (fix later) and Reopened (fix didn't work).
Example
Practise on any app you useBUG-2041 Cart total ignores discount when quantity changed after coupon
Environment: Web v3.8.1, Chrome 131, Windows 11, QA server
Severity: Major Priority: High
Steps: 1. Log in as test user qa_01 2. Add "Steel Bottle" (₹500) to cart 3. Apply coupon SAVE10 (10% off) → total shows ₹450 ✔ 4. Change quantity from 1 to 2
Expected: Total ₹900 (₹1,000 − 10%)
Actual: Total ₹1,000 — discount line disappears
Reproducible: 5/5 times
Attachments: cart-bug.mp4, console-log.txt
What to notice
• The title says what, where and when — a developer understands it without opening the report.
• Steps are minimal and start from a known state (logged-in user).
• "5/5 times" and the video remove doubt about reproducibility.
• Expected vs actual uses exact values, not "wrong total".
Apps, IDs and data are fictional examples written for practice.
Key points
- Reports must be reproducible.
- Severity = impact; priority = urgency.
- Exact expected vs actual values.
- Attach evidence: screenshots, videos, logs.
Quick check
A typo in the company name on the home page is usually…
It doesn't break functionality (low severity) but is highly visible and damages trust, so it is fixed quickly (high priority).
Practice task
Find a small real bug or UX issue in any website and write a full bug report for it using the fields above.
Interview corner
The developer says your bug is 'not reproducible'. What do you do?
Recheck the environment and data, record a video, share exact versions and logs, and if needed reproduce it together. Stay factual, not defensive.
What is a 'Deferred' bug?
A valid bug the team agrees to fix in a later release, usually because it is low impact or the fix is risky close to a deadline.
Original lesson written by the InfoparkDaily team · © 2026 InfoparkDaily · Free to learn — no paid course or subscription.