Test method and terminal equipment

Abstract

The invention discloses a test method and terminal equipment. The test method comprises the following steps: the terminal equipment determines a test node which executes a test function corresponding to each processing step and obtains the information of each test node according to processing steps contained in the business flow of a tested source code; the terminal equipment generates the information of each test node into a test use case according to the business flow of the tested source code; and the terminal equipment tests the tested source code according to the test case. Through the test method and the terminal equipment, the same test node can be used in different test use cases, and the test use cases can be flexibly configured by the test nodes.

Description

Technical field [0001] This application relates to the computer field, and in particular to a testing method and terminal equipment. Background technique [0002] Integration testing is generally integrated into the source code under test as an independent test module. The purpose of integration testing is to cover the overall business logic and abnormal branches of the source code under test by running test cases to ensure the correctness of business and exception handling. The design of the integration test is mainly composed of two parts: the source code to be tested and test cases. The test cases are driven data collections composed of various business parameters, which are used to simulate the use cases of certain business scenarios. The test cases are responsible for The parameters are combined according to certain rules and passed to the corresponding interface of the tested source code. The tested source code completes the simulation operation, and then the test case chec...

AI Technical Summary

Problems solved by technology

[0005] Although the Mock front-end business flow method reduces the complexity of test case design and focuses the test focus on the process node, there is a potential risk: the mock front-end data may not be completely correct, such as the front-end business flow output If the parameters are changed, but the mock data is not updated in time, data-driven errors will occur, resulting in omission of test coverage

[0006] Test the source code to solidify the business flow method, and obtain the data generated by the pre-process by running the business flow solidified in the test code. This kind of data has a high degree of simulation and can avoid the problem of driving data errors in the mock pre-mode, but This design method has the following defects: the business process is solidified in the test code, and each business flow needs to design a corresponding test case; a large part of the business flow front-end process is the same, and the front-end business flow data The preparation has similarities, but cannot be reused; the entire business process drives data softly in one test case, which increases the complexity of test case maintenance; when encountering complex long-process business, the above defects will be more obvious

Images