Sample questions
Qa Test Case DesignDifficulty 1
What is the core idea behind equivalence partitioning as a test design technique?
- aGrouping inputs into classes with the same expected behavior, then testing one representative per class✓
- bRunning every possible input value at least once to guarantee full coverage
- cTesting only the values that caused defects in a previous release
- dRandomly generating inputs until a fixed test budget is exhausted
Explanation:Equivalence partitioning assumes inputs within the same class trigger the same behavior, so one representative value per class is enough to catch class-level defects, which keeps the test set small without giving up meaningful coverage.
Qa Test Case DesignDifficulty 1
What does boundary value analysis focus on?
- aChoosing the input that appears most frequently in production logs
- bValues at, just below, and just above an equivalence class boundary✓
- cThe average value of an input range, since that is statistically most common
- dCombinations of every field on a form tested together at once
Explanation:Boundary value analysis targets the edges of a valid range (min, min-1, max, max+1 and similar) because defects such as off-by-one errors concentrate there far more than in the middle of a range.
Qa Test Case DesignDifficulty 1
What is negative testing, as opposed to positive testing?
- aTesting performed only after a defect has already reached production
- bTesting that measures how slow the system is under normal load
- cFeeding invalid or malformed input to verify the system rejects it gracefully✓
- dTesting carried out exclusively by a separate team that did not build the feature
Explanation:Negative testing checks that the system handles invalid, unexpected, or out-of-range input gracefully (clear error, no crash, no corrupted state), complementing positive testing which confirms correct behavior for valid input.
Qa Test Case DesignDifficulty 1
When is a decision table the most natural test design tool to reach for?
- aWhen there is a single input field with a simple valid/invalid split
- bWhen testing needs to cover a sequence of screens in a fixed order
- cWhen the goal is only to measure response time under load
- dWhen the expected output depends on several independent conditions combined together✓
Explanation:Decision tables map combinations of conditions to the resulting actions, which makes them the right fit when several independent factors jointly determine the outcome (e.g., customer type, order amount, region all affecting a discount rule).
Qa Test Case DesignDifficulty 1
What does state transition testing verify?
- aThat the system moves correctly between states and rejects disallowed transitions✓
- bThat every database column has a not-null constraint
- cThat the user interface renders identically on every screen resolution
- dThat response time stays below a fixed threshold under peak load
Explanation:State transition testing models the system as a set of states and the events/transitions allowed between them, then checks both valid transitions (the state changes as expected) and invalid ones (a disallowed transition is correctly refused).
Qa Test Case DesignDifficulty 1
In equivalence partitioning, what is an equivalence class?
- aA test case that has been executed and passed in the previous release
- bA subset of the input domain, valid or invalid, treated identically by the system✓
- cA group of testers assigned to the same feature
- dThe set of all inputs that produced a defect in a bug-tracking system
Explanation:An equivalence class groups inputs the system should treat the same way; classes include both valid ranges (e.g., age 18-65) and invalid ranges (e.g., negative age, age above a cap), and each class needs only one representative test.