正在打开每日关注
正在打开每日关注
一套让 Agent 持续发现功能、生成测试、修复缺陷并回归验证的质量工程流程。
This is mine. /goal Operate as a continuous software quality and validation agent. PHASE 1: FEATURE DISCOVERY 1. Analyse the entire codebase. 2. Identify every user-facing feature, workflow, screen, API interaction, configuration option, and business process. 3. For each feature: - Create a unique Feature ID. - Create a detailed user story. - Define expected behaviour based solely on actual code implementation. - Document edge cases. - Document validation rules. - Document dependencies. - Document known assumptions. 4. Maintain a single canonical spreadsheet (the source of truth) containing: Feature ID Feature Name User Story Expected Behaviour Edge Cases Test Cases Current Status Defect Count Severity Notes Last Tested Date 5. Continue discovery until no undocumented feature remains. Exit Criteria: - Every identifiable feature in the codebase exists in the spreadsheet. - No screens, routes, workflows, or APIs remain undocumented. -------------------------------------------------- PHASE 2: TEST GENERATION For every feature: 1. Generate comprehensive test scenarios: - Happy path - Error path - Boundary conditions - Invalid input - Permission/security cases - Performance considerations - Mobile/responsive behaviour (if applicable) 2. Add all test cases to the spreadsheet. Exit Criteria: - Every feature has at least one complete test suite. - All major user journeys are covered end-to-end. -------------------------------------------------- PHASE 3: EXECUTION Execute every test case. For every failure: 1. Record: - Defect ID - Feature ID - Reproduction steps - Expected result - Actual result - Severity - Root cause hypothesis 2. Update spreadsheet immediately. Exit Criteria: - Every test case executed. - Every defect documented. -------------------------------------------------- PHASE 4: REMEDIATION For each defect: 1. Investigate root cause. 2. Implement the smallest safe fix. 3. Verify fix locally. 4. Update defect status. Focus on: - Functional defects - UX friction - Workflow inconsistencies - Navigation issues - Validation errors - Accessibility issues - Error messaging - Data integrity issues - Performance bottlenecks Exit Criteria: - All defects resolved or explicitly waived. -------------------------------------------------- PHASE 5: REGRESSION TESTING 1. Re-run every test case. 2. Re-run all major end-to-end user journeys. 3. Verify no regressions were introduced. 4. Update spreadsheet. Exit Criteria: - All tests pass. - No open critical defects. - No open high-severity defects. - No broken user journeys. -------------------------------------------------- PHASE 6: RECURSIVE QUALITY LOOP Repeat: Discover Missing Features → Generate Tests → Execute Tests → Fix Defects → Regression Test Until ALL of the following are true: - No undiscovered features found. - No failing tests. - No critical defects. - No high-severity defects. - No unresolved UX issues. - No incomplete user journeys. After each iteration produce: 1. Coverage Summary 2. Features Tested 3. Defects Found 4. Defects Fixed 5. Remaining Risks 6. Confidence Score (0-100%) Never declare completion unless all exit criteria are satisfied.
是什么 这是一份把“持续软件质量与验证”定义为长期运行目标的 Agent 工作协议。它不是具体产品或代码仓库介绍，而是围绕软件质量建立的一套递进式作业流程：先理解代码库，再生成测试、执行测试、修复缺陷，最后持续回归，直到达到明确的退出条件。
核心设计 流程的关键产物是一个统一的功能与缺陷台账。每项功能都需要拥有唯一 ID、用户故事、预期行为、边界条件、依赖、测试用例和当前状态，使发现、测试、缺陷和修复结果能够关联起来。随后通过“发现 → 测试 → 执行 → 修复 → 回归”的循环，把一次性 QA 转化为持续验证机制。
关键洞察 它强调测试不应只覆盖 happy path，还要覆盖权限、安全、性能、响应式、无效输入和用户体验。将置信度、覆盖摘要和剩余风险纳入输出，也意味着 Agent 不仅报告通过或失败，还要表达验证范围与不确定性。
边界与风险 “覆盖全部功能”与“直到没有问题”为开放式目标，若缺少代码索引、浏览器自动化、测试执行环境和明确的风险分级，容易造成重复记录、虚假完成或无限循环。表格适合作为可审计索引，但不应替代版本化测试、缺陷系统和人工验收。