1. Write the interface test plan
The goals of the interface test plan and the functional test plan are consistent, both to confirm the requirements, determine the test environment, determine the test method, prepare for the design of test cases, and initially formulate the interface test progress plan. Generally speaking, the interface test plan includes overview, test resources, test functions, test focus, test strategies, test risks, test standards, etc.
2. Write and review interface test cases
Similar to functional testing, before starting interface testing, it is necessary to write and review interface test cases based on project-related documents such as requirements documents and interface documents.
3. Execute the interface test
According to the written interface test cases, with the help of test tools (postman, jmeter, soapui, etc.), perform interface tests and report test problems.
Fourth, the key points of continuous integration of interface automation testing
During project testing, interfaces will increase, decrease, and change, and test cases will be updated accordingly. Therefore, tools (github, etc.) are needed to maintain test cases for continuous integration, and real-time monitoring of project interfaces and running conditions through automated testing. For interface testing, continuous integration is the core content, and the cost can be reduced only by means of automation.
The continuous integration of interface automation testing mainly includes the following contents:
(1) In terms of process: In the regression stage, the coverage of interface exception scenarios is strengthened, and gradually extended to the system test and smoke test stages, and finally achieves full process automation.
(2) Result display: richer result display, trend analysis, quality statistics and analysis, etc.
(3) Problem location: The error information and logs are more accurate, which is convenient for problem recurrence and location.
(4) Result verification: strengthen automatic verification capabilities, such as database information verification.
(5) Code coverage: Constantly try to drop from the current black box to the white box to improve code coverage.
(6) Performance requirements: improve the performance testing system, and monitor whether the interface performance indicators are normal through automated means.
The following is the supporting information. For friends who do [software testing], it should be the most comprehensive and complete preparation warehouse. This warehouse also accompanied me through the most difficult journey. I hope it can help you too!
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
Information acquisition method:
