CN112286792A - Interface testing method, device, equipment and storage medium - Google Patents
Interface testing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN112286792A CN112286792A CN202011035777.3A CN202011035777A CN112286792A CN 112286792 A CN112286792 A CN 112286792A CN 202011035777 A CN202011035777 A CN 202011035777A CN 112286792 A CN112286792 A CN 112286792A
- Authority
- CN
- China
- Prior art keywords
- test
- interface
- tested
- receiver
- calling
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 260
- 238000000034 method Methods 0.000 claims abstract description 24
- 238000004590 computer program Methods 0.000 claims description 11
- 238000002372 labelling Methods 0.000 claims description 4
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000004891 communication Methods 0.000 abstract description 8
- 230000000694 effects Effects 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 14
- 230000008569 process Effects 0.000 description 9
- 230000006870 function Effects 0.000 description 5
- 238000013515 script Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000009517 secondary packaging Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000008719 thickening Effects 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- 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)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses an interface testing method, an interface testing device, interface testing equipment and a storage medium. The method comprises the following steps: 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; determining a receiver mail address appointed by each interface to be tested; and collecting test results of test failures, and sending each test result of test failures to a corresponding receiver through the receiver email address. By the scheme, the calling interfaces to be tested are divided according to the service systems, the receivers of the service systems are determined, and if the test fails, the test result of the test failure is sent to the receivers of the service systems related to the test result by the mail, so that the test efficiency and the test effect can be effectively improved, and the communication cost and the workload of testers are reduced.
Description
Technical Field
The embodiment of the invention relates to the technical field of internet, in particular to an interface testing method, device, equipment and 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 interface testing efficiency is needed.
Disclosure of Invention
The embodiment of the invention provides an interface testing method, an interface testing device, equipment and a storage medium, and aims to improve the technical scheme of interface testing efficiency.
In a first aspect, an embodiment of the present invention provides an interface testing method, where the method 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;
determining a receiver mail address appointed by each interface to be tested;
and collecting test results of test failures, and sending each test result of test failures to a corresponding receiver through the receiver email address.
Optionally, obtaining a test case corresponding to a call interface to be tested, where the call interface is an interface of a service system having a call relationship, and the method 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 determining a mail address of a receiver specified by each interface to be tested includes:
determining service types respectively corresponding to the service systems to be tested, and dividing test cases according to the service types;
and determining a receiver for providing each test case and the mail address of the receiver according to the service type.
Optionally, the collecting test results of the test failures, and sending each test result of the test failures to the corresponding receiver through the receiver email address includes:
collecting test results of test failure in the test results of the to-be-tested calling interface;
determining the receivers corresponding to the test results of the test failure respectively according to the corresponding relation between the calling interface to be tested and the receivers;
and sending the test result of each test failure to the corresponding receiver through the mail address of the receiver.
Optionally, the sending the test result of each test failure to the corresponding receiver through the receiver email address includes:
marking the mail through marking information according to the importance degree of the test result of the test failure;
and sending the test result carrying the labeling information to the corresponding receiver.
Optionally, the method further comprises: and collecting test results which are tested successfully, and sending each test result which is tested successfully to the relevant receiving party with the calling relation through the mail address of the receiving party.
In a second aspect, an embodiment of the present invention provides an interface testing apparatus, including:
the system comprises an acquisition module, a test case acquisition module and a test result analysis module, wherein the acquisition module is used for acquiring a test case corresponding to a to-be-tested calling interface, and the to-be-tested calling interface is an interface of a service system with a calling relation;
the determining module is used for determining the mail address of the receiver appointed by each interface to be tested;
and the sending module is used for collecting the test results of the test failures and sending each test result of the test failures to the corresponding receiver through the mail address of the receiver.
In a third aspect, an embodiment of the present invention provides an electronic device, including a processor and a memory, where the memory is used to store one or more computer instructions, and when executed by the processor, the one or more computer instructions implement the interface 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:
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;
determining a receiver mail address appointed by each interface to be tested;
and collecting test results of test failures, and sending each test result of test failures to a corresponding receiver through the receiver email address.
In the embodiment of the invention, a test case corresponding to a to-be-tested calling interface is obtained, wherein the to-be-tested calling interface is an interface of a business system with a calling relation; determining a receiver mail address appointed by each interface to be tested; and collecting test results of test failures, and sending each test result of test failures to a corresponding receiver through the receiver email address. By the scheme, the calling interfaces to be tested are divided according to the service systems, the receivers of the service systems are determined, and if the test fails, the test result of the test failure is sent to the receivers of the service systems related to the test result by the mail, so that the test efficiency and the test effect can be effectively improved, and the communication cost and the workload of testers are reduced.
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 an interface 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 an interface testing apparatus according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an electronic device corresponding to the interface 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. For example, when a certain call interface to be tested relates to many different service systems, if a test failure problem needs to be handled, a tester needs to repeatedly confirm and communicate with many service parties, resulting in low communication efficiency and low test efficiency. Therefore, a scheme capable of improving the test efficiency of the calling interface is provided.
Fig. 1 is a schematic flowchart of an interface testing method according to an embodiment of the present application, and as shown in fig. 1, the method includes the following steps:
101: and acquiring 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.
102: and determining the mail address of a receiver appointed by each interface to be tested.
103: and collecting test results of test failures, and sending each test result of test failures to a corresponding receiver through the receiver email address.
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. After the collection is completed, in order to solve the problem, the test result which fails to test may be collected with emphasis and sent to each receiver by mail. Therefore, testers do not need to collect and analyze the problems, determine the business system corresponding to the problems and then find the business system responsible for face-to-face communication. By the aid of the scheme, test results of test failures can be automatically collected, then the test results of the test failures are sent to the corresponding receivers, test problems are solved by corresponding responsible persons, test efficiency can be effectively improved, test problem solving efficiency is improved, and consumption of test manpower and material resources can be effectively saved.
In a complicated service system, some calling interfaces have a multi-level associated calling relationship, and an important test needs to be performed on the calling interfaces to be tested, and the calling relationship also needs to be fully considered when a test case is set.
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 determining a mail address of a receiver specified by each of the interfaces to be tested includes: determining service types respectively corresponding to the service systems to be tested, and dividing test cases according to the service types; and determining a receiver for providing each test case and the mail address of the receiver according to the service type.
As described above, the service system has multiple levels of call relations, and the call relations are complicated, and different test cases are used for testing a certain service system. Therefore, after the corresponding service system person in charge (i.e., the requester) provides the test case, the test case needs to be classified into types. And the requesting party is also divided according to the service type, and the purpose of the division is to accurately send the test result to the corresponding requesting party through the mail.
In one or more embodiments of the present application, the collecting test results that fail the test, and sending each test result that fails the test to a corresponding recipient through the recipient email address includes: collecting test results of test failure in the test results of the to-be-tested calling interface; determining the receivers corresponding to the test results of the test failure respectively according to the corresponding relation between the calling interface to be tested and the receivers; and sending the test result of each test failure to the corresponding receiver through the mail address of the receiver.
As described above, before testing, the requestor and the test cases are divided according to the service type. However, it should be noted that, what is needed to divide the requester is to fully consider the association relationship between the service systems, in other words, although the requester only knows the service system in charge of the requester, the service systems are associated with each other. For example, a problem arises with a business system, but may be a problem caused by a called business system, and therefore, the calling relationship is considered sufficiently when sending the test result to the requester. If a certain test result cannot clearly determine which service system is a problem, the test result of the test failure can be sent to the receivers corresponding to the plurality of service systems associated with the certain test result. Thereby helping the tester to summon more relevant personnel to solve the problem.
In one or more embodiments of the present application, the sending the test result of each test failure to the corresponding receiver through the receiver email address includes: marking the mail through marking information according to the importance degree of the test result of the test failure; and sending the test result carrying the labeling information to the corresponding receiver.
In practical application, the test result can be distinguished into different levels of importance. For example, a certain test result is related to a plurality of business systems at the upstream and downstream, and the test result may be considered to be important, and if the test result is a test failure, the relevant receiver needs to be paid attention. Then, when sending the email, the user needs to send the email to a receiving party of a plurality of service systems with a call relationship, and when sending the email, the user needs to make an obvious mark in the email, so as to attract the attention of the receiving party. It should be noted that there are various ways of carrying the annotation information in the email, and the annotation information may be added in the email header or in the email body. The form of the label information may be various, for example, by adding a special symbol to the header, or by thickening or marking the text in the mail body with red. By the scheme, the requester can be promoted to assist in solving the test problem as soon as possible.
Based on the embodiment, a test case corresponding to a to-be-tested calling interface is obtained, wherein the to-be-tested calling interface is an interface of a business system with a calling relation; determining a receiver mail address appointed by each interface to be tested; and collecting test results of test failures, and sending each test result of test failures to a corresponding receiver through the receiver email address. By the scheme, the calling interfaces to be tested are divided according to the service systems, the receivers of the service systems are determined, and if the test fails, the test result of the test failure is sent to the receivers of the service systems related to the test result by the mail, so that the test efficiency and the test effect can be effectively improved, and the communication cost and the workload of testers are reduced.
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). And compiling interface scripts by each service system, and combining the scripts among the service systems into the same script in a jar packet form or an interface providing form. 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, an interface testing apparatus is further provided in the embodiments of the present application, and fig. 4 is a schematic structural diagram of the interface testing apparatus provided in the embodiments of the present application. As can be seen from fig. 4, the device comprises:
an obtaining module 41, 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;
a determining module 42, configured to determine a receiver email address specified by each of the interfaces to be tested;
and a sending module 43, configured to collect test results of test failures, and send each test result of test failure to a corresponding recipient through the recipient email address.
Optionally, the obtaining module 41 is configured to determine the to-be-tested call interface with a call 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 determining module 42 is further configured to determine service types respectively corresponding to the service systems to be tested, and divide the test cases according to the service types; and determining a receiver for providing each test case and the mail address of the receiver according to the service type.
Optionally, the sending module 43 is further configured to collect a test result of a test failure in the test results of the to-be-tested calling interface; determining the receivers corresponding to the test results of the test failure respectively according to the corresponding relation between the calling interface to be tested and the receivers; and sending the test result of each test failure to the corresponding receiver through the mail address of the receiver.
Optionally, the sending module 43 is further configured to label the email with the label information according to the importance degree of the test result of the test failure; and sending the test result carrying the labeling information to the corresponding receiver.
Optionally, the sending module 43 is further configured to collect test results that are successfully tested, and send each test result that is successfully tested to the relevant receiving party with the call relationship through the receiving party email address.
Based on the embodiment, a test case corresponding to a to-be-tested calling interface is obtained, wherein the to-be-tested calling interface is an interface of a business system with a calling relation; determining a receiver mail address appointed by each interface to be tested; and collecting test results of test failures, and sending each test result of test failures to a corresponding receiver through the receiver email address. By the scheme, the calling interfaces to be tested are divided according to the service systems, the receivers of the service systems are determined, and if the test fails, the test result of the test failure is sent to the receivers of the service systems related to the test result by the mail, so that the test efficiency and the test effect can be effectively improved, and the communication cost and the workload of testers are reduced.
In a possible design, the structure of the interface testing apparatus shown in fig. 4 may be implemented as an electronic device, and as shown in fig. 5, a schematic structural diagram of an electronic device corresponding to the interface 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 interface 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 (9)
1. An interface testing method, the method comprising:
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;
determining a receiver mail address appointed by each interface to be tested;
and collecting test results of test failures, and sending each test result of test failures to a corresponding receiver through the receiver email address.
2. The method of claim 1, wherein obtaining a test case corresponding to a call interface to be tested, wherein the call interface is an interface of a service system having a call relationship, comprises:
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.
3. The method of claim 1, wherein determining the recipient email address specified by each of the test call interfaces comprises:
determining service types respectively corresponding to the service systems to be tested, and dividing test cases according to the service types;
and determining a receiver for providing each test case and the mail address of the receiver according to the service type.
4. The method of claim 1, wherein collecting test results that fail testing and sending each test result that fails testing to a corresponding recipient via the recipient email address comprises:
collecting test results of test failure in the test results of the to-be-tested calling interface;
determining the receivers corresponding to the test results of the test failure respectively according to the corresponding relation between the calling interface to be tested and the receivers;
and sending the test result of each test failure to the corresponding receiver through the mail address of the receiver.
5. The method of claim 4, wherein said sending the test result of each of said failed tests to the corresponding recipient via said recipient email address comprises:
marking the mail through marking information according to the importance degree of the test result of the test failure;
and sending the test result carrying the labeling information to the corresponding receiver.
6. The method of claim 1, further comprising:
and collecting test results which are tested successfully, and sending each test result which is tested successfully to the relevant receiving party with the calling relation through the mail address of the receiving party.
7. An interface testing apparatus, the apparatus comprising:
the system comprises an acquisition module, a test case acquisition module and a test result analysis module, wherein the acquisition module is used for acquiring a test case corresponding to a to-be-tested calling interface, and the to-be-tested calling interface is an interface of a service system with a calling relation;
the determining module is used for determining the mail address of the receiver appointed by each interface to be tested;
and the sending module is used for collecting the test results of the test failures and sending each test result of the test failures to the corresponding receiver through the mail address of the receiver.
8. 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 interface testing method of any of claims 1 to 6.
9. 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:
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;
determining a receiver mail address appointed by each interface to be tested;
and collecting test results of test failures, and sending each test result of test failures to a corresponding receiver through the receiver email address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011035777.3A CN112286792A (en) | 2020-09-27 | 2020-09-27 | Interface testing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011035777.3A CN112286792A (en) | 2020-09-27 | 2020-09-27 | Interface testing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112286792A true CN112286792A (en) | 2021-01-29 |
Family
ID=74422569
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011035777.3A Pending CN112286792A (en) | 2020-09-27 | 2020-09-27 | Interface testing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112286792A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112486719A (en) * | 2020-12-14 | 2021-03-12 | 上海悦易网络信息技术有限公司 | Method and equipment for RPC interface call failure processing |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104581806A (en) * | 2014-12-19 | 2015-04-29 | 联动优势电子商务有限公司 | Method and terminal for monitoring service system |
| CN107797919A (en) * | 2017-07-24 | 2018-03-13 | 平安普惠企业管理有限公司 | The method and computing device of a kind of automatic test |
| CN107807869A (en) * | 2017-10-16 | 2018-03-16 | 微梦创科网络科技（中国）有限公司 | A kind of test system and method for testing |
| CN109344076A (en) * | 2018-10-22 | 2019-02-15 | 浙江执御信息技术有限公司 | A kind of automatic interface testing method and its device based on JMeter and Jenkins |
| CN109960658A (en) * | 2019-03-29 | 2019-07-02 | 北京金山云网络技术有限公司 | Application programming interface test method, device, electronic equipment and storage medium |
| CN110147312A (en) * | 2019-04-09 | 2019-08-20 | 平安科技（深圳）有限公司 | Software development test method, device, computer installation and storage medium |
| CN110287105A (en) * | 2019-05-22 | 2019-09-27 | 平安普惠企业管理有限公司 | Document version test method, device, equipment and readable storage medium storing program for executing |
| CN110471839A (en) * | 2019-07-11 | 2019-11-19 | 平安普惠企业管理有限公司 | Fixed time test task control method, device, computer equipment and storage medium |
| CN110764993A (en) * | 2019-09-02 | 2020-02-07 | 深圳壹账通智能科技有限公司 | Automatic testing method and terminal equipment |
| CN111444080A (en) * | 2019-01-17 | 2020-07-24 | 北京京东尚科信息技术有限公司 | Continuous testing method and device |
-
2020
- 2020-09-27 CN CN202011035777.3A patent/CN112286792A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104581806A (en) * | 2014-12-19 | 2015-04-29 | 联动优势电子商务有限公司 | Method and terminal for monitoring service system |
| CN107797919A (en) * | 2017-07-24 | 2018-03-13 | 平安普惠企业管理有限公司 | The method and computing device of a kind of automatic test |
| CN107807869A (en) * | 2017-10-16 | 2018-03-16 | 微梦创科网络科技（中国）有限公司 | A kind of test system and method for testing |
| CN109344076A (en) * | 2018-10-22 | 2019-02-15 | 浙江执御信息技术有限公司 | A kind of automatic interface testing method and its device based on JMeter and Jenkins |
| CN111444080A (en) * | 2019-01-17 | 2020-07-24 | 北京京东尚科信息技术有限公司 | Continuous testing method and device |
| CN109960658A (en) * | 2019-03-29 | 2019-07-02 | 北京金山云网络技术有限公司 | Application programming interface test method, device, electronic equipment and storage medium |
| CN110147312A (en) * | 2019-04-09 | 2019-08-20 | 平安科技（深圳）有限公司 | Software development test method, device, computer installation and storage medium |
| CN110287105A (en) * | 2019-05-22 | 2019-09-27 | 平安普惠企业管理有限公司 | Document version test method, device, equipment and readable storage medium storing program for executing |
| CN110471839A (en) * | 2019-07-11 | 2019-11-19 | 平安普惠企业管理有限公司 | Fixed time test task control method, device, computer equipment and storage medium |
| CN110764993A (en) * | 2019-09-02 | 2020-02-07 | 深圳壹账通智能科技有限公司 | Automatic testing method and terminal equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112486719A (en) * | 2020-12-14 | 2021-03-12 | 上海悦易网络信息技术有限公司 | Method and equipment for RPC interface call failure processing |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108628748B (en) | Automatic test management method and automatic test management system | |
| CN105335310B (en) | Interface definition method and data transmission method and device | |
| CN107797919A (en) | The method and computing device of a kind of automatic test | |
| CN111314137A (en) | Information communication network automation operation and maintenance method, device, storage medium and processor | |
| CN106095688A (en) | A kind of software performance testing method and device | |
| CN108038039A (en) | The method and micro services system of record log | |
| CN116866242A (en) | Switch regression testing method, device and medium | |
| CN111143151B (en) | Service monitoring method and device and electronic equipment | |
| CN112286792A (en) | Interface testing method, device, equipment and storage medium | |
| CN113592305A (en) | Test method, test device, electronic device, and storage medium | |
| CN110716912A (en) | SQL performance detection method and server | |
| CN117234916A (en) | Workflow application testing method and device, electronic equipment and storage medium | |
| CN110147313B (en) | Log output method and device | |
| CN116383055A (en) | Financial scene testing method and device, processor and electronic equipment | |
| CN116527553A (en) | Processing method, system and storage medium for automatic test report of switch | |
| CN111045915A (en) | Safety test method and device based on product function test case | |
| CN113656003A (en) | Software package management method and related equipment | |
| CN110618943B (en) | Security service test method and device, electronic equipment and readable storage medium | |
| CN115203178A (en) | Data quality inspection method and device, electronic equipment and storage medium | |
| CN114020645A (en) | Test method, device, equipment, readable storage medium and computer program product | |
| CN112286791A (en) | Business system testing method, device, equipment and storage medium | |
| CN113157528A (en) | Operation change monitoring method and device based on big data service cloud | |
| CN113127362A (en) | Object testing method, object testing device, electronic device, and readable storage medium | |
| CN112363944A (en) | Method and equipment for comparing return values of multiple environment interfaces | |
| CN112597143B (en) | Data detection method and device and electronic equipment |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210129 |