1. Test the model
1.1 Waterfall Model
Waterfall model is suitable for structured method software project or product selection The waterfall model must meet the following conditions: 1. No or little change in requirements during development time; 2. Analysis designers should be familiar with the application domain; 3. Low-risk projects (for The target and environment are very familiar); 4. The user's use environment is very stable; 5. The user rarely participates in the development work except for the request
1.2V model
Advantages: It includes low-level testing (unit testing) and high-level testing (system testing); it clearly identifies the various stages of development and testing; it is refined step by step from top to bottom, and each stage has a clear division of labor, which is convenient for overall project control.
Disadvantages: The top-down sequence results in that the test work cannot be modified in time after coding. In actual work, the requirements often change, resulting in repeated execution of the V model steps, a large amount of rework, and low flexibility.
1.3W model
1.4H model
1.5 Agile Models
1.6 Exploratory Testing
Exploratory testing can be said to be a testing mindset. It doesn't have many actual testing methods, techniques and tools, but it is a testing mindset that all testers should master. Exploratory emphasizes the subjective initiative of testers, abandons the complicated test plan and test case design process, and emphasizes changing the test strategy in time when problems are encountered.
Note: The difference between the V model and the waterfall model
The V model and the waterfall model share some characteristics. The processes in the V model go from left to right and describe the basic development process and testing behavior.
Pros: The value of the V-model is that it very clearly identifies the different levels that exist in the testing process and clearly describes how these testing phases correspond to the phases during the development process
Limitations: (Testing is involved too late) Use testing as the last activity after coding, and errors generated in the early stage such as requirements analysis cannot be found until the later acceptance test
2. Software life cycle
demand analysis
Testers decompose, understand requirements, get test points, test requirements
- The relationship between test points and test cases is one-to-many
Requirement review meeting: Requirement personnel to explain, R&D, and testing related persons in charge
Test Plan
Write test plans based on requirements
- The main function
- Staff assignments
- Approximate execution time of the project
Test Case Design - Development Test
Testers pass the requirements, understand the development settings, and design test cases
Test case review meeting
- Early release of review notices
- Participants: Product requirements, development, testing, configuration managers
- output test case
test execution
The most important work stage for testers, combined with testing methods and basic knowledge of testing, exposes defects in all aspects of the software
Important requirements:
- software quality
- meet demand
- Serious bugs, such as 404, 500, errors, cannot appear after going online
test evaluation
The test gives the evaluation of the software test, including whether it is qualified to meet the online conditions, whether serious bugs have been closed, to ensure the smooth launch, and make a test report summary
Whether serious bugs are modified, verify after modification, and close after verification
references:
without
Remark:
If there is any infringement, please contact by email, I am sorry.
This is only for learning personal notes, and if there is any reprint, please indicate the source.
Contact Email: [email protected]
Learn to test the penguin group together (chat, water group, do not disturb advertising): 826471103