Test-plan generator

What CLARA will ask you for

• Programme name — your programme's name (e.g. SKYPROTECT).
• Track — the slice of the programme this artefact belongs to (workstream, capability area, feature line, etc.), or Programme-wide if it spans tracks.
• Test type — what kind of test this is. Examples: usability test on interactive prototype, moderated walk-through of a clickable prototype with operators, instrumented A/B on a deployed feature, capability rehearsal in scripted exercise.
• Test name — short (e.g. "Console-v1-usability-test", "Tank-crew-alerting-rehearsal").
• Test focus (optional) — describe what this round of testing should cover. Leave blank to test against all the artefact's success criteria. Otherwise narrow the scope: a specific user story (e.g. "submit-incident-report"), one or two success criteria, the features shipping in this PI, or the storyboard beats being rehearsed.
• Constraints (optional) — time budget, recruiting limits, environment, classification, secrecy.
• Inputs — CLARA will search the programme's Confluence space for relevant artefacts; success criteria; field notes for scenario seeding (optional). You can also paste fresh material if it's not in Confluence yet.

Where the output lands

Knowledge Base/{{track}}/Test-plans/{{test-name}} inside your programme's Confluence space.

Tips

• The Objective sentence is the test of the test plan. CLARA proposes it before drafting the rest and waits for your confirmation — if she can't compress it to one line, treat that as a signal to narrow the test focus and rerun.
• When you review CLARA's scenarios, each should map to a success criterion. If a scenario can't fail, it isn't a test — ask CLARA to rework it.