1. By development stage

· unit testing

    Also called module testing .

    The smallest unit of software design —— Test the correctness of the program module . Check whether each program unit is implemented correctly Detailed design specification The function of .

    Starting from the internal structure of the program , Design test cases , Multiple modules can be tested in parallel and independently .

· Integration testing

    Assembly test .

    On a unit test basis , All program modules are in order 、 Incremental testing . Check the interface relationship between program units or components . It is mainly used to find problems between module interfaces .

· Confirmation test （ Smoke testing ）

    Also called validity test .

    In a simulated environment , Verify the function of the software 、 Whether the performance and other characteristics are consistent with the user's expected requirements . Only after passing the confirmation test can they have the qualification to enter the system test .

    It's usually Forward test （ If the right path of the program doesn't work , Not to mention the exception path ）, Generally not as a formal test link .

    confirm ： Does the function have , Is it implemented

    verification ： Whether the function meets the requirements

· The system test

    Test the whole product system , Verify that the system meets Requirement specification The requirements . The test object includes not only the software of the product system , It also includes the hardware on which the software depends 、 Peripherals even include some data 、 Some support software and its interfaces .

    characteristic ： comprehensive （ All functions are tested ; Simulate the operation of all users ）; A full range of （ Check the connection with the hardware system ; Connection with system software ; Contact with other software, etc ）.

· The acceptance test

    The last link of software product inspection , according to Assignment or contract 、 Acceptance basis And other documents to test and review the whole software system , Decide whether to receive the system .

    （1）α test ： The developer of the software carries out pre delivery testing .

            A test conducted by a user in a development environment , It can also be a controlled test conducted by users within the company in a simulated environment . namely Internal measurement .

    （2）β test ： The software needs to be tested by itself .

            The test conducted by multiple users of software in the actual use environment of one or more users . namely Public survey .

    （3）γ test ： Tests conducted by third parties .

2. According to the test technology

· Black box testing

    Think of the test object as a black box , Regardless of its internal structure and processing process , Check whether the procedure is correctly implemented according to the requirements specification .

    Through the external performance of the software to find its errors and defects .

    Generally used to confirm the correctness and operability of software functions , Check whether each function of the software can be realized .

· White box testing

    Also called logic driven testing . It's code based testing .

    Test by analyzing the internal logical structure of the software , Check whether the internal actions of the software are carried out normally according to the provisions of the design instructions .

· Grey box testing

    Between black box and white box .

    Focus on the correctness of the output for the input ; Also focus on internal performance , But not as carefully as the white box test .

3. Divided by whether the code is running

· The static test

    Do not actually run the tested object , Just statically check the program code 、 The process of possible errors in an interface or document .

• Code testing ： Test whether the code conforms to the corresponding standards and specifications
• Interface tests ： Test whether the actual interface of the software is consistent with the description in the requirements
• Document the test ： Test whether the user manual and requirements specification meet the actual needs of users

· Dynamic testing

    Contrary to static testing , Need to run software .

4. According to software characteristics

· A functional test

    One aspect of black box testing , Check whether the function of the software meets the needs of users .

• Logic function test
• Interface tests
• Ease of use test
• install / Uninstall test
• Compatibility test

· Performance testing

    Focus on a function of the software at a specified time 、 Under space conditions , Whether it is in normal use .

    Main concern Time performance and Space performance .

· Safety test

    Verify whether the protection mechanism installed in the software system protects the system in practical application , So that it will not be invaded illegally 、 Not disturbed by various factors .

    give an example ：QQ Remote login protection mechanism

5. Other test categories

· regression testing

    When testing a new version of the software , Repeat all test cases of a previous important version .

    Verify that all defects in the previous version have been repaired ; Confirm that fixing these defects does not lead to new defects .

· Smoke testing

    Before large-scale testing of a new version , First, verify whether the basic functions of the software are realized , Is it measurable . Therefore, it is also called testability test .

· Random test

    Test based on experience and intuition , Find some marginal mistakes .

· Monkey test

    Think of yourself as a fool who doesn't understand products , Whatever you want , No subjective consciousness and ideas , Let some unexpected operations cause wrong results .

6. A summary of the testing techniques used at each stage