QuestionQ15

VerifiedTest Analysis and Test Design

Your organization is implementing a food-ordering application that is intended to have an intuitive user interface (easy navigation and fast search) and to offer functions such as:

  • personalization of the order (the ability to modify ingredients and add comments for the restaurant)
  • verification of order correctness before it is sent
  • real-time order tracking
  • viewing order history

Management has decided to test the requirements listed above with a checklist and has asked you to prepare one. Consider the following four checklists.

Checklist 1 -

[ ] Does the system reject an order with an incorrect zip code?

[ ] Does the system reject an order with an unfilled mandatory field?

Checklist 2 -

The interface allows the user to easily navigate the application (YES / NO / PARTIALLY)

The search function allows the user to quickly search for restaurants (YES / NO / PARTIALLY)

Checklist 3 -

[ ] Is the time from order placement to order confirmation less than 10s?

[ ] Is the user interface free of grammatical errors?

Checklist 4 -

The application works properly on the Android operating system (YES / NO)

The application works properly on the iOS operating system (YES / NO)

Which of the following is an example of a read-do checklist that is useful for testing the application described in the scenario?

Explanation

A read-do checklist contains concrete, actionable elements to execute during a process, such as specific invalid inputs to check. Rejecting orders with an incorrect ZIP code or an unfilled required field provides directly testable negative-input checks supporting order validation before submission.

Learn more

Community Discussion

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