Service testing method and device

Abstract

The invention provides a service test method and device which can be used in the financial field or other fields. The method comprises the following steps: receiving a test request of a target service; according to the test request, acquiring a flow configuration file corresponding to the target service, wherein the flow configuration file is generated in advance according to a flow chart drawn by a code component icon selected by a user on a front-end page and input component parameters; and determining an abnormal reason of the target service according to the process configuration file. The method can improve the automation degree and efficiency of service testing, and can save the labor cost of service testing.

Description

technical field [0001] The present application relates to the technical field of data processing, in particular to a service testing method and device. Background technique [0002] In the prior art, major software development companies generally deploy multiple sets of test environments isolated from the production environment during the project development process, such as functional test environments, process test environments, and simulated production test environments; each test environment is due to Due to frequent update of the test version and manual changes of data by the testers, it is easy to cause service errors; after the testers discover the service errors, they will contact the relevant developers and wait for the developers to troubleshoot the problem. If it takes a long time, it will cause problems to be blocked in the long run. [0003] Common log analysis tools mainly include: PAL, LOGalyze, and LogDNA log analysis tools; these log analysis tools mainly a...

AI Technical Summary

Problems solved by technology

[0002] In the prior art, major software development companies generally deploy multiple sets of test environments isolated from the production environment during the project development process, such as functional test environments, process test environments, and simulated production test environments; each test environment is due to Due to frequent update of the test version and manual changes of data by the testers, it is easy to cause service errors; after the testers discover the service errors, they will contact the relevant developers and wait for the developers to troubleshoot the problem. It takes a long time, and it will cause problems to be blocked in the long run.

[0003] Common log analysis tools mainly include: PAL, LOGalyze, and LogDNA log analysis tools; these log analysis tools mainly analyze logs for system-level problems, such as network performance, network failures, thread problems, and database failures; Tools can analyze underlying problems from the system and network levels, but problems in the daily software development process are often caused by dependent server downtime, data inconsistencies, and business logic control collisions (that is, some data will be blocked in a specific scenario). Refusal to trade), etc., resulting in service errors, most of which are data and business logic problems. Existing log analysis tools are difficult to solve the pain points that daily developers spend a lot of time troubleshooting service problems

Images