Testers, Quality Engineers, Product Owners and Designers

All courses / AI Developer / Module 3 / Chapter 17

Learning objectives

After the lesson the participant can:

• Explain how the tester's role shifts in weight from writing test code to owning the verification plan and exploring
• Apply the four-part test of an oracle's independence: source, author, seeded faults and age
• Explain the rule that a prototype is a question and not an answer, and its three conditions
• Draft a role-boundary matrix that marks which boundaries move and which are fixed

Key concepts

Four-part test of independence

Independence has to be shown and not asserted. Source: written from the specification record and independent evidence. Author: someone other than the author of the change, and not the generator. Seeded faults: known faults are injected and caught. Age: the evidence carries a date and expires, by default after 90 days.

A prototype is a question

Product owners and designers can now build running prototypes. The rule the book proposes is that a prototype is a question and not an answer: it is labelled, built on synthetic data and never promoted as code.

Quality as an independent voice

The quality function stays independent only if it has access to evidence, the authority to hold a release at a defined gate, and a measure of success that is not delivery speed. Quality is reported by team, service and oracle, never as a count per named tester.

Role-boundary matrix

A record for one team of who frames, builds, proves and owns each kind of work, what AI may do in it and what is fixed. It is an annex to the role charters and the delegation profile, and carries no Level 4 for any class of work.

Interactive exercises

Do them here and get feedback at once. Choose a card and then where it belongs, or drag it.

Teaching plan

Discussion

1. In both organisations one person asks, of any proposal to let an assistant write tests, who writes the oracle. Who asks that question in your team, and with what authority?
2. A product owner builds a running prototype in an afternoon. What stops it from being promoted as code when it already seems to work?
3. Measurement tied to reward invites distortion. How should the quality function itself be measured if not by delivery speed or defects per tester?

Written exercise

Self-test

Choose an answer to see whether it is right, or open the answer below each question.

1. According to the table of where the boundary moves, what must not move for the activity hold or revert a release?

   1. The release manager approves every hold in advance of the release window
   2. The pipeline acts on the basis of canary analysis alone
   3. The product owner signs the specification record
   4. The authority to hold or revert sits outside the pipeline
   Show the answer

   D. The authority to hold or revert sits outside the pipeline
   For hold or revert under D5 Steward, the quality engineer may hold and the owner reverts; the fixed point is that the authority sits outside the pipeline.

2. What default expiry does the book use for verification evidence in the four-part test?

   1. 30 days by the clock, or at the end of the sprint if that is sooner
   2. 90 days by the clock, and earlier when the conditions change
   3. 180 days by the clock, the same default as for value claims
   4. One year, reviewed together with the delegation profile
   Show the answer

   B. 90 days by the clock, and earlier when the conditions change
   The age part of the test says the evidence carries a date and expires: by clock, with 90 days as the book's default for verification evidence, and by event such as a change of generator model, module or specification.

3. How does the chapter label the claim that testing as a role will end because models write tests?

   1. Speculation: no study reviewed for the chapter shows it
   2. Observable: test drafting is already in use at Hansa Mutual
   3. Expected: the trend in test generation supports it
   4. Measured: the Meta field report demonstrates it
   Show the answer

   A. Speculation: no study reviewed for the chapter shows it
   The outlook calls it speculation: no study reviewed shows it, and the chapter instead expects independent quality functions to grow in importance where much code is generated.