Bug Definition and Example
Bug/Defect questions
What is a bug?
What is a Bug?
A bug is an error or defect in software that causes the application to behave differently from the
expected result.
Simple definition for interview:
“A bug is a problem in software where the actual result does not match the expected result.”
Example:
Suppose a login page requires a valid password to log in. You enter the correct username and password,
but the application shows “Invalid password.”
This is a bug because the actual result is different from the expected result.
Interview tip:
You can also say:
“A bug is an issue found during testing where the software does not work according to the
specified requirements.”
What is the bug life cycle?
What is the Bug Life Cycle?
The Bug Life Cycle is the sequence of stages a bug goes through from the time it is identified and
reported until it is closed.
Common Bug Life Cycle
New → Assigned → Open → Fixed → Retest → Verified → Closed
Status Meaning
New Tester finds and reports a new bug.
Assigned Bug is assigned to a developer/team for fixing.
Printed using ChatGPT to PDF, powered by PDFCrowd HTML to PDF API. 1/3
Status Meaning
Open Developer starts analyzing the bug.
Fixed Developer fixes the issue and sends it for testing.
Retest Tester tests the bug again to check whether it is fixed.
Verified Tester confirms that the bug has been successfully fixed.
Closed Bug is closed after successful verification.
Other possible statuses
Depending on the organization/tool, you may also see:
Rejected – Developer determines that it is not a valid bug.
Duplicate – The same bug has already been reported.
Deferred – Bug will be fixed in a future release.
Not a Bug / As Designed – The behavior is intentional.
Reopened – Bug still exists after the developer marked it as fixed.
Interview Answer
“The Bug Life Cycle is the series of stages through which a bug passes from
identification to closure. Generally, it starts with New, then Assigned, Open, Fixed,
Retest, Verified, and finally Closed. If the bug is not fixed properly, the tester can
Reopen it.”
"What happens if a developer says your bug isn't a bug?"
What happens if a developer says your bug isn't a bug?
This is a common interview question. The best answer is to show that you don't argue—you verify the
issue with evidence and requirements.
Interview Answer
“If a developer says that my reported issue is not a bug, I would first verify the issue
against the requirements or expected behavior. I would reproduce the issue and
provide evidence such as screenshots, logs, test data, or steps to reproduce. I would
discuss it with the developer and understand their reasoning. If the behavior is actually
as per the requirement, I would close the bug as ‘Not a Bug’ or update its status
accordingly. If I still believe it violates the requirements, I would involve the BA, product
owner, or senior QA for clarification.”
Simple Example
Suppose you report:
Bug: Login button remains disabled when the password is only 5 characters.
Printed using ChatGPT to PDF, powered by PDFCrowd HTML to PDF API. 2/3
Developer says: “It's not a bug.”
You would:
1. Check the requirement.
2. Verify the minimum password length.
3. Reproduce the issue.
4. Share screenshots/test data with the developer.
5. Discuss it with the developer.
6. If the requirement says minimum 6 characters, it's a valid bug.
7. If the requirement says minimum 8 characters, then the behavior may be correct and the bug
should be closed as Not a Bug.
⭐ Key point for interview
Don't say:
❌ “I will argue with the developer.”
Instead say:
✅ “I would use the requirements and evidence to determine whether it is actually a
defect.”
This demonstrates professional communication, requirement understanding, and logical problem-
solving.
ChatGPT can make mistakes. Check important info.
Printed using ChatGPT to PDF, powered by PDFCrowd HTML to PDF API. 3/3