What are the different types of software testing and what are the types of software testing?

PC software, Internet software, mobile phone software, embedded software, hardware, etc., all need to be tested, as long as there is software and hardware, they need to be tested, and the development prospects are the best.

static testing; From the press execution process.

From the perspective of running status, it is divided into: dynamic test and static test; From the perspective of the implementation process, it is divided into: manual testing and automated testing;

According to the characteristics of the software, the types of tests are divided into functional tests and performance tests.

Functional tests include:

Logical functional testing.

Interface test crack auspicious.

Usability testing.

Installation testing. compatibility testing, etc.

Performance is actually another indicator of function, which mainly focuses on whether a function in the software is used normally under specific time and space conditions; For example, load testing and stress testing are both performance tests, and the two can be combined.

According to the test technology, there are black box tests, white box tests, and gray box tests.

Black-box testing only focuses on input and output, that is, the external performance of the program;

The white-box test focuses not only on the external performance of the program, but also on how the internal structure of the program is realized.

Grey box testing is somewhere in between;

According to the development stage, there are unit tests, integration tests, system tests, and acceptance tests.

Unit testing, also known as module testing, is the smallest unit for software design, and unit testing needs to design test cases from the internal structure of the program;

Integration testing, also known as assembly testing, is to verify the interface relationship of program units or components, and gradually integrate them into program components or the whole system that meet the requirements of the summary design;

The system test 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 the real system operation environment, and finally meet all the needs of users;

Acceptance testing is the final part of the software product inspection. Test and review the entire system according to the project task book or contract, and the acceptance document agreed by both suppliers and demanders, and decide whether to accept or reject the system.

Finally: the main difference between black-box testing and white-box testing is whether or not the internal structure of a system or program is understood;

Unit testing mainly uses white-box testing;

The integration test is mainly based on the white box, supplemented by the black box;

The system test is mainly based on black box, supplemented by white box;

Acceptance testing is mainly the use of black box testing.

Regarding the field of software testing, there are a lot of terms, and it is found that there are many novice testers who confuse the concept, and even many recruitment requirements use various software testing-related terms indiscriminately, so computer training summarizes test-related terms here, and may be able to clarify your concept of various terms.

Divide the tests according to the process phases of the project.

The above diagram is a typical waterfall software development process, so the software testing work is carried out step by step in the project development process. Here's what the test means.

Unit Testing: Unit testing is testing of the basic units of software. The purpose is to verify the correctness of the basic components of the software.

Integration Testing: Integration testing is a test performed during the integration of a software system. The purpose is to check that the interface between the software units is correct.

System testing: System testing is a thorough test of an integrated software system to verify that the correctness and performance of the software system meet the requirements specified in its specification.

Acceptance Testing: Acceptance testing is the last test operation before the software is deployed. The purpose of acceptance testing is to ensure that the software is ready to demonstrate to the software that the software system meets the needs of its users.

Integration Testing Phase:

1.When connecting each module, whether the data data that traverses the module interface will be lost?

2.Whether the modules can be combined to achieve the expected required functions.

3.Whether the functionality of one module adversely affects the functionality of another.

4.Whether there is a problem with the global data structure.

5.Whether the accumulation of errors in individual modules will be amplified to achieve an unacceptable procedure.

System Testing Phase:

In general, the main test work of the system is concentrated in the system testing phase. Depending on the system, there are many types of tests performed.

Functional testing: Functional testing is to verify the functions of the product to check whether it meets the requirements of the requirements.

Performance testing: Performance testing is to test the performance indicators of the system by simulating a variety of normal, peak, and abnormal load conditions through automated testing tools.

Security test: The security test checks the system's ability to prevent illegal ingress.

Compatibility test: Compatibility test is mainly to test whether the system can run normally in different software and hardware environments.