R&D iteration quality control stuck points sorting out
2024-11-12 11:03:04 128 0 Report 0
0
Login to view full content
This mind map outlines the 5-step quality control process for R&D iteration, focusing on resolving stuck points. It emphasizes the importance of participating in requirements review meetings to understand demand planning and ensure QA synchronization. The process includes evaluating test difficulty, setting clear sprint admission criteria, and maintaining high-quality acceptance standards. Key areas include story test criteria, regression testing, and defect density analysis. It also covers release management, emphasizing code quality, bug fix timeliness, and collaborative execution. The map concludes with production monitoring, analyzing defect escape rates, and operational data to ensure optimal performance.
Other creations by the author
Outline/Content
Participate in the requirements review meeting
Understand short- and medium-term demand planning
Check: QA Weekly Meeting Group Synchronization
Provide test reference opinions, evaluate the difficulty of the test and the data scheme.
Pull-Through Sprint Admission Criteria
AC&PRD - R&D test review meeting question system
Priority - Development Testing Sequential Order
The latest story test date - Ordered testing
Story Release Date - Orderly Release
Story point accurate assessment and responsible person setting
Story test criteria, R&D self-test criteria, story rejection data statistics
Clear understanding of requirements, uniform development steps, high-quality acceptance for testing, clear release deadlines.
Clarify the execution criteria for acceptance test cases
Use Case Review
Test Plan - JIRAPlan
Smoke automation execution
Smoke Test Case Execution
Full regression test case execution
PRE integrated data testing
Core stability function smoking
Comparison data for case creation and execution
Review must be executed
Use Case Pass Rate
Story test progress control
The story test lag rate
The story rejection rate
Off-plan story rate
Thursday Final Version (CodeFreeze)
Code Quality
Defect Density (Number of Defects / Workload)
The proportion of serious defects
Smoke Test Pass Rate
Timeliness of bug fixes
Defect Fix Duration
7-day defect backlog
Distribution of defective modules
Release as agreed
Closing the code specification - Test what is released
No merge unless necessary
Automated Access Quality Evaluation - Test Report (<60 points poor, 60-80 points good, >80 points excellent)
BPM acceptance, grayscale trial
Checklist Management
Press Conference
Release Executor
Structured Query Language
Rollback plan
QA acceptance authority, data, test cases
Upstream and downstream collaboration
Standardized execution
Code, SQL execution order
Acceptance -> Issue Record
Non-essential issues are not fixed immediately.
Serious problem assessment and repair impact, decisive rollback
Comprehensive acceptance, especially for some functions that require business and product acceptance
What happened in production?
Defect Escape Rate
Incident analysis
APM Performance Data
Operational Data Monitoring - How many people are using it?
0 Comments
Next page
Recommended for you
More
