Organize the recent learning and ask for corrections if there is any inappropriateness.
The basic process of software testing:
Requirement analysis stage -> Test planning stage--> Writing test cases--> Test implementation stage--> Output test report
1. Demand analysis stage
Software testing must be based on requirements, which should be based on requirements. Therefore, at the beginning, you must carefully read the requirements, understand the requirements, analyze the requirements, participate in the requirements review, and deeply understand and grasp the logical relationships in the requirements.
2. Test planning stage
Compile a software test plan with reference to the software requirements specification and the overall project plan. It mainly contains the following five contents:
a. Test objectives and scope
b. Task assignment and schedule
c. Develop a test strategy
d. Risk analysis and prevention
e. Various indicators of acceptance items
The test strategy part generally includes three parts: test method, test tool, and test environment. For the testing strategy, the first round focuses on business processes to ensure that the online functions and pages are displayed normally; the second time focuses on page testing to ensure that the processes and pages of the online business are displayed normally; the third round focuses on the entire business The process and pages are the main ones to ensure that the functions, processes and pages of each section of the launch are normal; other direction tests such as fault tolerance test, permission test, special environment test, etc. The software risks include business risks, security risks, and schedule risks. The acceptance part includes deliverables such as test requirements, test plans, test cases, test reports, etc., as well as test case requirements and version acceptance defect repair rate requirements.
3. Write test cases
For software testing, from the perspective of the tested object, it can be divided into the following three testing methods: black box testing, white box testing and gray box testing. The eight commonly used methods of black box testing are: equivalence class method, boundary value method, decision table method, causality diagram method, state transition method, scenario method, orthogonal experiment method and error guessing method; white box testing methods include : Statement coverage, decision coverage, condition coverage, decision/condition coverage, condition combination coverage.
4. Test implementation phase
The work content of the test implementation phase includes the construction of the test environment, the execution of test cases, and bug regression. Software testing can be divided into four stages, namely
- Unit test: check and verify the smallest testable unit in the software, general tour developers implement the inspection function whether it meets the design requirements
- Integration test: also called assembly test. Based on the unit test, the module is assembled according to the design requirements to check whether the corresponding function is completed. The interface part of the test module is mainly tested, and the stub module or driver module used in the test process needs to be designed
- System test: Test the software that has been confirmed and tested together with computer hardware, peripherals, and supporting software in the actual operating environment
- Acceptance test: also called delivery test, it is a formal test for user needs and business processes to determine whether the system meets the acceptance criteria, and the user, customer or other authorized organization decides whether to accept the system
These four stages embody the gradual testing process and the idea of divide and conquer from small to large, from inside to outside. Among them, the granularity of unit testing is the smallest, and the development team generally uses white box testing to verify whether the test unit conforms to the "design"; integration testing is between unit testing and system testing, and developers generally use white box plus black The method of testing is to verify whether the system meets the "design" and whether it meets the "requirements"; the granularity of the system test is the largest, and generally an independent test team adopts a black box method to test whether the system meets the "requirement specifications" Manual"; acceptance test is similar to system test, the main difference is that the tester is different, and the acceptance test is performed by the user.
5. Output test report
The software test report is a summary document with unique value and logic behind it, including the test process and process results, some problems encountered during the process, and the next stage of improvement work. The role of the test report is manifested in three aspects: reporting, evaluation, and reflection. Reporting refers to reporting to leaders and projects as much as possible in the form of test reports, and reporting recent test results; evaluation refers to evaluating software quality, and the evaluation depends on the test team, and the use cases and use cases used in the test project are executed The results and the software defects found in the middle show the quality of the software directly and concretely; reflection means to reflect on how to improve work through review. The software test report can be written under the framework of the reference template, guided by the person in charge of the test and the leader, and carried out after the end of a test phase. Its core content should include:
- Elapsed test work: time, work, participants
- Use cases and defects: function, total, execution, defect
- Software quality assessment: functions, risks, possible quality problems
- Work improvement suggestions: remaining defects, demand suggestions, test environment, project management
Reference template: https://blog.csdn.net/xqtesting/article/details/78976456