QuestionQ75

VerifiedTest Analysis and Test Design

You have been given the following high-level checklist for testing the account balance functionality of an ATM:

  1. Does valid login work and invalid login fail? (valid/invalid account/password pairs)
  2. Are all accounts displayed and selectable?
  3. Does the screen meet the UI standards?
  4. Can you pick one account and view the balance?
  5. Is the balance consistent with the database?
  6. Do you have a variety of ways to exit (logout, walk away, check timeout)?
  7. Does exiting disconnect the session?

What other information should be added to the checklist?

Explanation

A complete test case or checklist item must specify the expected result for each check so that the actual outcome can be objectively compared against it to determine pass or fail. Without stated expected results, items such as "Does valid login work?" or "Is the balance consistent with the database?" are ambiguous about what constitutes success, making the checklist unusable for reliable, repeatable testing. Tester name/date, known defects, and screenshots are execution-record or reporting details added when running or logging the test, not core elements of the test design itself.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!