Software testing (II)

Catalog

1. According to the test object

1.1 Interface

1.2 reliability

1.3 Fault tolerance

​ edit  

1.4 Document the test

1.5 Compatibility test

1.6 Ease of use test

1.7 Install the uninstall

 2. Divided by whether to view the code

 2.1 Black box testing

2.2 White box testing

2.3 Grey box testing

3. According to the development stage

3.1 unit testing

​ edit  3.2 Integration testing

3.3 The system test

3.4 regression testing

​ edit  3.5 Smoke testing

3.6 The acceptance test

4. According to the implementation organization

5. It is divided according to whether the code is running

6. According to whether it is divided manually

7. By Region

---

Preface ： We explained some basic contents and methods of testing . Next, we will divide it according to the classification of general tests .

1. According to the test object

1.1 Interface

The user interacts with the software through the interface , The quality of interface design . It directly affects the users' understanding of the software The impression of . So let's start with interface testing , Also called UI test .

Common interface errors ：

 

1.2 reliability

 

1.3 Fault tolerance

Definition ： System exception , Or an error occurs in the software system due to incorrect operation , Software digests its own mistakes , Or make changes , It's called system fault tolerance .

 

1.4 Document the test

The software development must keep the integrity with the requirements of the documentation 、 Uniformity 、 Correctness and ease of use ( Easy to understand ）

1.5 Compatibility test

 

1.6 Ease of use test

 

1.7 Install the uninstall

 

      

 2. Divided by whether to view the code

 2.1 Black box testing

2.2 White box testing

 

2.3 Grey box testing

Both the input and output of software functions are concerned , Also concerned about the implementation of software internal code

3. According to the development stage

 

3.1 unit testing

 3.2 Integration testing

3.3 The system test

 

3.4 regression testing

 3.5 Smoke testing

When the software development is finished , Test the basic functions and core processes of the software , After passing the test , To officially enter the test environment . If the test fails , The tester has the right to call back , Let the development revise , Until smoking succeeds .

3.6 The acceptance test

 

4. According to the implementation organization

 

5. It is divided according to whether the code is running

1） The static test ： Don't run code , Check whether the style of the code conforms to the company's specifications and standards , Check whether the logical structure of the code meets the function to be realized .

 2） Dynamic testing

Run code , Input to program response , See if you get the desired output

6. According to whether it is divided manually

7. By Region