Test process management (software test management_quality management)
2024-11-12 11:03:04 0 Report
Log in to view full content
This mind map outlines the comprehensive process of Test Process Management in software quality management. It details each phase, starting with Requirements Analysis, where understanding and confirming product requirements is crucial. The Development Phase emphasizes version control and code review, leading to the Testing Phase, which involves defining and documenting test scopes and executing smoke tests. Acceptance follows, where content and timing are clarified, and the iteration acceptance rate is evaluated. The final stages include Release and Go Live, ensuring all functions are operational, and a Conclusion that focuses on documenting key features and addressing production issues.
Other works by the author
Outline/Content
1. Requirements Analysis
Find the product requirements/prototypes, need to understand the requirements 1 day/half a day in advance,
sort out the question points, including the actual operation of the business, the actual meaning/role of each field
sort out the question points, including the actual operation of the business, the actual meaning/role of each field
Requirement review, questioning, raising issues, confirming requirements
Clarify the test time for iterative testing, test time
2. Development phase
Version Control Specification
code review
Test case/use case writing --- Output①
3. Testing phase
Check the test scope: ① The scope of the test requirements must be clear
② The impact scope of the test content must be clear (confirm in time when it is unclear)
② The impact scope of the test content must be clear (confirm in time when it is unclear)
Test scope record: The test document must be clearly written when submitting for testing.
If there are any additions to the impact scope later, it must be expressed in writing, as verbal expression is not standardized.
If there are any additions to the impact scope later, it must be expressed in writing, as verbal expression is not standardized.
Smoke test case test acceptance passed, enter the test phase
4. Testing phase
The scope of testing: ① requirement scope ② the impact scope of this iteration ③ main process regression test
Bug recording specification:
Reopen bug tracking (Tapd)
Write test points xmind (test cases) according to the version - Output ①
Test progress control, do a good job of risk inspection, synchronization
5. Acceptance
Clarify the acceptance content/time, and conduct the acceptance.
Confirm whether pre-acceptance is required for different projects
(e.g., call the product team for acceptance when the function is running, and then conduct user acceptance after the later testing is completed)
(e.g., call the product team for acceptance when the function is running, and then conduct user acceptance after the later testing is completed)
The acceptance rate (how many times a requirement iteration is accepted after several inspections)
Reason for non-acceptance
6. Release and go live
Confirm the online function and notify relevant parties.
Confirm the execution of the production database script, service configuration, and the deployment order of the frontend and backend.
Production function verification
Online User Manual Writing and Updating - Output ②
7. Conclusion
Organize the latest [instruction document]: regarding key business, operation logic, and features that need to be explained - Output ③
Collect the problems in production, record them in the "Problem Record Form", and follow up on the solutions. (Including BUGs, optimizations, questions, and requests for data modification, etc.)
Schedule regular bug reviews
0 Comments
Next Page
Recommended for you
See more
