What I will share with you today is the functional testing and interface testing that we will definitely come into contact with in our daily testing work and are currently the main testing content in the enterprise
1. The basic concepts of functional testing and interface testing.
1.1 What is functional testing?
Functional testing: It is an aspect of black box testing to check whether the function of the actual software meets the needs of users
The content of the functional test test includes the following aspects:
Logic function test
interface test
usability test
Install/Uninstall Test
compatibility test
Now that black-box testing is mentioned, let's look at the definition of black-box testing.
1.2 What is black box testing?
Black box testing refers to discovering hidden defects of software through the external performance of software.
Black-box testing regards the object under test as a black box, completely ignoring the internal structure and implementation logic of the program.
Black box testing is to test at the interface of the program, it just checks whether the program is implemented normally according to the provisions of the PRD document (requirement specification).
1.3 What is interface testing?
The interface is the realization of a certain business logic of the system, and it is a kind of specification provided for use by other systems, mainly a protocol specification for a certain business behavior and the data (parameters) involved and the results of the business behavior
Interface testing is the process of simulating the data exchange between the client and the server for request and response. It is a test of the interface between system components in the server.
The interface test is mainly used to check the interaction points between the external system and the system, and between the various modules in the system.
The focus of interface testing is the logical dependencies between systems and modules and related data generated with the business
2. Functional testing and unit testing are in that development stage
unit test:
Unit test is also called module test. The test content is the smallest unit of the program, that is, the module (code block). The reference basis is the detailed design specification
Integration Testing
Integration testing is also known as assembly testing. Usually, on the basis of unit testing, all program modules are tested in an orderly and incremental manner. The test content is the interface relationship between modules and between systems. Integrate as program components or entire systems that meet the outline design requirements.
confirmation test
Also called validity 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 is qualified to enter the system testing stage
System test
Check the entire system/program in the production environment, whether it can be correctly configured and connected with system resources (including hardware, peripherals, network, system software, supporting platforms, etc.), and finally meet all the needs of users
Acceptance Test
It is the last link of software product inspection.
Test and review the entire system according to the project task statement or contract, and the acceptance basis documents agreed by the supplier and the buyer, and decide whether to accept or reject the system, which is divided into customer acceptance and third-party acceptance
Through the above relevant content, I believe you can see more intuitively that the interface test is tested in the integration test phase. Functional testing is concentrated in the stages of confirmation testing and system testing.
3. Comparison of interface testing and functional testing
Comprehensive comparison:
1. The functional test must be the front-end interface, and the back-end code can only be carried out after the joint debugging is completed, while the interface test can be tested after the back-end development code is written. Relatively speaking, the interface test is earlier than the function test;
2. Functional testing does not focus on the internal structure and code implementation of the program, while interface testing tests how the program is implemented internally. Therefore, interface testing is naturally suitable for more complex systems. The larger the system, the stronger the necessity of interface testing. At the same time, the effect of interface testing will be better.
3. Functional testing is to discover hidden defects in the software by executing corresponding test cases in the interface of the program, while interface testing is to initiate a request to obtain response data by calling a predefined interface in the program. The business and data of the interface scene are verified. From the perspective of the efficiency of finding defects, the efficiency of interface testing to find defects is much higher than that of functional testing.
4. Interface testing is a test that focuses on business logic. Therefore, in the current scope of testing in enterprises, the proportion of interface testing has gradually exceeded that of functional testing.
5. The purpose of interface testing and functional testing is to discover hidden defects in the software, so in essence, they are all to ensure the quality of the software. There is no one who is more dominant. Therefore, in the actual testing process, The two do not conflict.
Finally, I would like to thank everyone who has read my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, you can take it away if you need it:【保100%免费】
Software testing interview applet
The software test question bank maxed out by millions of people! ! ! Who is who knows! ! ! The most comprehensive quiz mini program on the whole network, you can use your mobile phone to do the quizzes, on the subway or on the bus, roll it up!
The following interview question sections are covered:
1. Basic theory of software testing, 2. web, app, interface function testing, 3. network, 4. database, 5. linux
6. web, app, interface automation, 7. performance testing, 8. programming basics, 9. hr interview questions, 10. open test questions, 11. security testing, 12. computer basics
Document acquisition method:
This document and video material should be the most comprehensive and complete preparation warehouse for friends who want to engage in [software testing]. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey. Hope Can help you too! All of the above can be shared, click the small card below to receive.