Software Testing Fundamentals
But if you will come, then winter is not worth mentioning
1. Basic knowledge of software testing
1. Definition of software testing
2. Classification of software testing methods
3. Principles of software testing
4. Software testing strategy
5. Software testing model
6. Software testing life cycle
1. Definition of software testing
The process of operating a program under specified conditions to detect program errors, measure software quality, and evaluate whether it meets design requirements.
Specified Conditions --> Test Cases
Find program errors --> find bugs
Measuring software quality --> quality assessment
Meet the design requirements --> meet the requirements
2. Classification of software testing methods
3. Principles of software testing
1. Testing should be done as early as possible, preferably at the requirements stage, because the most serious mistake is that the system does not meet the user's needs.
2. Programmers (development) should avoid checking their own programs, and software testing should be done by third parties (testers).
3. Design test cases with legal and illegal inputs in mind. [For example: the decimal part of the amount input box exceeds two digits 0.0001]
4. When testing a program, it is not only necessary to check whether the program does what it should do, but also whether the program does what it should not do. The extra work will bring side effects, affect the efficiency of the program, and sometimes bring potential problems. harm or error.
5. All test cases should be retained for a long time. Retaining test cases is helpful for regression testing after program modification.
4. Software testing strategy
1. Select the test method: choose the most suitable test method for the current project (such as when the project is urgent? The project is frequently released) (for example, automated testing can be used for repetitive testing work)
2. Roles and responsibilities: Each role and the responsibilities of the role need to be clearly defined in the test strategy. Such as project managers, test leaders, test engineers.
3. Environmental requirements: This is very important, it will describe the system environment (software, server Linux, windows, database MySQL) required for the test, including hardware and software, network environment and so on. In clarifying environmental requirements, the testing organization can identify resource-related risks.
4. Risk Analysis: Risks affecting the testing process should be identified as early as possible, and corresponding solutions must be in place to eliminate or mitigate these risks. (For example: personnel leave, whether the software is completed)
5. Test Progress Evaluation: The test progress will evaluate the time required to complete the test. When setting the progress, you first need to specify the test scope (for example, adding a D module this time, some functions will affect the functions of the B module that has been launched), and then specify the test that can be recognized by all aspects according to the amount of test resources. progress plan.
6. Regression Testing strategy: Regression testing is used to ensure that the code that fixes bugs will not affect other parts of the software, which requires us to select the already executed test cases to rerun. Testers need to find a way to determine which test cases should be run in regression testing, not too many use cases, because resources are limited, and too few use cases, otherwise the necessary test intensity will not be achieved.
7. Priority: The things within the scope of the test are not all equally important, and the testing resources are limited, so it is necessary to prioritize the tested modules.
5. Models for software testing
6. The life cycle of software testing
