CN115878487A - Interface checking method and device - Google Patents
Interface checking method and device Download PDFInfo
- Publication number
- CN115878487A CN115878487A CN202211686986.3A CN202211686986A CN115878487A CN 115878487 A CN115878487 A CN 115878487A CN 202211686986 A CN202211686986 A CN 202211686986A CN 115878487 A CN115878487 A CN 115878487A
- Authority
- CN
- China
- Prior art keywords
- interface
- matching
- matching result
- subsystem
- system simulation
- 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
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application provides an interface checking method and device, and the method comprises the following steps: acquiring an interface of a system simulation platform, an interface of an automatic cloud test platform, a subsystem Git warehouse interface and an interface case in the automatic cloud test platform; matching an interface of a system simulation platform with an interface of an automatic cloud test platform to obtain a first matching result; matching the interface of the subsystem Git warehouse with the interface of the system simulation platform to obtain a second matching result; matching the interface case with a gateway (Git) warehouse interface of the subsystem to obtain a third matching result; and summarizing the first matching result, the second matching result and the third matching result to obtain an interface checking result. Therefore, by implementing the implementation mode, the interface can be automatically checked in time, manual participation is not needed, manpower and material resources are saved, the problems of omission and the like caused by manual checking are avoided, and the interface testing efficiency is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to an interface checking method and apparatus.
Background
At present, the stock interfaces of each subsystem and the newly added interfaces of each version are more, and the interfaces of different systems need to be checked before interface testing. In practice, the existing method usually adopts a manual checking method to find that whether corresponding automatic cases are input into interfaces of different platforms and systems is checked simply by manual checking, and whether each newly added interface is timely and correspondingly input into different platforms, so that time and labor are wasted, and omission is easy to generate. Therefore, the existing method consumes manpower and material resources, has low checking timeliness and is easy to omit, thereby reducing the interface testing efficiency.
Disclosure of Invention
An object of the embodiment of the present application is to provide an interface checking method and apparatus, which can perform automatic interface checking in time, do not need manual participation, save manpower and material resources, and avoid the problems of omission and the like caused by manual checking, thereby improving interface testing efficiency.
A first aspect of an embodiment of the present application provides an interface checking method, including:
acquiring an interface of a system simulation platform, an interface of an automatic cloud test platform, a subsystem Git warehouse interface and an interface case in the automatic cloud test platform;
matching an interface of the system simulation platform with an interface of the automatic cloud test platform to obtain a first matching result;
matching the subsystem Git warehouse interface with the interface of the system simulation platform to obtain a second matching result;
matching the interface case with the subsystem Git warehouse interface to obtain a third matching result;
and summarizing the first matching result, the second matching result and the third matching result to obtain an interface checking result.
In the implementation process, the method can preferentially acquire an interface of a system simulation platform, an interface of an automatic cloud test platform, a subsystem Git warehouse interface and an interface case in the automatic cloud test platform; then, matching an interface of the system simulation platform with an interface of the automatic cloud test platform to obtain a first matching result; then, matching the interface of the subsystem Git warehouse with the interface of the system simulation platform to obtain a second matching result; matching the interface case with a Git warehouse interface of the subsystem to obtain a third matching result; and finally, summarizing the first matching result, the second matching result and the third matching result to obtain an interface checking result. Therefore, the method can be used for automatically checking the interface in time without manual participation, saves manpower and material resources, avoids the problems of omission and the like caused by manual checking, and improves the interface testing efficiency.
Further, after the interface of the system simulation platform is matched with the interface of the automated cloud test platform to obtain a first matching result, the method further includes:
determining a successfully matched interface set according to the first matching result; wherein the interface of the system simulation platform comprises the matching success interface set;
and when the interfaces in the successfully matched interface set are all recorded into the corresponding automatic cases, marking the interfaces in the successfully matched interface set as realized automatic interfaces.
Further, the matching the subsystem Git warehouse interface with the interface of the system simulation platform to obtain a second matching result includes:
determining a subsystem interface corresponding to the system simulation platform according to the interface of the system simulation platform;
and matching the subsystem Git warehouse interface with a subsystem interface corresponding to the system simulation platform to obtain a second matching result.
Further, after the matching the subsystem Git warehouse interface with the interface of the system simulation platform to obtain a second matching result, the method further comprises:
determining a first unmatched successful interface set according to the second matching result; wherein the subsystem Git repository interface comprises the first set of unmatched successful interfaces;
sending interface maintenance prompt information comprising the first unmatched successful interface set; and the maintenance interface prompt message is used for prompting that the interface data matched with the first unmatched successful interface set is maintained on the system simulation platform.
Further, after the matching the interface case with the subsystem Git warehouse interface to obtain a third matching result, the method further comprises:
determining a second unmatched successful interface set in the subsystem Git warehouse interface according to the third matching result;
sending case entry prompt information comprising the second unmatched successful interface set; and the case entry prompt information is used for prompting the entry of the automated case corresponding to the second unmatched successful interface set in the automated cloud test platform.
Further, after the summarizing the first matching result, the second matching result, and the third matching result to obtain an interface checking result, the method further includes:
sorting the interface checking results according to different subsystems to obtain sorted data;
and outputting the classified and sorted data.
A second aspect of the embodiments of the present application provides an interface checking apparatus, including:
the system comprises an acquisition unit, a storage unit and a processing unit, wherein the acquisition unit is used for acquiring an interface of a system simulation platform, an interface of an automatic cloud test platform, a subsystem Git warehouse interface and an interface case in the automatic cloud test platform;
the first matching unit is used for matching an interface of the system simulation platform with an interface of the automatic cloud test platform to obtain a first matching result;
the second matching unit is used for matching the interface of the subsystem Git warehouse with the interface of the system simulation platform to obtain a second matching result;
the third matching unit is used for matching the interface case with the subsystem Git warehouse interface to obtain a third matching result;
and the summarizing unit is used for summarizing the first matching result, the second matching result and the third matching result to obtain an interface checking result.
In the implementation process, the device can acquire an interface of a system simulation platform, an interface of an automatic cloud test platform, a subsystem Git warehouse interface and an interface case in the automatic cloud test platform through an acquisition unit; matching an interface of a system simulation platform with an interface of an automatic cloud test platform through a first matching unit to obtain a first matching result; matching the Git warehouse interface of the subsystem with an interface of a system simulation platform through a second matching unit to obtain a second matching result; matching the interface case with a gateway (Git) warehouse interface of the subsystem through a third matching unit to obtain a third matching result; and finally, summarizing the first matching result, the second matching result and the third matching result through a summarizing unit to obtain an interface checking result. Therefore, the device can automatically check the interface in time, does not need manual participation, saves manpower and material resources, avoids the problems of omission and the like caused by manual checking, and improves the interface testing efficiency.
Further, the interface checking device further includes:
the first determining unit is used for determining a successfully matched interface set according to a first matching result after the interface of the system simulation platform is matched with the interface of the automatic cloud test platform to obtain the first matching result; wherein the interface of the system simulation platform comprises the matching success interface set;
and the marking unit is used for marking the interfaces in the successfully matched interface set as realized automatic interfaces when the interfaces in the successfully matched interface set are all recorded into the corresponding automatic cases.
Further, the second matching unit includes:
the determining subunit is used for determining a subsystem interface corresponding to the system simulation platform according to the interface of the system simulation platform;
and the matching subunit is used for matching the subsystem Git warehouse interface with the subsystem interface corresponding to the system simulation platform to obtain a second matching result.
Further, the interface checking device further includes:
the second determining unit is used for determining a first unmatched successful interface set according to a second matching result after the subsystem Git warehouse interface is matched with the interface of the system simulation platform to obtain the second matching result; wherein the subsystem Git repository interface comprises the first set of unmatched successful interfaces;
a sending unit, configured to send interface maintenance prompt information including the first unmatched successful interface set; and the maintenance interface prompt information is used for prompting the system simulation platform to maintain the interface data matched with the first unmatched successful interface set.
Further, the interface checking device further includes:
a third determining unit, configured to determine, after the interface case is matched with the subsystem Git warehouse interface to obtain a third matching result, a second unmatched successful interface set in the subsystem Git warehouse interface according to the third matching result;
the sending unit is further configured to send case entry prompt information including the second unmatched successful interface set; and the case entry prompt information is used for prompting the entry of the automated case corresponding to the second unmatched successful interface set in the automated cloud test platform.
Further, the interface checking device further includes:
the sorting unit is used for sorting the interface checking results according to different subsystems after the first matching result, the second matching result and the third matching result are gathered to obtain the interface checking results, so that classified sorting data are obtained;
and the output unit is used for outputting the classified and sorted data.
A third aspect of the embodiments of the present application provides an electronic device, including a memory and a processor, where the memory is used to store a computer program, and the processor runs the computer program to make the electronic device execute the interface checking method according to any one of the first aspect of the embodiments of the present application.
A fourth aspect of the embodiments of the present application provides a computer-readable storage medium, which stores computer program instructions, and when the computer program instructions are read and executed by a processor, the computer program instructions perform the interface checking method according to any one of the first aspect of the embodiments of the present application.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments of the present application will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and that those skilled in the art can also obtain other related drawings based on the drawings without inventive efforts.
Fig. 1 is a schematic flowchart of an interface checking method according to an embodiment of the present application;
fig. 2 is a schematic flowchart of another interface checking method according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an interface checking apparatus according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of another interface checking apparatus according to an embodiment of the present application;
fig. 5 is a schematic flowchart illustrating an example of an interface checking method according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined or explained in subsequent figures. Meanwhile, in the description of the present application, the terms "first", "second", and the like are used only for distinguishing the description, and are not to be construed as indicating or implying relative importance.
Example 1
Referring to fig. 1, fig. 1 is a schematic flow chart illustrating an interface checking method according to the present embodiment. The interface checking method comprises the following steps:
s101, obtaining an interface of a system simulation platform, an interface of an automatic cloud test platform, a subsystem Git warehouse interface and an interface case in the automatic cloud test platform.
S102, matching an interface of the system simulation platform with an interface of the automatic cloud test platform to obtain a first matching result.
S103, matching the interface of the subsystem Git warehouse with the interface of the system simulation platform to obtain a second matching result.
And S104, matching the interface case with a Git warehouse interface of the subsystem to obtain a third matching result.
And S105, summarizing the first matching result, the second matching result and the third matching result to obtain an interface checking result.
In this embodiment, the method can be applied to the financial field.
In this embodiment, the execution subject of the method may be a computing device such as a computer and a server, and is not limited in this embodiment.
In this embodiment, an execution subject of the method may also be an intelligent device such as a smart phone and a tablet computer, which is not limited in this embodiment.
Therefore, by implementing the interface checking method described in this embodiment, developers and testers can know the degree of automation completion of the interface more clearly, so that the degree of automation completion of the newly added interface of the version does not need to be counted manually, and an effect of automatically reminding relevant personnel to enter an interface case is achieved. Meanwhile, the efficiency can be improved, the labor is saved, the effect of reminding the development and maintenance of the interface document is achieved, and the omission of the interface is effectively avoided.
Example 2
Referring to fig. 2, fig. 2 is a schematic flow chart of an interface checking method according to the present embodiment. The interface checking method comprises the following steps:
s201, obtaining an interface of a system simulation platform, an interface of an automatic cloud test platform, a subsystem Git warehouse interface and an interface case in the automatic cloud test platform.
S202, matching an interface of the system simulation platform with an interface of the automatic cloud test platform to obtain a first matching result.
S203, determining a successfully matched interface set according to the first matching result; the interface of the system simulation platform comprises a matching success interface set.
And S204, when the interfaces in the successfully matched interface set are all recorded into the corresponding automatic cases, marking the interfaces in the successfully matched interface set as realized automatic interfaces.
S205, determining a subsystem interface corresponding to the system simulation platform according to the interface of the system simulation platform.
And S206, matching the subsystem Git warehouse interface with a subsystem interface corresponding to the system simulation platform to obtain a second matching result.
S207, determining a first unmatched successful interface set according to a second matching result; wherein the subsystem Git repository interface comprises a first set of unmatched successful interfaces.
S208, sending interface maintenance prompt information comprising the first unmatched successful interface set; and the maintenance interface prompt information is used for prompting that interface data matched with the first unmatched successful interface set is maintained on the system simulation platform.
And S209, matching the interface case with a Git warehouse interface of the subsystem to obtain a third matching result.
And S210, determining a second unmatched successful interface set in the subsystem Git warehouse interface according to the third matching result.
S211, sending case entry prompt information comprising a second unmatched successful interface set; and the case entry prompt information is used for prompting the entry of the automated case corresponding to the second unmatched successful interface set in the automated cloud test platform.
S212, summarizing the first matching result, the second matching result and the third matching result to obtain an interface checking result.
And S213, sorting the interface checking results according to different subsystems to obtain sorted data.
And S214, outputting the classified and sorted data.
In the embodiment, the method pulls out all the interfaces of each subsystem in an Arena platform, a Git warehouse and an Automan automation platform, performs full interface path matching,
for example, the method screens out the interfaces which do not have three platforms at the same time, and the specific implementation flow is as follows:
(1) Pulling out an interface of the Arena platform, matching the interface full path with an interface in an Automan automation platform (an automation cloud test platform), and marking the interface as the automation if the corresponding interface is matched and a corresponding automation case is recorded;
(2) Pulling an interface in each subsystem Git warehouse according to the version, matching the interface with a subsystem interface corresponding to the Arena platform, and if the interface is not matched, reminding a corresponding code submitter of the mail to timely maintain the interface to the Arena platform;
(3) Pulling an interface in a Git warehouse of each subsystem according to the version, matching the interface with an interface case in an Automan automation platform, and if the interface case is not matched, reminding a corresponding test responsible person by using a mail, and timely inputting an automation case;
(4) And sorting all results according to different subsystems, sorting and outputting the results to a page table and providing the page table for related personnel to view.
Referring to fig. 5, fig. 5 shows an exemplary flow of an interface checking method.
In this embodiment, the execution subject of the method may be a computing device such as a computer and a server, and is not limited in this embodiment.
In this embodiment, an execution subject of the method may also be an intelligent device such as a smart phone and a tablet computer, which is not limited in this embodiment.
Therefore, by implementing the interface checking method described in this embodiment, developers and testers can know the degree of automation completion of the interface more clearly, so that the degree of automation completion of the newly added interface of the version does not need to be counted manually, and an effect of automatically reminding relevant personnel to enter an interface case is achieved. Meanwhile, the efficiency can be improved, the labor is saved, the effect of reminding the development and maintenance of the interface document is achieved, and the omission of the interface is effectively avoided.
Example 3
Referring to fig. 3, fig. 3 is a schematic structural diagram of an interface checking device provided in this embodiment. As shown in fig. 3, the interface collating apparatus includes:
the acquiring unit 310 is used for acquiring an interface of a system simulation platform, an interface of an automatic cloud testing platform, a subsystem Git warehouse interface and an interface case in the automatic cloud testing platform;
the first matching unit 320 is configured to match an interface of the system simulation platform with an interface of the automated cloud test platform to obtain a first matching result;
the second matching unit 330 is configured to match the interface of the subsystem Git warehouse with the interface of the system simulation platform to obtain a second matching result;
the third matching unit 340 is configured to match the interface case with a Git warehouse interface of the subsystem to obtain a third matching result;
the summarizing unit 350 is configured to summarize the first matching result, the second matching result, and the third matching result to obtain an interface checking result.
In this embodiment, for the explanation of the interface checking device, reference may be made to the description in embodiment 1 or embodiment 2, and details are not repeated in this embodiment.
Therefore, by implementing the interface checking device described in this embodiment, developers and testers can know the automation completion degree of the interface more clearly, so that the automation completion degree of the newly added interface of the version does not need to be counted manually, and an effect of automatically reminding relevant personnel to input the interface case is achieved. Meanwhile, the efficiency can be improved, the labor is saved, the effect of reminding the development and maintenance of the interface document is achieved, and omission of the interface is effectively avoided.
Example 4
Referring to fig. 4, fig. 4 is a schematic structural diagram of an interface checking device provided in this embodiment. As shown in fig. 4, the interface collating apparatus includes:
the acquiring unit 310 is used for acquiring an interface of a system simulation platform, an interface of an automatic cloud testing platform, a subsystem Git warehouse interface and an interface case in the automatic cloud testing platform;
the first matching unit 320 is configured to match an interface of the system simulation platform with an interface of the automated cloud test platform to obtain a first matching result;
the second matching unit 330 is configured to match the interface of the subsystem Git warehouse with the interface of the system simulation platform to obtain a second matching result;
the third matching unit 340 is configured to match the interface case with a Git warehouse interface of the subsystem to obtain a third matching result;
the summarizing unit 350 is configured to summarize the first matching result, the second matching result, and the third matching result to obtain an interface checking result.
As an optional implementation manner, the interface checking apparatus further includes:
the first determining unit 360 is configured to determine a successfully matched interface set according to a first matching result after matching an interface of the system simulation platform with an interface of the automated cloud test platform to obtain the first matching result; the interface of the system simulation platform comprises a matching success interface set;
and a marking unit 370, configured to mark, when the interfaces in the successfully matched interface set are all recorded in the corresponding automation cases, the interfaces in the successfully matched interface set as implemented automation interfaces.
As an alternative embodiment, the second matching unit 330 includes:
the determining subunit 331 is configured to determine, according to an interface of the system simulation platform, a subsystem interface corresponding to the system simulation platform;
and the matching subunit 332 is configured to match the subsystem Git warehouse interface with the subsystem interface corresponding to the system simulation platform, so as to obtain a second matching result.
As an optional implementation manner, the interface checking apparatus further includes:
a second determining unit 380, configured to determine, after matching the gateway warehouse interface of the subsystem with an interface of the system simulation platform to obtain a second matching result, a first unmatched successful interface set according to the second matching result; wherein the subsystem Git warehouse interface comprises a first unmatched successful interface set;
a sending unit 390, configured to send interface maintenance prompt information including a first unmatched successful interface set; and the maintenance interface prompt information is used for prompting the system simulation platform to maintain the interface data matched with the first unmatched successful interface set.
As an optional implementation manner, the interface checking apparatus further includes:
a third determining unit 400, configured to determine, after matching the interface case with the Git warehouse interface to obtain a third matching result, a second unmatched successful interface set in the Git warehouse interface according to the third matching result;
a sending unit 390, further configured to send case entry prompt information including the second unmatched successful interface set; and the case entry prompt information is used for prompting the entry of the automated case corresponding to the second unmatched successful interface set in the automated cloud test platform.
As an optional implementation manner, the interface checking apparatus further includes:
a sorting unit 410, configured to sort the interface check results according to different subsystems after summarizing the first matching result, the second matching result, and the third matching result to obtain an interface check result, so as to obtain sorted data;
and the output unit 420 is used for outputting the sorted and sorted data.
In this embodiment, for the explanation of the interface checking device, reference may be made to the description in embodiment 1 or embodiment 2, and details are not repeated in this embodiment.
It can be seen that, the interface checking device described in this embodiment can enable developers and testers to more clearly know the degree of automation completion of the interface, so that the automation completion of the newly added interface of the version does not need to be counted manually, and an effect of automatically reminding relevant personnel to enter an interface case is achieved. Meanwhile, the efficiency can be improved, the labor is saved, the effect of reminding the development and maintenance of the interface document is achieved, and the omission of the interface is effectively avoided.
An embodiment of the present application provides an electronic device, including a memory and a processor, where the memory is used to store a computer program, and the processor runs the computer program to make the electronic device execute the interface checking method in embodiment 1 or embodiment 2 of the present application.
An embodiment of the present application provides a computer-readable storage medium, which stores computer program instructions, and when the computer program instructions are read and executed by a processor, the computer program instructions execute the interface checking method in embodiment 1 or embodiment 2 of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved
Depending on the function involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
0 if implemented in the form of software functional modules and sold or made as a stand-alone product
And may be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application, or portions thereof, that essentially contribute to the prior art, may be embodied in the form of a software product stored on a storage medium
In other words, instructions are included to cause a computer device (which may be a personal computer, a server 5, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application.
And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk, and various media capable of storing program codes.
The above description is only an example of the present application and is not intended to limit the scope of the present application, and 0 may be modified and varied by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application. It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
The above 5 is only the specific embodiment of the present application, but the protection scope of the present application is not limited thereto
Therefore, any person skilled in the art can easily think of the changes or substitutions in the technical scope of the present disclosure, and shall cover the protection scope of the present disclosure. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a … …" does not exclude the presence of another identical element in a process, method, article, or apparatus that comprises the element.
Claims (10)
1. An interface checking method, comprising:
acquiring an interface of a system simulation platform, an interface of an automatic cloud test platform, a subsystem Git warehouse interface and an interface case in the automatic cloud test platform;
matching an interface of the system simulation platform with an interface of the automatic cloud test platform to obtain a first matching result;
matching the interface of the subsystem Git warehouse with the interface of the system simulation platform to obtain a second matching result;
matching the interface case with the subsystem Git warehouse interface to obtain a third matching result;
and summarizing the first matching result, the second matching result and the third matching result to obtain an interface checking result.
2. The interface checking method according to claim 1, wherein after the matching the interface of the system simulation platform with the interface of the automated cloud test platform to obtain a first matching result, the method further comprises:
determining a successfully matched interface set according to the first matching result; wherein the interface of the system simulation platform comprises the matching success interface set;
and when the interfaces in the successfully matched interface set are all recorded into the corresponding automatic cases, marking the interfaces in the successfully matched interface set as realized automatic interfaces.
3. The interface checking method according to claim 1, wherein the matching the interface of the subsystem Git warehouse with the interface of the system simulation platform to obtain the second matching result includes:
determining a subsystem interface corresponding to the system simulation platform according to the interface of the system simulation platform;
and matching the subsystem Git warehouse interface with the subsystem interface corresponding to the system simulation platform to obtain a second matching result.
4. The interface checking method according to claim 3, wherein after the matching of the subsystem Git warehouse interface with the interface of the system simulation platform to obtain the second matching result, the method further comprises:
determining a first unmatched successful interface set according to the second matching result; wherein the subsystem Git repository interface comprises the first set of unmatched successful interfaces;
sending interface maintenance prompt information comprising the first unmatched successful interface set; and the maintenance interface prompt message is used for prompting that the interface data matched with the first unmatched successful interface set is maintained on the system simulation platform.
5. The interface verification method according to claim 1, wherein after said matching said interface case with said subsystem Git warehouse interface to obtain a third matching result, said method further comprises:
determining a second unmatched successful interface set in the subsystem Git warehouse interface according to the third matching result;
sending case entry prompt information comprising the second unmatched successful interface set; and the case entry prompt information is used for prompting the entry of the automated case corresponding to the second unmatched successful interface set in the automated cloud test platform.
6. The interface verification method according to claim 1, wherein after summarizing the first matching result, the second matching result, and the third matching result to obtain an interface verification result, the method further comprises:
sorting the interface checking results according to different subsystems to obtain sorted data;
and outputting the classified and sorted data.
7. An interface collating apparatus, characterized by comprising:
the system comprises an acquisition unit, a storage unit and a processing unit, wherein the acquisition unit is used for acquiring an interface of a system simulation platform, an interface of an automatic cloud test platform, a subsystem Git warehouse interface and an interface case in the automatic cloud test platform;
the first matching unit is used for matching an interface of the system simulation platform with an interface of the automatic cloud test platform to obtain a first matching result;
the second matching unit is used for matching the subsystem Git warehouse interface with the interface of the system simulation platform to obtain a second matching result;
the third matching unit is used for matching the interface case with the subsystem Git warehouse interface to obtain a third matching result;
and the summarizing unit is used for summarizing the first matching result, the second matching result and the third matching result to obtain an interface checking result.
8. The interface collating apparatus according to claim 7, further comprising:
the first determining unit is used for determining a successfully matched interface set according to a first matching result after the interface of the system simulation platform is matched with the interface of the automatic cloud testing platform to obtain the first matching result; wherein the interface of the system simulation platform comprises the matching success interface set;
and the marking unit is used for marking the interfaces in the successfully matched interface set as realized automatic interfaces when the interfaces in the successfully matched interface set are all recorded into corresponding automatic cases.
9. An electronic device, characterized in that the electronic device comprises a memory for storing a computer program and a processor for executing the computer program to cause the electronic device to execute the interface checking method according to any one of claims 1 to 6.
10. A readable storage medium having stored therein computer program instructions which, when read and executed by a processor, perform the interface checking method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211686986.3A CN115878487A (en) | 2022-12-27 | 2022-12-27 | Interface checking method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211686986.3A CN115878487A (en) | 2022-12-27 | 2022-12-27 | Interface checking method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115878487A true CN115878487A (en) | 2023-03-31 |
Family
ID=85754777
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211686986.3A Pending CN115878487A (en) | 2022-12-27 | 2022-12-27 | Interface checking method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115878487A (en) |
-
2022
- 2022-12-27 CN CN202211686986.3A patent/CN115878487A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112613917B (en) | Information pushing method, device, equipment and storage medium based on user portrait | |
| CN112882699B (en) | Service processing method, device, equipment and medium based on flow configuration engine | |
| CN112416778B (en) | Test case recommendation method and device and electronic equipment | |
| CN111338692A (en) | Vulnerability classification method and device based on vulnerability codes and electronic equipment | |
| CN113836128A (en) | Abnormal data identification method, system, equipment and storage medium | |
| CN110688823B (en) | XML file verification method and device | |
| CN112256517A (en) | Log analysis method and device of virtualization platform based on LSTM-DSSM | |
| CN113205130B (en) | Data auditing method and device, electronic equipment and storage medium | |
| CN117909392B (en) | Intelligent data asset inventory method and system | |
| CN113869789A (en) | Risk monitoring method and device, computer equipment and storage medium | |
| CN112835810A (en) | Interface testing method and device based on log analysis | |
| CN112486841A (en) | Method and device for checking data collected by buried point | |
| CN112860722A (en) | Data checking method and device, electronic equipment and readable storage medium | |
| CN110334333B (en) | Information modification method and related device | |
| CN115756486A (en) | Data interface analysis method and device | |
| CN115878487A (en) | Interface checking method and device | |
| CN115170073A (en) | Logistics arbitration list processing method, device, equipment and storage medium | |
| CN112364121B (en) | Automatic questionnaire PDF creation method and device, storage medium and computer equipment | |
| CN111177501B (en) | Label processing method, device and system | |
| CN113901817A (en) | Document classification method and device, computer equipment and storage medium | |
| CN112035287A (en) | Data cleaning result testing method and device, storage medium and equipment | |
| CN115795058B (en) | Threat modeling method, threat modeling system, electronic equipment and storage medium | |
| CN116541382B (en) | Data management method and system based on data security identification level | |
| CN116955283A (en) | Service information query method, device, equipment, medium and product | |
| CN115344890A (en) | Sensitive information processing method and device |
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 |