1. According to the development stage
Unit testing, integration testing, system testing, acceptance testing
Generally, you need to read programs and codes. Most of the time, unit testing is done by developers themselves, also known as module testing, which is the testing work for correctness verification of program modules, the
smallest unit of software design .
- Its purpose is to check whether each program unit can correctly realize the module function, performance, interface and design constraints in the detailed design specification, and to find various errors that may exist inside each module.
- Unit testing needs to design test cases from the internal structure of the program.
- Multiple modules can be unit tested in parallel and independently.
Also known as assembly testing. More related to interface testing (interface testing tools and methods)
- Usually on the basis of unit testing, all program modules are tested in an orderly and incremental manner.
- Integration testing is to verify the interface relationship of program units or components, and gradually become program components or the entire system that meet the requirements of the outline design.
3. Confirmation test (whether the function is realized)
It is generally a positive test, and generally not a formal test link.
Confirmation testing is also called validity testing or smoke testing.
- It is to verify whether all functions, performance and other characteristics of the software are consistent with the user's expected requirements in a simulated environment.
- After passing the confirmation test, the software has the qualification to enter the system testing stage.
Comprehensive: the test of all the functions of the system
simulates the operation of all software users
Comprehensive: the relationship between the tested software and hardware, the relationship with the system software, and the relationship with other software
- System testing is to check whether the complete program system can be correctly configured and connected with the system (including hardware, peripherals, network and system software, support platform, etc.) in a real system running environment, and finally meet all the needs of users.
Generally,
there are three main subjects of acceptance testing between the supply and demand sides: α test (pre-delivery test conducted by the software developer himself), β test (test conducted by the software demander himself), γ test (third-party software testing by the software demander)
- It is the last link of software product inspection. according to
- Test and review the entire system according to the project mission statement or contract, and the acceptance basis documents agreed by the supplier and the buyer, and decide whether to accept or reject the system.
2. Divide according to code operation
- Refers to the process of statically checking possible errors in program codes, interfaces or documents without actually running the tested object
- Code testing : mainly testing whether the code complies with the corresponding standards and specifications
- Interface test : Mainly test whether the actual interface of the software is consistent with the description in the requirements
- Documentation test : Mainly test whether the user manual and demand description meet the actual needs of users
- Refers to the process of actually running the object under test, inputting the corresponding test data, and checking whether the actual output results are consistent with the expected results.
- So we judge whether a test is a dynamic or a static test, the only criterion is whether to run the program
3. According to the software characteristics
Is an aspect of black box testing, which checks whether the actual software functionality meets the needs of the user
- Logic function test
- interface test
- usability test
- Install / Uninstall Test
- compatibility test
- Another indicator of function, which mainly focuses on whether a certain function in the software is used normally under the specified time and space conditions
- The performance of software includes many aspects, mainly including time performance and space performance.
- Verify whether the protection mechanism installed in the system can protect the system in practical application, so that it will not be invaded illegally or interfered by various factors.
Fourth, according to the test technology division
- Find defects and errors in software by its external appearance.
- The black box testing method regards the test object as a black box, without considering the internal structure and processing process of the program at all.
- Black box testing is to test at the program interface, it just checks whether the program is implemented normally according to the requirement specification
- Find problems by analyzing and testing the internal structure of the program.
- White box testing can regard the program as being installed in a transparent box, check whether all the structures and paths are correct, and check whether the internal actions of the software are carried out normally according to the design instructions.
- white box testing
Testing between white box testing and black box testing.
Gray box testing focuses on the correctness of the output to the input; it also pays attention to the internal performance, but this kind of attention is not as detailed and complete as the white box testing. It only judges the internal operating status through some representative phenomena, events, and signs.
- Refers to the repeated execution of all test cases of an important previous version when testing the latest version of the software
- Purpose: To verify that all bugs from previous versions have been fixed; to confirm that fixing these bugs did not cause new bugs
2. Smoke test/confirmation test
- It refers to verifying whether the basic functions of the software are realized and whether it is testable before conducting a systematic large-scale test on a new version, also called testability testing.
3. Random test/exploratory test
- It refers to the tester based on experience and intuition, and found some marginal errors
- Think of yourself as a fool or a small animal who doesn’t understand the product, randomly click without the main awareness and ideas of the heat to participate, and let some unexpected operations cause wrong results
6. According to the division of test operation subjects
Functional testing, little by little
Use tool software, or the way of writing code, to test the software system under test (game plug-in)