table of Contents
1. The definition of software testing
Second, the life cycle of the software
Three, the basic process of software testing
4. Test points, test cases, bugs and test reports
1. The definition of software testing
(From "The Practice of Test Architects")
Second, the life cycle of the software
| life cycle |
Subdivision |
Work content |
| Problem definition and planning |
The developer and the demander discuss together, mainly to determine the purpose and feasibility of the software development. Make a development plan |
|
| demand analysis |
Analyze in detail the various functions that the software needs to achieve, and figure out all the users’ requirements for the software system Output "Requirements Specification" |
|
| Software design (convert the results of demand analysis into software structure and data structure to form a system architecture) |
Outline design |
Mainly the realization of the architecture, referring to the construction of the architecture, the description of the functions of each module, the realization of the module interface connection and the realization of data transmission, etc. |
| detailed design |
In-depth analysis of each module, analysis of each module combination, etc. At this stage, the pseudo-code level is required, and the specific functions and phenomena to be realized by the program are described, including database design instructions. |
|
| Software coding |
According to the detailed design of the module function table, programmers start to write code |
|
| Software testing (After the software is written, it must undergo rigorous testing to find problems and correct them) |
unit test |
Mainly to test the program code, in order to ensure that each unit module is compiled normally. There are tests specific to modules, as well as tests specific to classes and functions, etc. |
| Integration Testing |
After the unit test, each unit is formed into a complete system to test whether the interface between the software units is correct and whether the data can be transmitted normally |
|
| System test |
Set up the software system and test various functions in accordance with the requirements in the "Software Specification" to see if it meets the requirements and whether there are loopholes in the system operation, etc.-Perform a complete system test based on the test cases |
|
| Acceptance Test |
After the customer gets the software, he will do the corresponding test according to the requirements mentioned above and the "Specification Manual" to determine whether the software meets the requirements |
|
| Operation and Maintenance |
It is the longest period in the life cycle. In order to extend the service life of the software and adapt to user needs, the software must be maintained. Including corrective maintenance and improvement maintenance |
Three, the basic process of software testing
| Test process |
Work content |
| Demand analysis stage |
Reading needs, understanding needs, mainly means learning business and analyzing demand points |
| Planning stage |
The main task is to write a test plan, refer to the software requirements specification, project overall plan, test scope, schedule, allocation of manpower and material resources, designation of the overall test strategy, and risk assessment and avoidance measures. There is a designation, usually written by a test manager. |
| design phase |
The main task is to write test cases. It will refer to the requirements analysis, outline design, detailed design and other documents. If there are ambiguities, it will promptly communicate with the development and product managers. After the use case is written, it will be reviewed |
| Execution phase |
First, build a test environment and perform predictions to determine whether the current version is testable or not. If the prediction passes, enter the system test formally, submit bugs to the defect management platform when encountering problems, and track the bugs until the software under test meets the test requirements , No major bugs, the test is over |
| Evaluation phase |
Write a test report and make a detailed assessment of the entire test process and version quality |
4. Test points, test cases, bugs and test reports
(From "The Soul of Soft Test Core Test Design Detailed Explanation")
4.1 Test plan design
4.2 Test points and test case design
4.3 Basic knowledge of bugs
4.4 Test report design
