Update nexus wiki content
This commit is contained in:
32
wiki/concepts/Continuous-Dev-QA-Loop.md
Normal file
32
wiki/concepts/Continuous-Dev-QA-Loop.md
Normal file
@@ -0,0 +1,32 @@
|
||||
---
|
||||
title: "Continuous-Dev-QA-Loop"
|
||||
type: concept
|
||||
tags: []
|
||||
sources: [agents-orchestrator]
|
||||
last_updated: 2026-05-29
|
||||
---
|
||||
|
||||
## Definition
|
||||
**Continuous Dev-QA Loop**(持续开发质量循环)是 [[AgentsOrchestrator]] Phase 3 的核心机制——开发与 QA 交替进行,每个开发交付物立即经过 QA 验证,形成快速反馈闭环。
|
||||
|
||||
## Relationship to [[Dev-QA-Loop]]
|
||||
- [[Dev-QA-Loop]] is the specific implementation of this concept within the AgentsOrchestrator pipeline
|
||||
- Continuous Dev-QA Loop is the broader principle: rapid feedback between development and quality assurance
|
||||
|
||||
## Core Principle
|
||||
> "No shortcuts: Every task must pass QA validation."
|
||||
|
||||
## Loop Characteristics
|
||||
- **Continuous**: No waiting until end-of-project QA — validation happens after each task
|
||||
- **Fast feedback**: Developer receives specific feedback immediately after implementation
|
||||
- **Evidence-based**: QA requires visual/screenshot proof, not self-reported completion
|
||||
- **Iterative**: Loop continues until PASS or max retries reached
|
||||
|
||||
## Benefits
|
||||
- Issues caught early before propagating to downstream tasks
|
||||
- Developer receives specific, actionable feedback
|
||||
- Quality gates prevent broken functionality from advancing
|
||||
- Reduced final integration issues due to continuous validation
|
||||
|
||||
## Sources
|
||||
- [[agents-orchestrator]]
|
||||
Reference in New Issue
Block a user