What constitutes a valid test case in Trusted Tester?

• A. A single informal observation.
• B. A step-by-step, repeatable, verifiable scenario with expected outcomes and acceptance criteria.
• C. A list of features without steps.
• D. A random collection of defects.

Answer: (B)

A valid test case describes a specific scenario in enough detail that any tester can reproduce it exactly. It should present a step-by-step sequence, specify the input data and preconditions, define the environment, and state the expected results. Alongside the expected results, there are acceptance criteria that determine when the test has passed. This structure makes the test repeatable and verifiable: you can run it again in the same conditions, compare what actually happened with what was expected, and show that the outcome meets the defined criteria. In Trusted Tester, this clarity also helps tie the test back to a requirement or user goal, ensuring traceability.

Informal observations lack the repeatable steps and defined outcomes needed to verify behavior. A list of features without steps doesn’t show how to exercise them or what constitutes a pass. A random collection of defects isn’t a cohesive test case; it doesn’t provide the planned actions, expected results, or acceptance criteria needed to validate functionality consistently.