CN112286791A - Business system testing method, device, equipment and storage medium - Google Patents
Business system testing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112286791A CN112286791A CN202011035775.4A CN202011035775A CN112286791A CN 112286791 A CN112286791 A CN 112286791A CN 202011035775 A CN202011035775 A CN 202011035775A CN 112286791 A CN112286791 A CN 112286791A
- Authority
- CN
- China
- Prior art keywords
- test
- tested
- service system
- calling
- interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a service system testing method, a device, equipment and a storage medium. The method comprises the following steps: testing the calling interface to be tested by using the test case; collecting test results of test failure; and in the test result of the test failure, generating a multi-level service system log which has a cascade relation with the test result of the test failure according to the call relation among the call interfaces to be tested. By the scheme, when the service system is tested, the current calling interface to be tested is tested, the calling relation among the service systems is considered, the service system with the calling relation is tested, if the test fails, the service system with the current test failure or the log related to the calling interface to be tested is output, and the log related to other service systems with the calling relation is output, so that the efficiency of processing the test problem can be effectively improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of internet, in particular to a service system testing method, a device, equipment and a storage medium.
Background
With the development of service types and service ranges, service systems supporting service implementation are also more and more complex. When a new service system is on-line or when a service system needs to be updated, the service system needs to be tested.
In practical application, when a service system is tested, a tester is often required to set a test process according to experience, so as to perfect a test case. However, the call relationship of a complex business system is also quite complex. The problem of incomplete test is likely to occur, and after the problem occurs, the tester needs to communicate with the butt-joint personnel of each service system to correct the problem. The communication cost is high, and the business progress efficiency is low.
Therefore, a technical solution capable of improving the testing efficiency of the service system is needed.
Disclosure of Invention
The embodiment of the invention provides a method, a device, equipment and a storage medium for testing a service system, which are used for improving the technical scheme of the testing efficiency of the service system.
In a first aspect, an embodiment of the present invention provides an information popularization method, where the method includes:
testing the calling interface to be tested by using the test case;
collecting test results of test failure;
and in the test result of the test failure, generating a multi-level service system log which has a cascade relation with the test result of the test failure according to the call relation among the call interfaces to be tested.
Optionally, the testing the interface to be tested by using the test case includes: obtaining a test case corresponding to a to-be-tested calling interface, wherein the to-be-tested calling interface is an interface of a service system with a calling relation; and testing the calling interface to be tested by using the test case.
Optionally, the obtaining a test case corresponding to a to-be-tested call interface, where the to-be-tested call interface is an interface of a service system having a call relationship, includes: determining the to-be-tested calling interface with a calling relation; sending the interface to be tested with the calling relation to the receiving party; and receiving the test case provided by the receiver.
Optionally, the generating a multi-level service system log having a cascade relationship with the test result of the test failure includes: and generating an assertion log, a system interface log and an analysis log of the multi-stage service system corresponding to the test result of the test failure.
Optionally, the generating a multi-level service system log having a cascade relationship with the test result of the test failure according to the call relationship between the call interfaces to be tested includes: determining the test result as the calling interface to be tested which fails to test; determining a first-stage service system having a calling relation with the to-be-tested calling interface and a second-stage service system having a calling relation with the first-stage service system; and generating the analysis log based on the log of the first-level service system and the log of the second-level service system.
Optionally, the testing the interface to be tested by using the test case includes: the test case is utilized to assert a return state code and a response field of the to-be-tested calling interface; according to the calling relation, a test case state code and a response field of a service system which has the calling relation with the service system corresponding to the calling interface to be tested are asserted; the test results including the assertion log are output.
Optionally, after generating a multi-level service system log having a cascade relationship with the test result of the test failure, the method further includes: sending the multistage service system log with the test result of each test failure having the cascade relation to the corresponding receiver through the mail address of the receiver; wherein the receiver has a corresponding relationship with the service system.
In a second aspect, an embodiment of the present invention provides a service system testing apparatus, where the apparatus includes:
the test module is used for testing the calling interface to be tested by utilizing the test case;
the collection module is used for collecting test results of test failures;
and the generating module is used for generating a multi-level service system log which has a cascade relation with the test result of the test failure according to the call relation among the call interfaces to be tested in the test result of the test failure.
In a third aspect, an embodiment of the present invention provides an electronic device, including a processor and a memory, where the memory is configured to store one or more computer instructions, and when executed by the processor, the one or more computer instructions implement the business system testing method according to the first aspect.
In a fourth aspect, embodiments of the present invention provide a computer-readable storage medium storing a computer program, which when executed by one or more processors causes the one or more processors to perform actions comprising:
testing the calling interface to be tested by using the test case;
collecting test results of test failure;
and in the test result of the test failure, generating a multi-level service system log which has a cascade relation with the test result of the test failure according to the call relation among the call interfaces to be tested.
In the embodiment of the invention, the test case is used for testing the calling interface to be tested; collecting test results of test failure; and in the test result of the test failure, generating a multi-level service system log which has a cascade relation with the test result of the test failure according to the call relation among the call interfaces to be tested. By the scheme, when the service system is tested, the current calling interface to be tested is tested, the calling relation among the service systems is considered, the service system with the calling relation is tested, if the test fails, the service system with the current test failure or the log related to the calling interface to be tested is output, and the log related to other service systems with the calling relation is output, so that the efficiency of processing the test problem can be effectively improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is a schematic flowchart of a service system testing method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a method for determining a test case according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram illustrating a testing process according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a service system testing apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device corresponding to the service system testing apparatus provided in the embodiment of fig. 4.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the examples of the present invention and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise, and "a plurality" typically includes at least two.
It should be understood that the term "and/or" as used herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
It is also noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a good or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such good or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a commodity or system that includes the element.
With the development of service types and service ranges, technicians need to continuously update the current service systems. In order to ensure that the updated service system can stably operate, the updated service system needs to be tested, and particularly, whether the functions of each calling interface are normal needs to be mainly tested. It is easy to understand that different service systems are often assigned to different service module workers to write or modify, and then problems such as inconsistent interface types may occur, which may cause errors in calling and may not meet normal application requirements. If a test result of the test failure occurs in the test process, a tester is required to investigate the reason of the test failure, especially when the calling relationship of the service system is complex, the inspector is required to know the internal logic of each service system and the calling relationship between different service systems, a great deal of effort and time are required, and the inspected result is not necessarily accurate. Therefore, a scheme for ensuring efficient and orderly operation of the service system test process is provided.
Fig. 1 is a schematic flow chart of a service system testing method according to an embodiment of the present application. As shown in fig. 1, the method comprises the steps of:
101: and testing the calling interface to be tested by using the test case.
102: and collecting the test result of the test failure.
103: and in the test result of the test failure, generating a multi-level service system log which has a cascade relation with the test result of the test failure according to the call relation among the call interfaces to be tested.
In practical application, a plurality of service systems may have complex calling relationships, and when a certain service system is to be tested, the service system may be affected by other service systems having calling relationships. Therefore, when the test case is used for testing the call interface to be tested, various problems which cannot be expected in advance are inevitably caused. If a problem occurs in the test process, the problem needs to be checked, and a related service system needs to be checked according to a calling relation in the checking process. It is easily understood that the purpose of the test is to find and solve problems, and therefore, when collecting the test results, it is necessary to collect not only the test results of normally completed tests but also the test results of failed tests.
The process of troubleshooting test results that fail testing is often cumbersome. Therefore, in order to simplify the difficulty of the testing personnel in checking the testing problems, the system logs of the related services with the testing results of failure testing can be output when the testing results are output, so that the problems can be found conveniently, the log checking is not required to be exported one by one, and the efficiency of solving the testing problems can be effectively improved.
In one or more embodiments of the present application, the testing the interface to be tested by using the test case includes: obtaining a test case corresponding to a to-be-tested calling interface, wherein the to-be-tested calling interface is an interface of a service system with a calling relation; and testing the calling interface to be tested by using the test case.
In practical application, some call interfaces to be tested do not have a call relationship, or only have a first-level call relationship, so that the test difficulty of the call interfaces to be tested is low. Even if a test problem occurs, the problem can be quickly checked and solved. However, in a complicated service system, some call interfaces have a multi-level associated call relationship, and an emphasis test needs to be performed on the call interfaces to be tested, and the call relationship needs to be fully considered when setting a test case.
The following illustrates how to set an appropriate test case according to the call relation. Fig. 2 is a schematic flowchart of a method for determining a test case according to an embodiment of the present application. As can be seen from fig. 2, the obtaining of the test case corresponding to the to-be-tested call interface, where the to-be-tested call interface is an interface of a service system having a call relationship, includes: 201: and determining the to-be-tested calling interface with a calling relation. 202: and sending the interface to be tested with the calling relation to the receiving party. 203: and receiving the test case provided by the receiver.
It is easy to understand that there are multiple parameter transmissions for the interface to be tested, and in order to ensure that the test can be performed smoothly, these parameters are required to be correct. However, each service system has a corresponding responsible person, and the responsible person (i.e., the receiving party) has the best knowledge about its own service system, but not the best knowledge about other service systems having direct or indirect calling relationships. Therefore, it is necessary for a plurality of receivers having a call relationship to confirm parameters and test cases for a test in common, thereby ensuring smooth completion of the test. Therefore, the time cost and the labor cost for the testers or other personnel to be familiar with the calling interface to be tested and the service system to be tested are avoided, and the testing efficiency and the testing accuracy can be improved.
In one or more examples of the present application, the generating a multi-level service system log having a cascade relationship with a test result of the test failure includes: and generating an assertion log, a system interface log and an analysis log of the multi-stage service system corresponding to the test result of the test failure.
In the testing process, in order to facilitate subsequent analysis and problem troubleshooting on the test result of the test failure, it is necessary to comprehensively output relevant test information, such as an assertion log and a system log of the tested service system, and an analysis log having a call relationship with the tested service system.
It should be noted that, the specific process of obtaining the analysis log with call relation of the tested service system is as follows. The generating a multi-level service system log having a cascade relation with the test result of the test failure according to the call relation between the call interfaces to be tested includes: determining the test result as the calling interface to be tested which fails to test; determining a first-stage service system having a calling relation with the to-be-tested calling interface and a second-stage service system having a calling relation with the first-stage service system; and generating the analysis log based on the log of the first-level service system and the log of the second-level service system.
First, it should be noted that in the present embodiment, the call relationship of the interface to be tested has only two levels, but there may be a multi-level call relationship in practical application. The embodiment is to illustrate how to obtain the analysis log in the tested service system with a multi-level calling relationship.
In order to help a tester to more comprehensively and accurately master other service systems related to a test result and thus help the tester to find a problem more quickly, not only logs related to a tested service need to be output, but also logs of a service system with a multi-level calling relationship need to be output as analysis logs to help the tester to complete problem analysis.
In one or more embodiments of the present application, the testing the interface to be tested by using the test case includes: the test case is utilized to assert a return state code and a response field of the to-be-tested calling interface; according to the calling relation, a test case state code and a response field of a service system which has the calling relation with the service system corresponding to the calling interface to be tested are asserted; the test results including the assertion log are output.
The internal script of each system returns a state code to the interface to be tested, and the response field is asserted; when the upstream system calls the test script of the downstream system to test, the assertion log of the downstream system interface script is output, and the state code and the response field of the test script of the downstream system are asserted at the calling level,
when an interface abnormality occurs, the whole operation of the script is stopped firstly, an assertion log in a downstream system is thrown upwards, and when the current system is detected to be thrown abnormally, an upstream call directly outputs the received abnormality on an analysis report. The tester can quickly locate the problem according to the analysis report.
In practical application, an assertion statement assert is followed by any legal expression, the assertion statement makes a judgment, if the result is true, the statement does nothing, if the result is false, the assertion statement throws an exception assertineror, if the result is false, an explanatory statement is added after the assertion statement to explain the reason of some exception, and when some exception occurs, the explanatory statement is thrown as the exception.
In one or more embodiments of the present application, after generating a multi-level service system log having a cascade relationship with the test result of the test failure, the method further includes: sending the multistage service system log with the test result of each test failure having the cascade relation to the corresponding receiver through the mail address of the receiver; wherein the receiver has a corresponding relationship with the service system.
It should be noted that the receiving party mentioned herein refers to a person in charge of the corresponding service system, and can compare and understand the logical relationship in the service system, so as to send the test result to the corresponding receiving party. When sending the test result, all the test results can be sent to the receiving party, and the test result can also be split according to the service system and sent in a targeted manner. For example, if the current test result includes test results of six service systems, and if the test results of 5 service systems have a problem, the test result of the corresponding service system is sent to the corresponding receiving party, so that the receiving party can quickly find the problem according to the received mail and assist in completing the problem solution. If a problem may be associated with multiple business systems, the test results may be sent to multiple recipients simultaneously by mail.
In practical application, according to the importance degree of the test result of the test failure, marking is carried out in the mail through marking information; and sending the test result carrying the labeling information to the corresponding receiver.
In order to facilitate understanding of the technical solutions of the present application, the following specifically exemplifies implementation processes of the technical solutions of the present application. Fig. 3 is a schematic diagram illustrating a testing process according to an embodiment of the present application. As can be seen from fig. 3, the main process test cases of the business system to be tested are first sorted, and then the test cases are divided according to the business system. Since the interface to be tested may involve multiple business systems, all people in charge of the multi-business system are required to determine the test case, the parameter type of the interface to be tested, and the like. Each business system responsible person facilitates interface use cases (usually XML formatted files). Each service system writes and calls an interface script, prints different assertion logs, system interface logs, design analysis logs and the like aiming at different service scenes. And (4) accessing the final script to a benchmark system (the benchmark system is a framework for the jenkins secondary packaging). At the time of testing, the final script can be executed regularly or manually. And sending the produced test report to a corresponding receiver through a mail, so that the receiver can quickly analyze the test problem and solve the problem according to the relevant logs in the test result.
Based on the same idea, the embodiment of the application further provides a service system testing device. Fig. 4 is a schematic structural diagram of a service system testing apparatus according to an embodiment of the present application. As can be seen from fig. 4, the device comprises:
and the test module 41 is configured to test the interface to be tested by using the test case.
And the collection module 42 is used for collecting the test result of the test failure.
A generating module 43, configured to generate, in the test result of the test failure, a multi-level service system log having a cascade relationship with the test result of the test failure according to the call relationship between the call interfaces to be tested.
Optionally, the testing module 41 is configured to obtain a test case corresponding to a to-be-tested call interface, where the to-be-tested call interface is an interface of a service system having a call relationship; and testing the calling interface to be tested by using the test case.
Optionally, the testing module 41 is further configured to determine the to-be-tested calling interface with a calling relationship;
sending the interface to be tested with the calling relation to the receiving party;
and receiving the test case provided by the receiver.
Optionally, the generating module 43 is configured to generate an assertion log of the service system, a system interface log, and an analysis log of the multi-stage service system, which correspond to the test result of the test failure.
Optionally, the generating module 43 is configured to determine that the test result is the test-failed call interface to be tested; determining a first-stage service system having a calling relation with the to-be-tested calling interface and a second-stage service system having a calling relation with the first-stage service system; and generating the analysis log based on the log of the first-level service system and the log of the second-level service system.
Optionally, the test module 41 is configured to assert a return status code and a response field of the to-be-tested call interface by using the test case; according to the calling relation, a test case state code and a response field of a service system which has the calling relation with the service system corresponding to the calling interface to be tested are asserted; the test results including the assertion log are output.
Optionally, the generating module 43 is configured to send, to the corresponding receiving party, the multi-level service system log in which the test result of each test failure has a cascade relationship through the receiving party email address; wherein the receiver has a corresponding relationship with the service system.
Based on the embodiment, the test case is used for testing the calling interface to be tested; collecting test results of test failure; and in the test result of the test failure, generating a multi-level service system log which has a cascade relation with the test result of the test failure according to the call relation among the call interfaces to be tested. By the scheme, when the service system is tested, the current calling interface to be tested is tested, the calling relation among the service systems is considered, the service system with the calling relation is tested, if the test fails, the service system with the current test failure or the log related to the calling interface to be tested is output, and the log related to other service systems with the calling relation is output, so that the efficiency of processing the test problem can be effectively improved.
In a possible design, the structure of the service system testing apparatus shown in fig. 4 may be implemented as an electronic device, and as shown in fig. 5, the electronic device corresponding to the service system testing apparatus provided in the embodiment shown in fig. 4 may include: a processor 51, a memory 52, wherein the memory 52 is used for storing one or more computer instructions, and when the one or more computer instructions are executed by the processor 51, the steps performed by the server in the foregoing embodiments are implemented.
Optionally, the electronic device may further include a communication interface 53 for communicating with other devices.
In addition, an embodiment of the present invention provides a computer storage medium, which is used to store a computer program, and when the computer program is executed, the client implements the service system testing method in the embodiment shown in fig. 1.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by adding a necessary general hardware platform, and of course, can also be implemented by a combination of hardware and software. With this understanding in mind, the above-described aspects and portions of the present technology which contribute substantially or in part to the prior art may be embodied in the form of a computer program product, which may be embodied on one or more computer-usable storage media having computer-usable program code embodied therein, including without limitation disk storage, CD-ROM, optical storage, and the like.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable resource updating apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable resource updating apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable resource updating apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable resource updating apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. A method for testing a service system, the method comprising:
testing the calling interface to be tested by using the test case;
collecting test results of test failure;
and in the test result of the test failure, generating a multi-level service system log which has a cascade relation with the test result of the test failure according to the call relation among the call interfaces to be tested.
2. The method of claim 1, wherein the testing the interface to be tested by using the test case comprises:
obtaining a test case corresponding to a to-be-tested calling interface, wherein the to-be-tested calling interface is an interface of a service system with a calling relation;
and testing the calling interface to be tested by using the test case.
3. The method of claim 2, wherein the obtaining of the test case corresponding to the interface to be tested is performed, where the interface to be tested is an interface of a business system having a call relationship, and includes:
determining the to-be-tested calling interface with a calling relation;
sending the interface to be tested with the calling relation to the receiving party;
and receiving the test case provided by the receiver.
4. The method of claim 1, wherein generating a multi-level service system log having a cascading relationship with the test result of the test failure comprises:
and generating an assertion log, a system interface log and an analysis log of the multi-stage service system corresponding to the test result of the test failure.
5. The method of claim 3, wherein the generating a multi-level service system log having a cascade relationship with the test result of the test failure according to the calling relationship between the calling interfaces to be tested comprises:
determining the test result as the calling interface to be tested which fails to test;
determining a first-stage service system having a calling relation with the to-be-tested calling interface and a second-stage service system having a calling relation with the first-stage service system;
and generating the analysis log based on the log of the first-level service system and the log of the second-level service system.
6. The method of claim 2, wherein the testing the interface to be tested with the test case comprises:
the test case is utilized to assert a return state code and a response field of the to-be-tested calling interface;
according to the calling relation, a test case state code and a response field of a service system which has the calling relation with the service system corresponding to the calling interface to be tested are asserted;
the test results including the assertion log are output.
7. The method of claim 1, wherein after generating a multi-level service system log having a cascading relationship with the test result of the test failure, further comprising:
sending the multistage service system log with the test result of each test failure having the cascade relation to the corresponding receiver through the mail address of the receiver; wherein the receiver has a corresponding relationship with the service system.
8. A business system testing apparatus, the apparatus comprising:
the test module is used for testing the calling interface to be tested by utilizing the test case;
the collection module is used for collecting test results of test failures;
and the generating module is used for generating a multi-level service system log which has a cascade relation with the test result of the test failure according to the call relation among the call interfaces to be tested in the test result of the test failure.
9. An electronic device, comprising: a processor, a memory for storing one or more computer instructions, wherein the one or more computer instructions, when executed by the processor, implement the business system testing method of any of claims 1 to 7.
10. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by one or more processors, causes the one or more processors to perform acts comprising:
testing the calling interface to be tested by using the test case;
collecting test results of test failure;
and in the test result of the test failure, generating a multi-level service system log which has a cascade relation with the test result of the test failure according to the call relation among the call interfaces to be tested.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011035775.4A CN112286791A (en) | 2020-09-27 | 2020-09-27 | Business system testing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011035775.4A CN112286791A (en) | 2020-09-27 | 2020-09-27 | Business system testing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112286791A true CN112286791A (en) | 2021-01-29 |
Family
ID=74422568
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011035775.4A Pending CN112286791A (en) | 2020-09-27 | 2020-09-27 | Business system testing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112286791A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116302907A (en) * | 2021-12-20 | 2023-06-23 | 网联清算有限公司 | Joint debugging test method and device for service system and joint debugging test system |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105868391A (en) * | 2012-09-25 | 2016-08-17 | 北京奇虎科技有限公司 | Method and device for recording log |
| CN109471845A (en) * | 2018-10-25 | 2019-03-15 | 深圳壹账通智能科技有限公司 | Log management method, server, and computer-readable storage medium |
| CN109885496A (en) * | 2019-02-20 | 2019-06-14 | 北京百佑科技有限公司 | Test log management method and system |
| CN110865944A (en) * | 2019-11-29 | 2020-03-06 | 江苏芯盛智能科技有限公司 | Data analysis method and device for test case, storage medium and test equipment |
-
2020
- 2020-09-27 CN CN202011035775.4A patent/CN112286791A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105868391A (en) * | 2012-09-25 | 2016-08-17 | 北京奇虎科技有限公司 | Method and device for recording log |
| CN109471845A (en) * | 2018-10-25 | 2019-03-15 | 深圳壹账通智能科技有限公司 | Log management method, server, and computer-readable storage medium |
| CN109885496A (en) * | 2019-02-20 | 2019-06-14 | 北京百佑科技有限公司 | Test log management method and system |
| CN110865944A (en) * | 2019-11-29 | 2020-03-06 | 江苏芯盛智能科技有限公司 | Data analysis method and device for test case, storage medium and test equipment |
Non-Patent Citations (1)
| Title |
|---|
| 孙更新: "《JAVA程序开发大全 基于MyEclipse平台+Structs+Hibernate+Spring主流框架开发》", 北京铁道出版社, pages: 74 - 76 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116302907A (en) * | 2021-12-20 | 2023-06-23 | 网联清算有限公司 | Joint debugging test method and device for service system and joint debugging test system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112650685B (en) | Automatic test method, device, electronic equipment and computer storage medium | |
| CN110460460B (en) | Service link fault positioning method, device and equipment | |
| CN112286790B (en) | Full link testing method, device, equipment and storage medium | |
| CN111209206B (en) | Automatic test method and system for software products | |
| CN111444093B (en) | Method and device for determining quality of project development process and computer equipment | |
| CN114064208A (en) | Method and device for detecting application service state, electronic equipment and storage medium | |
| US11526775B2 (en) | Automatically evaluating application architecture through architecture-as-code | |
| CN116866242A (en) | Switch regression testing method, device and medium | |
| CN114500249B (en) | Root cause positioning method and device | |
| CN111143151B (en) | Service monitoring method and device and electronic equipment | |
| CN110147313B (en) | Log output method and device | |
| CN113986764A (en) | Data checking test method and device, electronic equipment and storage medium | |
| CN112597143B (en) | Data detection method and device and electronic equipment | |
| CN112286791A (en) | Business system testing method, device, equipment and storage medium | |
| CN112286792A (en) | Interface testing method, device, equipment and storage medium | |
| CN111857802A (en) | Method, system and equipment for merging request group integration | |
| CN116756037A (en) | Abnormal code positioning system, method, equipment and computer readable storage medium | |
| CN113515401B (en) | Positioning and debugging method, system, electronic equipment and medium for abnormal transaction | |
| CN109360618A (en) | A kind of management method and system of electronization test report | |
| CN118276916A (en) | Application changing method and device | |
| CN115981901A (en) | Fault positioning method, equipment and medium for automatic test of switch | |
| CN112486823B (en) | Error code verification method and device, electronic equipment and readable storage medium | |
| CN115545677B (en) | Online process specification detection method and system based on automatic case execution condition | |
| CN112632056B (en) | Method and device for generating inspection rule | |
| CN110109809B (en) | Method and equipment for testing log auditing function according to syslog |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210129 |
|
| RJ01 | Rejection of invention patent application after publication |