Card #1. Q1.

What is a critical bug? Explain the bug life cycle or the different states of a bug.

A critical bug is a bug that impacts a major functionality of the application and the applica-
tion cannot be delivered without fixing the bug. It is different from the blocker bug as it doesn’t af-
fect or blocks the testing of other parts of the application.
A critical bug questions the very foundation of a given quality attribute like functionality,
performance, security etc. for the software.
The Bug Life Cycle, is a cycle of defects from which it goes through covering the different
states in its entire life. This starts as soon as any new defect is found by a tester and comes to an end
when a tester closes that defect assuring that it won’t get reproduced again.
Defect Life Cycle States:
New - Potential defect that is raised and yet to be validated.
Assigned - Assigned against a development team to address it but not yet resolved.
Active - The Defect is being addressed by the developer and investigation is under progress.
At this stage there are two possible outcomes; viz - Deferred or Rejected.
Test - The Defect is fixed and ready for testing.
Verified - The Defect that is retested and the test has been verified by QA.
Closed - The final state of the defect that can be closed after the QA retesting or can be clo-
sed if the defect is duplicate or considered as NOT a defect.
Reopened - When the defect is NOT fixed, QA reopens/reactivates the defect.
Deferred - When a defect cannot be addressed in that particular cycle it is deferred to future
release.
Rejected - A defect can be rejected for any of the 3 reasons; viz - duplicate defect, NOT a
Defect, Non Reproducible.

Card #1. Q2.

Explain equivalence class partitioning.

Equivalence class partitioning (ECP). It is a software testing technique or black-box testing

that divides input domain into classes of data, and with the help of these classes of data, test cases
can be derived. An ideal test case identifies class of error that might require many arbitrary test ca-
ses to be executed before general error is observed.
In equivalence partitioning, equivalence classes are evaluated for given input conditions.
Whenever any input is given, then type of input condition is checked, then for this input conditions,
Equivalence class represents or describes set of valid or invalid states.
Guidelines for Equivalence Partitioning :
If the range condition is given as an input, then one valid and two invalid equivalence classes
are defined.
If a specific value is given as input, then one valid and two invalid equivalence classes are defi-
ned.
If a member of set is given as an input, then one valid and one invalid equivalence class is defi-
ned.
If Boolean no. is given as an input condition, then one valid and one invalid equivalence class is
defined.