Getting one person productive in Studio takes an afternoon. Getting a team to the point where they agree on what a test is for takes about a week — and it is the second one that decides whether the program is still running in six months.
This is a five-day plan that uses material already on this site. It assumes people have day jobs: roughly ninety minutes a day, with two sessions that need everyone in the same room or call.
One person does the environment work: access confirmed, a project created, and one test that passes. Do this in advance. A kickoff that turns into a debugging session teaches the wrong lesson and costs you the room.
Day 1 — Build something that runs
Together, 60 minutes. Everyone does Exercise 1 - Create Your First Test From a Prompt and Exercise 2 - Write Assertions That Prove Something against the demo store. Nobody touches your own application yet.
Alone, 30 minutes. Read Your First 30 Minutes with Functionize Studio and the Studio Essentials flash-card deck.
The point of the day: everyone has watched a plain-English sentence become something that runs. Discussion about strategy goes better after that than before it.
Day 2 — Read a result properly
Alone, 60 minutes. Exercise 3 - Read a Test Run and Its Evidence and Exercise 5 - Break a Test on Purpose, Then Diagnose It. Breaking something deliberately is the fastest way to learn what the evidence is telling you.
Alone, 20 minutes. The Quality Engineering Fundamentals deck. Several of these definitions will be mildly surprising, which is the useful part.
Day 3 — Decide what is worth automating
Together, 90 minutes. This is the session that matters. Read What Makes a Good Automation Candidate beforehand, then fill in sections 2, 4 and 5 of the Master Test Strategy Template as a group: what you test manually today, your critical journeys, and what you will automate.
Expect ninety minutes and expect disagreement. Teams routinely discover here that the tests they have and the journeys they care about are not the same list.
Day 4 — Make it a gate
Alone, 45 minutes. Exercise 6 - Group Tests Into an Orchestration, then read Keeping a Suite Green: Flake, Tiers and Who Owns Red.
Together, 20 minutes. Agree three things and write them down: which tests gate what, who reads a red result, and by when. A suite nobody is accountable for stops being read within a month.
Day 5 — Agree the vocabulary, and the baseline
Together, 60 minutes. Run Check Yourself: Twenty Questions on Testing With AI as a group. Read each question aloud, let people answer, then open the card. Where two people answer differently you have found something to settle.
Together, 30 minutes. Write down the baseline: escaped defects last quarter, manual regression hours per release, which critical journeys are covered today. Put the date on it. This is the half hour people skip and later wish they had not.
One passing test per person, an orchestration that runs on a schedule, three sections of a written strategy, a named owner for red results, and a dated baseline. That is a program. Everything after it is extension.
If you only have one day
Do day 1 in the morning and day 3 in the afternoon. Building something and deciding what is worth building are the two irreplaceable halves; the rest can be picked up as you go.
The material, in one place
| Hands-on | The seven-part exercise series, against a demo store that needs no sign-in. Each one has a printable lab handout. |
| Vocabulary | Flash Cards: The Vocabulary Your Team Needs — five decks, readable in the browser or printable as cut-out cards. |
| Self-check | Check Yourself: Twenty Questions on Testing With AI — twenty questions with answers, designed to be run with a team rather than alone. |
| Reference | AI Testing and AI-DLC: A Glossary for definitions with primary sources, and Frequently Asked Questions for the things people ask in week one. |
| Documents | Test Strategy Templates You Can Use Today — four strategy documents in Word and PDF, free to edit and put your own name on. |