@bugzy-ai/bugzy 1.13.0 → 1.13.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/cli/index.cjs +6 -0
- package/dist/cli/index.cjs.map +1 -1
- package/dist/cli/index.js +6 -0
- package/dist/cli/index.js.map +1 -1
- package/dist/index.cjs +6 -0
- package/dist/index.cjs.map +1 -1
- package/dist/index.js +6 -0
- package/dist/index.js.map +1 -1
- package/dist/tasks/index.cjs +4 -0
- package/dist/tasks/index.cjs.map +1 -1
- package/dist/tasks/index.js +4 -0
- package/dist/tasks/index.js.map +1 -1
- package/package.json +1 -1
package/dist/cli/index.cjs
CHANGED
|
@@ -268,6 +268,9 @@ Before invoking the agent, identify the test cases for the current area:
|
|
|
268
268
|
- Existing automated tests: ./tests/specs/
|
|
269
269
|
- Existing Page Objects: ./tests/pages/
|
|
270
270
|
|
|
271
|
+
**Knowledge Base Patterns (MUST APPLY):**
|
|
272
|
+
Include ALL relevant testing patterns from the knowledge base that apply to this area. For example, if the KB documents timing behaviors (animation delays, loading states), selector gotchas, or recommended assertion approaches \u2014 list them here explicitly and instruct the agent to use the specific patterns described (e.g., specific assertion methods with specific timeouts). The test-code-generator does not have access to the knowledge base, so you MUST relay the exact patterns and recommended code approaches.
|
|
273
|
+
|
|
271
274
|
**The agent should:**
|
|
272
275
|
1. Read the manual test case files for this area
|
|
273
276
|
2. Check existing Page Object infrastructure for this area
|
|
@@ -276,6 +279,7 @@ Before invoking the agent, identify the test cases for the current area:
|
|
|
276
279
|
5. For each test case marked \`automated: true\`:
|
|
277
280
|
- Create automated Playwright test in ./tests/specs/
|
|
278
281
|
- Update the manual test case file to reference the automated test path
|
|
282
|
+
- Apply ALL knowledge base patterns listed above (timing, selectors, assertions)
|
|
279
283
|
6. Run and iterate on each test until it passes or fails with a product bug
|
|
280
284
|
7. Update .env.testdata with any new variables
|
|
281
285
|
|
|
@@ -6467,6 +6471,8 @@ Before proceeding, read the curated knowledge base to inform your work:
|
|
|
6467
6471
|
- Build on existing understanding
|
|
6468
6472
|
- Maintain consistency with established practices
|
|
6469
6473
|
|
|
6474
|
+
3. **Relay to subagents**: Subagents do NOT read the knowledge base directly. When delegating work, you MUST include relevant KB patterns in your delegation message \u2014 especially testing patterns (timing, selectors, assertion approaches) that affect test reliability.
|
|
6475
|
+
|
|
6470
6476
|
**Note:** The knowledge base may not exist yet or may be empty. If it doesn't exist or is empty, proceed without this context and help build it as you work.`,
|
|
6471
6477
|
tags: ["setup", "context"]
|
|
6472
6478
|
};
|