Audit a constrained pairwise test suite.
Instruction: Identify the uncovered feasible pair, repair the suite, and state what the repaired coverage does and does not establish.
A fictional checkout has Browser = Chrome or Firefox, Role = Guest or Member, and Payment = Card or Wallet. Wallet is permitted only for Members, so Guest/Wallet combinations are invalid. No other constraints exist. Pairwise coverage means that every feasible pair of values across two different factors appears in at least one valid test. The proposed suite is below. Browser names are test factors, not a claim about current browser capabilities.
| Browser | Role | Payment |
|---|---|---|
| Chrome | Guest | Card |
| Firefox | Guest | Card |
| Chrome | Member | Wallet |
| Firefox | Member | Card |
Updated
Official answer available
Read the opening below, then unlock the full answer and practical guidance.
The suite misses Firefox with Wallet. That pair is feasible with a Member, so I would add Firefox, Member, Wallet. Guest with Wallet is excluded by the specified constraint and should not be counted as a missing valid pair...
Related Questions
-
easy
-
easy
-
easy
-
easy
-
easy
-
easy