1. Understand the test object
1. Familiar with the documentation
a. Requirements documentation: for new requirements; familiar with baseline version documentation
b. Help documents: familiar with old functions such as product documents, user manuals, etc.
c. Develop design documents
d. Code documentation
2. Familiar with operation
Operate the software under test
2. Familiarize yourself with the test object from six aspects, SFDPOT
1. Structure results
a. Be familiar with the architecture of the software under test and what files are included
b. Network architecture: B/S, C/S, P2P, stand-alone version
c, the composition of the software under test
Startup files, uninstall files, program code files, configuration files, help files, testers (test all possible situations)
2, function function
Be familiar with everything the software under test can do, i.e. functional modules
3. Data data
Be familiar with all the data the software under test can handle
a. Input data: legal, illegal
b. Output data
c. Preset data: data prepared in advance
c. Preset data: data prepared in advance
4. Pattern platform
Familiar with the platform on which the software can run, that is, the environment
5. Operation
Familiar with how the software under test may be used and how users use it
6. time
Familiar with the modules of the software under test and system time, such as special time, leap year, new year, etc.
Pay attention to the time difference
3. Extract test points
1. Quality Model Analysis
For a single module, each module needs to extract
Reminder to test from multiple angles and multiple aspects, not just focus on functions
The picture comes from Baidu
2. Functional Interaction Analysis
Focus on module-to-module direct interaction or mutual influence
Direct sequence of modules, testing high-priority functions will interrupt low-priority functions
3. User usage scenario analysis
Pay attention to user usage