Mapping between TDD Implementation Process and qTest Modules
Align the TDD micro-development iteration (Red-Green-Refactor) with the qTest quality brain (Requirement, Plan, Execution, Defect) point-to-point to implement measurable software engineering.
Comparison Matrix of TDD Process and qTest Modules
In an agile DevOps team, every action by developers corresponds to a specific state in the qTest quality management system. This establishes a complete end-to-end traceability chain:
1. qTest Requirement
Corresponds to the **starting point of TDD specifications**. Both developer test code and functional code must be created based on resolving the requirement specifications logged in qTest.
2. qTest Plan
Corresponds to the **Red (failing test) stage of TDD**. Developers must directly derive automated test scripts from the planned test cases (Use Cases) in qTest.
3. qTest Execution
Corresponds to the **Green (passing test) stage of TDD**. After local self-testing passes, code is published to the test area where Key Users perform UAT, and test results are logged in qTest.
4. qTest Defect / Issue
Corresponds to the **Refactor / Reactive Bug-fixing closed loop of TDD**. When execution fails, logged defects will trigger a dedicated refactoring and fixing process until issues are reduced to zero.
Daily TDD Development Process Details
Follow these four development steps to strictly infuse qTest quality requirements into every line of production code:
Parse Requirement SpecificationsRequirement
Read approved requirement items and specifications from qTest. Clarify the business logic and boundaries of this feature, treating requirements as the sole starting point for development.
Write Failing Tests (Red)Plan - Use Case
Developers directly pull the planned test cases (Use Cases) from qTest and write automated test code in the local environment. At this point, executing the test must result in a **red light**, thereby establishing the target specification.
Implement Functionality and Deliver for ExecutionExecution
Write the simplest MES functionality code to make tests turn into a **green light**. After local self-testing passes, deploy the program to the Test Area, initiate qTest Execution for user UAT, ensuring evidence-based delivery.
Safe Refactoring and Defect RegressionDefect - Issue
Eliminate duplication and optimize code, ensuring tests maintain a green light. If UAT fails and defects are logged, force the transition to 'first write tests to reproduce bugs, then fix them'. Only unlock after regression testing passes.