Testing is implemented into every link of the software life cycle (planning-requirements-design-coding-testing-maintenance)
The four stages of testing
The four stages are: unit testing - integration testing - system testing - acceptance testing
Software product level: function - module, subsystem - software
1. Unit testing
a. Time: After a single function is completed, perform a test on the function
b. Object: function
c. Basis: LLD (Detailed Design Description)
d. Executive: Development
2. Integration test
a. Time: After a module is completed, test the module
b. Objects: modules, subsystems
c. Basis: HLD (Outline Design Description)
d. Executives: development, testing
3. System test
a. Time: the entire software development is completed
b. Object: the entire software, running on the specified hardware environment
c. Basis: SRS (Requirement Description)
d. Executor: test
4. Acceptance test
a. Time: After the R&D team completes the development and testing of the product, before submitting it to the user for use
b. Object: software system
c. Basis: the user's own needs
d. Two tests:
d1. Formal acceptance, the third party conducts acceptance on behalf of the user, the software evaluation center
d2. Informal acceptance. Alpha testing: internal testing of the software, acceptance by users in a specified environment, and the environment is controllable; beta testing: users test in the actual environment, the environment is uncontrollable
Two, three basis documents
1. Requirements document SRS
General overview: software overview, functions implemented by the software, user features used, etc.
Specific requirements: implemented functions (input, output, processing), performance requirements (corresponding time, etc.), external interfaces (user interface, software interface, etc.)
Overall design constraints, requirements classification, etc.
Main content: characteristics of software, constraints and importance of software
Implications for development and testing: The ultimate goal of developing a product; testing is based on documentation and tests the entire software
2. Outline design document HLD
Decompose software and describe the process by which it is formed
3. Detailed design document LLD
The internal implementation of the function
3. Testing activities
1. Test plan
who、when、where、what
2. Test design
how
3. Test implementation
use case writing
4. Test execution
Use case execution, environment construction, bug analysis submission, defect analysis report, risk
4. Regression testing
For tests that have already been performed, repeated executions become regressions
Scenario: Verify after code modification. Bug modification and software upgrade or software interface reconstruction
After the code is modified, other problems may be introduced, and the related functions of the modified code also need to be tested
Strategy: full regression: importance, timing, impact; partial regression: modified content, related features, important features, suggestions provided by development