Command to draft and save a Playwright scenario plan in docs/test-plan/
Generates Playwright test plans and saves them to docs/test-plan/ based on feature code analysis.
/plugin marketplace add venturo-id/venturo-claude/plugin install venturo-e2e-web@venturo-toolsCommunication Style: Casual, professional Bahasa Indonesia.
TODOS for each instructions below.Think to execute step by step :
Determine the feature path in the codebase:
src/features/user), Never scan codebase or continue the process if user did not give the feature path.feature name base on feature path (e.g., src/features/user it mean feature name = user).Determine the context test scenario:
After get context test scenario and feature path from user, Delegate to codebase-explorer to gather context:
codebase-explorer:
I need you to systematically explore the codebase for the <context test scenario> located at <feature path> to gather comprehensive context for
creating test plans.
Please collect the following information:
1. List all components, forms, and UI elements in the <feature path>
2. Identify application routes related to <context test scenario> functionality
3. Extract props, attributes, and file structure,
4. Do not use assumption for three point above, all information must base on codebase.
5. **MOST IMPORTANT**: Use "Logic to collect data-testid" from `collect-selector` skill and Think step-by-step to resolve the correct value for `data-testid`
Please provide a comprehensive analysis of:
- Component structure and hierarchy
- Form elements and their data-testid values
- Buttons, links, and interactive elements
- Input fields and validation
- API endpoints and services
- Any existing test files or test-related configurations
Focus on gathering all the necessary context to create end-to-end test scenarios for the user feature.
Mandatory think step-by-step to re-validate and resolve the correct value for data-testid for each UI element found by the codebase-explorer agent using "Logic to collect data-testid" from collect-selector skill.
Based on the context, propose 3–7 candidate scenarios with the fields: | ID | Title | Component Path | Route | Priority | Tags |
SCN-<sequential from 001> as Code / Scenario IDUse the plan-document skill to generate the full Markdown test plan for each scenario (1 scenario = 1 document).
Flow: Save the file:
docs/test-plan/
ls -la docs/test-plan/ If you find a duplicate <feature name>, Propose to create version directory docs/test-plan/<feature name>-v-*.docs/test-plan/<feature name>/<Code>-<short-scenario-slug>.mdAfter all scenarios are saved, close the session with:
"All plans have been saved in docs/test-plan/<feature name>/ and are ready for /venturo-e2e-web:generate."