Requirements: turning a wish into a testable statement · seed 1 · A4, ink-friendly. The answer key prints on its own page for grown-ups.

Turning foggy wishes into checkable promises

Computing · Software Engineering · ages 19-20
Name ______________________   Date ____________

  1. Which statement describes a functional requirement for catalog search?

    • Return catalog titles that match the user's search text.
    • Display search results within the agreed response-time limit.
    • Keep search available for the agreed share of the test period.

  2. Plan P fixes the browser, network profile, dataset and query list. Which statement adds an observable pass criterion for search speed?

    • Under plan P, make search feel quick and comfortable for everyone who uses it.
    • Under plan P, show all search results within four seconds of selecting Search.
    • Under plan P, show search results whenever the page seems ready to display them.

  3. An agreed test query matches no records. The requirement says to display 'No matches' in that case. A tester can check it without a numeric threshold.

    Circle one:   True   False

  4. Two draft rules cover the same guests at the same time. One sets their maximum books on loan to six. The other sets that same maximum to three. What should review flag?

    • A conflict between two maximums for the same guests in the same circumstances.
    • A function and a speed target that describe separate aspects of guest borrowing.
    • A scope boundary separating what guests can borrow from what staff can borrow.

  5. A client asks you to make checkout easy. No users, task or acceptance check have been agreed. What should you do next?

    • Choose a layout that you expect customers to like, then call checkout easy to use.
    • Start coding checkout from your own preferences, then decide what easy means later.
    • Ask which users and task to test, and agree the pass criterion and conditions.

  6. A shop requires each checkout product photo to have a text alternative naming the pictured product. Which check tests this requirement?

    • Check that each photo has a nonempty alternative, whatever those words say.
    • Review whether each photo's text alternative names the product it shows.
    • Count all product photos without reading any of their text alternatives.

  7. A draft says 'Handle many active users quickly.' The test plan fixes the browser, network profile, dataset and measurement method. Which two limits are still needed?

    • The active-user count and response-time limit for the agreed test conditions.
    • The adjective used to describe speed and the preferred colour of the page header.
    • The programming language and the name of the person who wrote the draft statement.

  8. An agreed borrow-only release excludes book sales to avoid payment work. A new sales requirement has no linked need. What should review do?

    • Approve the sales feature because any additional function must help the release.
    • Move the sales feature into an appendix and keep it in the release without review.
    • Check the need with stakeholders and reconcile it with the agreed release scope.
LightMySky · lightmysky.comW1-mt_TFb-YNpvT1-s1

Answer key

For grown-ups. Fold this page away before handing over the rest.

Turning foggy wishes into checkable promises W1-mt_TFb-YNpvT1-s1

  1. Return catalog titles that match the user's search text. · Returning matching titles describes the service the system provides. The other statements set response-time and availability qualities for that service.
  2. Under plan P, show all search results within four seconds of selecting Search. · The four-second statement defines a timing limit and its start and end events. Plan P supplies the test conditions. Feel quick and seems ready leave the pass criterion undefined.
  3. True · The query supplies a known condition. Comparing the displayed message with 'No matches' gives an observable check without a number.
  4. A conflict between two maximums for the same guests in the same circumstances. · The rules define the same maximum under the same conditions. That maximum cannot be both six and three. The team must agree which limit applies.
  5. Ask which users and task to test, and agree the pass criterion and conditions. · Easy does not identify a test. Agreeing the users, task, pass criterion and conditions turns the request into something the team can check.
  6. Review whether each photo's text alternative names the product it shows. · The requirement concerns the meaning of the text alternative. A reviewer must compare its wording with the pictured product. Presence alone is insufficient.
  7. The active-user count and response-time limit for the agreed test conditions. · Many gives no active-user count, and quickly gives no response-time limit. The test plan supplies the other stated conditions and measurement method.
  8. Check the need with stakeholders and reconcile it with the agreed release scope. · The proposal lacks a need link and falls outside the release boundary. Review its justification, then reject an unsupported proposal or agree whether justified work should be deferred or included through a scope change.
Worksheet · LightMySky