Static Test - review requirements documents, test cases.
Static testing refers to not run the program, procedures and documentation for analysis and inspection.
Static testing is complete, also known as static analysis technology
Static tests including requirements specification software specification, source code, design documents, review.
Static test content:
1. Walkthrough (development phase)
Reading between each other ① developer code check written is correct or not
② Only by understanding the source code before they can complete the unit test, or to quickly understand the source code is a prerequisite for the completion of unit testing.
③ code for commuting problems found in more than unit tests found, faster, sooner.
④ Test Unit programming specifications can not meet the problem.
⑤ Sometimes the naked eye look, do not need unit tests.
2. Document review (all stages)
① needs assessment document
② review of design documents
③ assessment test documentation: test plans, test cases, test reports.
④ review the user manual
Dynamic testing: manual, automatic.
Dynamic testing is carried out manually or by using a tool checking program operation, and program output execution state analysis program.
White box, black box testing gray box testing belong dynamic test.
Black box testing
Focus only on input and output
Black box testing to find flaws and errors in its external representation of the software. The test object as a black box, does not consider internal structure and processing procedure.
Black box test design method:
Equivalence partitioning method
Boundary value analysis
Error reckoning
Cause and effect diagram method
Scenario analysis
Gray box testing:
Interface test (data - Format - certification), integration testing
Gray box testing interposed between the white box and black box test
Follow output gray box testing input correctness; also look at the internal representation, but not concern white box as detailed and complete.
White-box testing
Corresponding to the unit test
Test Methods range:
White box test application unit 1. Method
2. Application integration testing gray box testing method
3. System test and test applications really black box testing methods.
System test:
The concept: is to combine other elements that have been identified software, computer hardware, peripherals, networks, various assembly and testing and validation testing information systems.
System tests include:
1. Functional Test:
To verify each product's features, according to functional test cases, one by one test, check whether the product meets customer needs.
Functional test is based on the "requirements specifications"
Structure Normal / abnormal input communication check whether the desired output. If they do not match, that indicates that the function is wrong.
Functional test difficulty is to understand the user's needs, and efficient data structure.
2. Performance Test
Test software processing speed of business
Test performance is in line with demand
Some performance data obtained with reference to the workers
3. Robustness Testing
1. robustness means that in exceptional circumstances, the ability to run software also normal.
2. Robustness has two meanings:
① fault tolerance: some unreasonable input fault tolerance test is generally configured to trigger a software error such as:
1. Enter the wrong data type
2. Enter values outside the domain of
3. Test the client - a software server mode, unplug the network cable, resulting in abnormal communication interruption.
② resilience
1. The system can run again.
2. Wrong loss of important data.
3. Is destroyed other related software and hardware.
4. Security Testing
Refers to the system to prevent illegal invasion of capacity, technology and technical problems and management issues belong.
① set goals for the illegal invasion, such as "theft of a file" or "Change database record" and so on.
② invite (or reward) Some hackers play, let them find ways to break into systems, to achieve the "target."
③ If someone successful. Asked him to describe the invasion process.
5. Pressure test
That limit state system operation.
6. Reliability Test
Reliability testing is the probability that under certain circumstances, at a given time, the system does not malfunction. Because the software not the hardware that can be "accelerated aging" According to this definition, software reliability may be issued for a long time.
- disaster recovery, recovery, fault tolerance.
Reproduced in: https: //www.cnblogs.com/Chamberlain/p/11001167.html