From 7ea347022e0615ecfadab144ab5e558c17c5e97a Mon Sep 17 00:00:00 2001 From: DavertMik Date: Sat, 7 Nov 2026 14:30:11 +0200 Subject: [PATCH] Plan a website's main user flow first The Planner's guidance is built around create, update and delete, and it only planned capabilities visible in research. A shop's cart and checkout got no tests, while sign-in and filters filled the plan. The Planner now decides what the website is for and plans that outcome end to end first, using hints for common flows. Unseen steps of the main flow are described by goal and left for the Tester to find at run time. Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 5 +++++ src/ai/planner.ts | 14 +++++++++++++- 2 files changed, 18 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 1d585e79..901a0a2d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,10 @@ # Changelog +## 2026-11-07 + +### Changes +- [Planner] Works out what a website is for and plans its main user flow first, such as buying or reserving, managing records, communicating, multi-step applications or reporting. Steps of that flow that are not visible yet are still planned. Sign-in, FAQ and support pages come afterwards, unless they are the main flow. + ## 2026-11-06 ### Changes diff --git a/src/ai/planner.ts b/src/ai/planner.ts index c44ccfb8..ee374c27 100644 --- a/src/ai/planner.ts +++ b/src/ai/planner.ts @@ -377,6 +377,18 @@ export class Planner extends PlannerBase implements Agent { Exception: if the page reports the requested resource is missing, shows a failure state, or holds no content and no controls, return an empty scenarios list. Never invent tests for a page with nothing to exercise.${ignoredPagesRule} + + First decide what this website is for and which business outcome its users come for. Unless a focus was requested, plan that outcome end to end before anything else. + Common main flows: + - Buying or reserving (shops, marketplaces, booking, listings): find an item, choose options, add it to the cart or select it, check out or confirm, see the confirmation. + - Managing records (SaaS, admin): create, update, delete. + - Communicating (chat, social, community): post or send, see it appear, reply, react. + - Multi-step applications (claims, onboarding, enrollment): complete each step, submit, track the status. + - Reporting (dashboards, analytics): change the period or grouping, drill into a number, export. + Sign-in, FAQ and support pages are supporting features: cover them after the main flow, unless they are the main flow. + Steps of the main flow may be unseen yet. Describe them by goal; the tester finds the controls at run time. For these steps this overrides and the rules requiring evident prerequisites or observed interface details. + + Scenarios must involve interaction with the web page (clicking, scrolling or typing). Scenarios must focus on business logic and functionality of the page. @@ -643,7 +655,7 @@ export class Planner extends PlannerBase implements Agent { Cover sections in this order — first propose tests for elements from earlier sections, then later ones. Extended Research sections come after the main sections. 3. Focus on interactive elements of the page. Skip navigation links that lead away from current page. - 4. Focus on tests you are 100% sure relevant to this page and can be achived from UI. + 4. Focus on tests relevant to this page and achievable from UI. 5. For each task, provide BOTH steps and expected outcomes as separate lists: STEPS - actionable commands: