Software testing process: traditional testing process, test shift left (development) and test shift right (operation and maintenance)
Traditional testing process
Unit testing → integration testing → smoke testing → system testing → regression testing → acceptance testing
System testing process
Requirements analysis → Test plan → Test design (use case) → Use case review → Test execution → Bug management → Release maintenance
bug management process
Submit defects → Assign defects → Confirm defects (Yes) → Postpone processing (Yes) → Remaining defects (processed in subsequent versions) → Process defects → Regress defects (Pass) → Close defects
Confirm the defect (yes) → defer processing (no) → process the defect → return the defect (pass) → close the defect
Confirm defect (No) → Revert defect (Pass) → Close defect
Regression defect (failed) → Reopen → Confirm defect
Shift testing left (development) and shift testing right (operations)
Shift left testing: intervene early in the development cycle to test code and prevent bugs.
Quality assurance methods: code review, code audit, unit testing, automated smoke testing, R&D self-testing.
Test shift right: After release, monitor online.
Quality assurance methods: closed-loop online problem feedback-check-solve-update process, log review and return service, quick log positioning, business monitoring, daily monitoring of key indicators, and production data monitoring.