testing

Testing

Dependency Specification

#[[file:../rules/review-base.md]] #[[file:../rules/git-workflow.md]] #[[file:../rules/project-structure.md]]

Purpose

Verify that functionality meets requirements and ensure delivery quality.

Input

• Module code: code for each module
• Requirements list: requirements list, used as the basis for test cases

Test Types

#	Type	Description
1	Unit Testing	Core logic of each module, covering normal paths and exception paths
2	Integration Testing	Cover core business processes
3	E2E Testing	Cover key user scenarios
4	Regression Testing	Add corresponding test cases after each bug fix
5	Performance Testing	No obvious performance issues in core processes (load time, rendering lag, etc.)
6	Security Testing	Input validation, permission control, sensitive data not exposed

Steps

For each step, first output the title, then output the result

• Ask the user: Before starting any testing work, first send the following confirmation message to the user:

  Do you need to write tests? If so, please select the test types (multiple selections allowed):

  1. Unit Testing
  2. Integration Testing
  3. E2E Testing
  4. Regression Testing
  5. Performance Testing
  6. Security Testing
  7. No testing needed, skip this phase

  • After waiting for the user's explicit reply, execute subsequent steps only for the test types selected by the user
  • If the user selects 0 or clearly indicates that testing is not needed, skip this phase

• Loop by type (only for the test types confirmed by the user):

  • Create branch: decide whether to create a separate branch based on the test type (unit tests can be written on the feature branch; integration/E2E, etc. are recommended to use a separate branch)
  • Write test cases: write test cases according to the requirements list
  • Delete outdated: delete invalid test cases
  • Execute review: after completion, execute review, comply with review-base
  • Merge branch: after review passes, merge into the main branch

• Write documentation: after all tests are completed, write the test report (path complies with project-structure Document storage specification)

• Execute review: comply with review-base, and only proceed to the next step after passing

• Submit: after review passes, submit according to git-workflow submit

Output

• Test cases: each type of test case selected by the user
• Test report

Review checklist

• Type coverage: every test type selected by the user has been completed
• Business coverage: core business processes all have test coverage
• Boundary coverage: boundary conditions and exception scenarios have test cases
• Case quality: descriptions are clear and can be used as functional documentation

Phase End

Next Phase:deployment

#[[file:../rules/stage-gate.md]]