A developer removes the HTML class attribute from the checkout button, so now it is simply:
<button>Checkout</button>
There is a test to verify the existence of the checkout button, however it looks for a button with class="blue". The test fails because no such button is found.
Which type of test category describes this test?
Correct Answer: D
Definitions in testing context (treating "positive" as "test reports a bug/failure"):
True positive: System has a bug; test correctly fails.
False positive: System is correct; test fails (reports a bug that isn't actually a bug).
True negative: System has a bug; test correctly passes indicating "no success" in detection context (less common phrasing here).
False negative: System has a bug; test incorrectly passes (missed bug).
Here:
The real requirement, as stated, is to verify the existence of the checkout button.
The button still exists (<button>Checkout</button>), so the system behavior is correct regarding that requirement.
The test, however, is checking for an overly specific condition (class="blue"), which is not actually part of the stated requirement.
The test fails, saying there is a problem (no button with class="blue"), even though from the requirement standpoint, the checkout button is present.
So:
No real bug concerning presence of checkout button.
Test reports a failure → a false positive.
Therefore, the correct category is D, False positive.