[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71PV8ATNFM34PX3TQN9FQGZ":3,"skill-same:01M71PV8ATNFM34PX3TQN9FQGZ":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":14,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M71PV8ATNFM34PX3TQN9FQGZ","bmad-qa-generate-e2e-tests",null,"Generate end to end automated tests for existing features. Use when the user says \"create qa automated tests for [feature]\"","jsacko\u002FOpenDFIR","jsacko","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63580474?v=4","01M71PG17HH9PJ0ME3103K2MF5","Julien Sacko","01M71PG188SHJ0DBAYX85237WG",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002F.continue\u002Fskills\u002Fbmad-qa-generate-e2e-tests\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"e2e","qa","bmad","generate","e2e tests","bmad qa","bmad qa generate e2e tests","generate e2e tests","tests","user","features","create","when","Existing","use","end","for","feature","2026-11-10 13:02:02",false,"---\nname: bmad-qa-generate-e2e-tests\ndescription: 'Generate end to end automated tests for existing features. Use when the user says \"create qa automated tests for [feature]\"'\n---\n\n# QA Generate E2E Tests Workflow\n\n**Goal:** Generate automated API and E2E tests for implemented code.\n\n**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use the `bmad-code-review` skill for that).\n\n## Conventions\n\n- Bare paths (e.g. `checklist.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve:\n\n- `project_name`, `user_name`\n- `communication_language`, `document_output_language`\n- `implementation_artifacts`\n- `date` as system-generated current datetime\n- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Paths\n\n- `test_dir` = `{project-root}\u002Ftests`\n- `source_dir` = `{project-root}`\n- `default_output_file` = `{implementation_artifacts}\u002Ftests\u002Ftest-summary.md`\n\n## Execution\n\n### Step 0: Detect Test Framework\n\nCheck project for existing test framework:\n\n- Look for `package.json` dependencies (playwright, jest, vitest, cypress, etc.)\n- Check for existing test files to understand patterns\n- Use whatever test framework the project already has\n- If no framework exists:\n  - Analyze source code to determine project type (React, Vue, Node API, etc.)\n  - Search online for current recommended test framework for that stack\n  - Suggest the meta framework and use it (or ask user to confirm)\n\n### Step 1: Identify Features\n\nAsk user what to test:\n\n- Specific feature\u002Fcomponent name\n- Directory to scan (e.g., `src\u002Fcomponents\u002F`)\n- Or auto-discover features in the codebase\n\n### Step 2: Generate API Tests (if applicable)\n\nFor API endpoints\u002Fservices, generate tests that:\n\n- Test status codes (200, 400, 404, 500)\n- Validate response structure\n- Cover happy path + 1-2 error cases\n- Use project's existing test framework patterns\n\n### Step 3: Generate E2E Tests (if UI exists)\n\nFor UI features, generate tests that:\n\n- Test user workflows end-to-end\n- Use semantic locators (roles, labels, text)\n- Focus on user interactions (clicks, form fills, navigation)\n- Assert visible outcomes\n- Keep tests linear and simple\n- Follow project's existing test patterns\n\n### Step 4: Run Tests\n\nExecute tests to verify they pass (use project's test command).\n\nIf failures occur, fix them immediately.\n\n### Step 5: Create Summary\n\nOutput markdown summary:\n\n```markdown\n# Test Automation Summary\n\n## Generated Tests\n\n### API Tests\n- [x] tests\u002Fapi\u002Fendpoint.spec.ts - Endpoint validation\n\n### E2E Tests\n- [x] tests\u002Fe2e\u002Ffeature.spec.ts - User workflow\n\n## Coverage\n- API endpoints: 5\u002F10 covered\n- UI features: 3\u002F8 covered\n\n## Next Steps\n- Run tests in CI\n- Add more edge cases as needed\n```\n\n## Keep It Simple\n\n**Do:**\n\n- Use standard test framework APIs\n- Focus on happy path + critical errors\n- Write readable, maintainable tests\n- Run tests to verify they pass\n\n**Avoid:**\n\n- Complex fixture composition\n- Over-engineering\n- Unnecessary abstractions\n\n**For Advanced Features:**\n\nIf the project needs:\n\n- Risk-based test strategy\n- Test design planning\n- Quality gates and NFR assessment\n- Comprehensive coverage analysis\n- Advanced testing patterns and utilities\n\n> **Install Test Architect (TEA) module**: \u003Chttps:\u002F\u002Fbmad-code-org.github.io\u002Fbmad-method-test-architecture-enterprise\u002F>\n\n## Output\n\nSave summary to: `{default_output_file}`\n\n**Done!** Tests generated and verified. Validate against `.\u002Fchecklist.md`.\n\n## On Complete\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete`\n\nIf the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.\n","# QA Generate E2E Tests Workflow\n\n**Goal:** Generate automated API and E2E tests for implemented code.\n\n**Your Role:** You are a QA automation engineer. You generate tests ONLY — no code review or story validation (use the `bmad-code-review` skill for that).\n\n## Conventions\n\n- Bare paths (e.g. `checklist.md`) resolve from the skill root.\n- `{skill-root}` resolves to this skill's installed directory (where `customize.toml` lives).\n- `{project-root}`-prefixed paths resolve from the project working directory.\n- `{skill-name}` resolves to the skill directory's basename.\n\n## On Activation\n\n### Step 1: Resolve the Workflow Block\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow`\n\n**If the script fails**, resolve the `workflow` block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:\n\n1. `{skill-root}\u002Fcustomize.toml` — defaults\n2. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.toml` — team overrides\n3. `{project-root}\u002F_bmad\u002Fcustom\u002F{skill-name}.user.toml` — personal overrides\n\nAny missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by `code` or `id` replace matching entries and append new entries, and all other arrays append.\n\n### Step 2: Execute Prepend Steps\n\nExecute each entry in `{workflow.activation_steps_prepend}` in order before proceeding.\n\n### Step 3: Load Persistent Facts\n\nTreat every entry in `{workflow.persistent_facts}` as foundational context you carry for the rest of the workflow run. Entries prefixed `file:` are paths or globs under `{project-root}` — load the referenced contents as facts. All other entries are facts verbatim.\n\n### Step 4: Load Config\n\nLoad config from `{project-root}\u002F_bmad\u002Fbmm\u002Fconfig.yaml` and resolve:\n\n- `project_name`, `user_name`\n- `communication_language`, `document_output_language`\n- `implementation_artifacts`\n- `date` as system-generated current datetime\n- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`\n\n### Step 5: Greet the User\n\nGreet `{user_name}`, speaking in `{communication_language}`.\n\n### Step 6: Execute Append Steps\n\nExecute each entry in `{workflow.activation_steps_append}` in order.\n\nActivation is complete. Begin the workflow below.\n\n## Paths\n\n- `test_dir` = `{project-root}\u002Ftests`\n- `source_dir` = `{project-root}`\n- `default_output_file` = `{implementation_artifacts}\u002Ftests\u002Ftest-summary.md`\n\n## Execution\n\n### Step 0: Detect Test Framework\n\nCheck project for existing test framework:\n\n- Look for `package.json` dependencies (playwright, jest, vitest, cypress, etc.)\n- Check for existing test files to understand patterns\n- Use whatever test framework the project already has\n- If no framework exists:\n  - Analyze source code to determine project type (React, Vue, Node API, etc.)\n  - Search online for current recommended test framework for that stack\n  - Suggest the meta framework and use it (or ask user to confirm)\n\n### Step 1: Identify Features\n\nAsk user what to test:\n\n- Specific feature\u002Fcomponent name\n- Directory to scan (e.g., `src\u002Fcomponents\u002F`)\n- Or auto-discover features in the codebase\n\n### Step 2: Generate API Tests (if applicable)\n\nFor API endpoints\u002Fservices, generate tests that:\n\n- Test status codes (200, 400, 404, 500)\n- Validate response structure\n- Cover happy path + 1-2 error cases\n- Use project's existing test framework patterns\n\n### Step 3: Generate E2E Tests (if UI exists)\n\nFor UI features, generate tests that:\n\n- Test user workflows end-to-end\n- Use semantic locators (roles, labels, text)\n- Focus on user interactions (clicks, form fills, navigation)\n- Assert visible outcomes\n- Keep tests linear and simple\n- Follow project's existing test patterns\n\n### Step 4: Run Tests\n\nExecute tests to verify they pass (use project's test command).\n\nIf failures occur, fix them immediately.\n\n### Step 5: Create Summary\n\nOutput markdown summary:\n\n```markdown\n# Test Automation Summary\n\n## Generated Tests\n\n### API Tests\n- [x] tests\u002Fapi\u002Fendpoint.spec.ts - Endpoint validation\n\n### E2E Tests\n- [x] tests\u002Fe2e\u002Ffeature.spec.ts - User workflow\n\n## Coverage\n- API endpoints: 5\u002F10 covered\n- UI features: 3\u002F8 covered\n\n## Next Steps\n- Run tests in CI\n- Add more edge cases as needed\n```\n\n## Keep It Simple\n\n**Do:**\n\n- Use standard test framework APIs\n- Focus on happy path + critical errors\n- Write readable, maintainable tests\n- Run tests to verify they pass\n\n**Avoid:**\n\n- Complex fixture composition\n- Over-engineering\n- Unnecessary abstractions\n\n**For Advanced Features:**\n\nIf the project needs:\n\n- Risk-based test strategy\n- Test design planning\n- Quality gates and NFR assessment\n- Comprehensive coverage analysis\n- Advanced testing patterns and utilities\n\n> **Install Test Architect (TEA) module**: \u003Chttps:\u002F\u002Fbmad-code-org.github.io\u002Fbmad-method-test-architecture-enterprise\u002F>\n\n## Output\n\nSave summary to: `{default_output_file}`\n\n**Done!** Tests generated and verified. Validate against `.\u002Fchecklist.md`.\n\n## On Complete\n\nRun: `python3 {project-root}\u002F_bmad\u002Fscripts\u002Fresolve_customization.py --skill {skill-root} --key workflow.on_complete`\n\nIf the resolved `workflow.on_complete` is non-empty, follow it as the final terminal instruction before exiting.\n",{"name":5,"description":7},"main","6a38430d5c23377d52d12343bfc156063f577e1d",".continue\u002Fskills\u002Fbmad-qa-generate-e2e-tests","https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR","https:\u002F\u002Fgithub.com\u002Fjsacko","2026-06-22 14:57:27",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add jsacko\u002FOpenDFIR --skill bmad-qa-generate-e2e-tests",{"tool":59,"command":60},"bunx","bunx skills add jsacko\u002FOpenDFIR --skill bmad-qa-generate-e2e-tests",{"tool":62,"command":63},"pnpm","pnpm dlx skills add jsacko\u002FOpenDFIR --skill bmad-qa-generate-e2e-tests","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002F.continue\u002Fskills\u002Fbmad-qa-generate-e2e-tests\u002FSKILL.md",true,[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"checklist.md","REFERENCE","参考文档",891,"https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002F.continue\u002Fskills\u002Fbmad-qa-generate-e2e-tests\u002Fchecklist.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"customize.toml","OTHER","其他",1639,"https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002F.continue\u002Fskills\u002Fbmad-qa-generate-e2e-tests\u002Fcustomize.toml",[80,107,128,147,168,181],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":89,"publishedAt":42},"01M71PW68SHKJ6357YZJH4ES0E","agent-tonin","Pressure-tests incident response product design against real SOC and DFIR constraints. Use when the user asks to talk to Tonin, requests the Incident Response Strategist, or needs a senior security design partner to challenge incident response automation ideas.","https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002Fskills\u002Fagent-tonin\u002FSKILL.md",[86],{"categoryNo":87,"categoryName":88,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[90,91,92,93,94,95,32,96,38,36,97,98,99,100,101,102,103,104,105,106],"agent tonin","ideas","senior security","dfir","incident","challenge","design","product design","automation","incident response","soc","design partner","requests","product","senior","strategist","security",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":114,"publishedAt":42},"01M71PW3BV6P3JK7MFN31TA61D","bmad-workflow-builder","Builds, converts, and analyzes workflows and skills. Use when the user requests to \"build a workflow\", \"modify a workflow\", \"quality check workflow\", \"analyze skill\", or \"convert a skill\".","https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002F.continue\u002Fskills\u002Fbmad-workflow-builder\u002FSKILL.md",[113],{"categoryNo":87,"categoryName":88,"taxonomyType":21,"taxonomyTypeDesc":22},[115,116,117,26,118,102,33,119,120,121,122,123,124,36,125,38,126,127],"builder","workflow","workflow builder","bmad workflow builder","a skill","quality","build","analyze","check","convert","workflows","quality check","modify",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":139,"publishedAt":42},"01M71PW0ETTF8DA2C6HB77FPNX","bmad-validate-prd","Validate a PRD against standards. Use when the user says \"validate this PRD\" or \"run PRD validation\"","https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002F.continue\u002Fskills\u002Fbmad-validate-prd\u002FSKILL.md",[134],{"categoryNo":135,"categoryName":136,"taxonomyType":137,"taxonomyTypeDesc":138},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[140,141,26,142,143,144,38,36,145,146,33],"validate","bmad validate prd","prd","validate prd","standards","run","validation",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":156,"publishedAt":42},"01M71PVY254CKN2PNAEX41CRR9","bmad-technical-research","Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report","https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002F.continue\u002Fskills\u002Fbmad-technical-research\u002FSKILL.md",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[157,158,159,26,160,161,162,163,38,36,164,165,166,167,33],"technical research","bmad technical research","technical","research","conduct","do","produce","architecture","to do","research report","report",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":42},"01M71PVWCA63WBH08JHVV6WV75","bmad-sprint-status","Summarize sprint status and surface risks. Use when the user says \"check sprint status\" or \"show sprint status\"","https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002F.continue\u002Fskills\u002Fbmad-sprint-status\u002FSKILL.md",[],[175,26,176,177,178,33,123,179,36,38,180],"status","bmad sprint status","sprint","sprint status","summarize","show",{"skillNo":182,"name":183,"nameZh":6,"description":184,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":185,"categories":186,"keywords":187,"publishedAt":42},"01M71PVT03ZW4PQVV5TZDNPBXH","bmad-sprint-planning","Generate sprint status tracking from epics. Use when the user says \"run sprint planning\" or \"generate sprint plan\"","https:\u002F\u002Fgithub.com\u002Fjsacko\u002FOpenDFIR\u002Fblob\u002Fmain\u002F.continue\u002Fskills\u002Fbmad-sprint-planning\u002FSKILL.md",[],[177,188,189,26,190,175,33,191,192,145,27,178,193,36,38],"bmad sprint planning","planning","sprint planning","sprint plan","tracking","plan"]