1. Test Category:
Press development stage: unit testing, integration testing, validation testing, system testing and acceptance testing;
Executed in the body: developer Test (a), the user test (b), third-party testing;
Executed in the state: static and dynamic;
Testing Technology Press: black box, white box, gray box;
2. Automated Test
Principle: Direct static and dynamic code analysis, capture and playback of the testing process, test scripts and virtual user technology.
Script: A collection of tools to test a set of instructions executed.
Scripts Directory: linear script, structured script, sharing script, data-driven script, keyword-driven script, virtual user technology.
3. testing process: test plans - Design test - test execution - test records - analysis - Defect Tracking - finished - test summary
4. Test Unit (code under test for testing a very clear function)
Five tasks:
Interface Test Module: Globals defined consistency, call parameters
Test module local data structures: data definitions, using
All test module execution paths: the critical path, the path is important
Error handling various tests: Non reasonable input, system abnormalities
Boundary conditions of the test module: circular boundary, the input boundary (boundary value analysis case design)
Module: a drive module (a module on the module under test analog) - the module under test - the stub (analog module calls the module under test)
The integrated test (unit tested modules connected together, dependencies between modules of the interface diagram of the test)
Five tasks:
When checking module call each other, when data is lost through the interface;
After each sub-combinations of features, functions can achieve the intended inspection requirements;
Whether a function module of another function module will have a negative impact;
Whether global data structure in question, would not be unusual modifications;
Individual modules accumulated error, whether amplified to an unacceptable extent.
classification:
Incremental integration: one step, as a whole, are connected after the individual test unit tests for all modules
Non-incremental integration:
1) top-down test (depth-first strategy / breadth-first policy)
2) Top-Up Test
3) Sandwich integration testing
6. confirmation (verification same functionality and performance of software and whether the user's requirements) test
Validity of the test
Software Configuration Review
7. Acceptance Test
1) a and b Test Test
2) Regression Testing
8. Software Testing Model : V model, W model, H model, X model, the model front
V model:
Most typically, it is software development variant of the waterfall model
On the left is the development stage, the right is the test phase
The arrows represent the order, that is, after the first development test
W Model:
Two V, representing the development and testing, both simultaneously
Unable to support iterative development model
H model:
The important point is ready to reach a test, test execution activities can be carried out
Test preparation and test execution separation is conducive to resource allocation
Fully reflect the complexity of the testing process
X models:
Left X code, test procedures for individual segments, and integrally formed executable program;
The top right has been submitted to the user through the integration testing of the finished version of the seal, the lower right is exploratory testing.
9. Test Case
Types of:
Functional test case: functionality, robustness, reliability
Performance test: performance, pressure, intensity,
Integrated test case: interfaces, robustness, reliability
Security test
The user interface test
Install / uninstall test
| Testing phase | Test Type | executive staff |
| unit test | Functional testing module, comprising an interface portion of the test, the test path | Develop |
| Integration Testing | Interface testing, path testing, functional testing portion comprising | Develop |
| System test | Functional testing, robustness testing, performance testing, user interface testing, security testing, stress testing, reliability testing, installation / de-installation testing | test |
| Acceptance Test | Same as above for the actual project, and the document that contains the test; For software products, the main test technical documentation | Test, may contain user |