Basic knowledge of software testing

1. Divide the test type from the test phase

project （ The software product / Software product function version ） The development phase ： （ Project life cycle ： Abandon from the beginning of the project ）

Demand survey -> Demand for design （ Product function design description ）-> Technical design stage -> code -> test -> check before acceptance -> go online

unit testing ：

Test process based on the smallest code module of the project ;

practitioners ：

In the market, developers are basically responsible for executing unit tests by themselves ;

To achieve complete coverage of all cases or possibilities, unit tests , The unit test code is more than twice as much as the development function code

Integration testing ：

The process of combining multiple units for testing

execution time ：

The coding phase is carried out later ;

practitioners ：

Back end code module integration , Testing based on the source code of future generations is still tested by development ;

Front and back end code integration , Self test by development , Testers can coordinate integration testing ;

The implementation of ：

On the market 50% Functions do not perform integration tests

The system test

Developer , Version / All the developed codes of the project are packaged and submitted to the test for verification （ Stage ）

In the process of system testing, testers can take various testing methods to test according to the requirements of the requirements

Manual testing

Performance testing

Compatibility testing

The acceptance test

After testing, the engineer submits the complete contents of the project to the product for acceptance ;

Person in charge of acceptance test ： The product manager

Stage

Internal measurement ：

Within the company . Release it to some external customers for experience ;

In use , Development and testing focus on whether there are problems in the internal testing process , If it is repaired in time ;

Internal test generally delete files ;

Public survey

        Develop the system for external customers , Generally, there is no problem ;

  Official release

      After the public beta is stable for a period of time , Officially released to all customers for use ;

Now the company's conventional playing methods in the market ：

1. Acceptance testing is generally the acceptance of product personnel in the simulation environment ;

      Simulation environment ： Use real online customer data to execute the test environment ;

2. In the form of grayscale release ;

      Grayscale Publishing ： Only a small number or designated customers can see the latest functions by using technical means ; Through this form to reduce the risk of problems ;

Responsibilities of Test Engineer ：

      Follow up whether there are defects in the acceptance process （ problem ）

      Be responsible for recording defects , And assigned to the developer of problem processing , At the same time, be responsible for verifying whether the problem is solved after repair ;

2. Divide from whether to view the source code

Black box testing

        Pay no attention to the implementation of the code , Only focus on entering the specified data on the interface , The test process of whether the results presented by the page are correct ;

White box testing

        The process of testing completely based on the code level ;

            Perform unit tests （ A means of performing tests using code or tool code ）

            Use the code to check the coverage of the code written by the programmer

Grey box testing

        Will touch some code , But I will also check the presentation of some data

        What is tested is some interfaces provided by the background for front-end access （ route ）

        The interface test

3. According to whether it is divided

The static test

        Test whether there are typos on the interface , Is the style correct , Is the alignment correct

        Write relevant documents in the test project / Whether the description is correct and reasonable （ I can't do it for the time being ）

                For example, text ambiguity . The requirement description reveals

                    Delete the commodity data of the background management system , Pop up the window to confirm deletion , Click delete , Click Cancel reservation

  Dynamic testing

        Run the system to execute the test process

4. Divide according to whether it is automated

Manual testing

automated testing

        Take the code , The process of testing the program with tools

5. The test strategy

Smoke testing ：

              After development and test , Only after smoke test can the system test be officially started

              Smoke test mainly checks whether the core functions of this version are available , There is no lack of function

regression testing ：

              Defects found during the test , Retesting of defects after development and repair

                Test the functions that have been launched in history

Randomness test

Exploratory testing

6. defects

Concept ： Errors or problems found during the operation of the complete project or single function version

judge ：

        Implementation error

        Not according to the product manual （ The requirements document .UI/UE Design draft ） Rules to implement functions ( Data error / Function error / Page display error, etc )

Multiple implementation

        It realizes the functions required in the product specification （ Gild the lily ）

Less realization

        Omit the function or display clearly required in the product manual

By market business （IT Hidden rules for software quality in the industry ） Unrealized requirements （ Accumulated through practical work experience ）

Software usability . Poor learnability ;

      QQ Chat and wechat chat

      Function buttons in a page cannot exceed 9 individual ;

7. The cause of the defect

Product requirements specification （ Requirements specification .UE/UI Design draft ） Explain the error , Input errors lead to incorrect implementation ;

Team developers , Testers , People in need ,UI The design has inconsistent understanding of requirements in the process of their respective implementation ;

Developers write code incorrectly ;

Software compatible with hardware or system software error ;

8. Type of defect

Compatibility error

Interface error （ Panel type of interface display . How , Style and UI The design draft is inconsistent ）

Function error

Opinions and usability optimization

9. The test case

Concept ： To verify specific rules , The function point , Execute the input in the pending condition , operation , Validation rule , Whether the function points are documented in accordance with the requirements

        Explain what to test

        Explain how to test the specified content