CN111679983A - JAVA interface static test method and device - Google Patents
JAVA interface static test method and device Download PDFInfo
- Publication number
- CN111679983A CN111679983A CN202010512102.7A CN202010512102A CN111679983A CN 111679983 A CN111679983 A CN 111679983A CN 202010512102 A CN202010512102 A CN 202010512102A CN 111679983 A CN111679983 A CN 111679983A
- Authority
- CN
- China
- Prior art keywords
- interface
- document
- fields
- xml mapping
- java
- 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.)
- Granted
Links
- 230000003068 static effect Effects 0.000 title claims abstract description 52
- 238000010998 test method Methods 0.000 title claims abstract description 15
- 238000013507 mapping Methods 0.000 claims abstract description 82
- 238000012360 testing method Methods 0.000 claims abstract description 68
- 238000000034 method Methods 0.000 claims abstract description 27
- 238000004590 computer program Methods 0.000 claims description 16
- 238000011161 development Methods 0.000 abstract description 17
- 230000008439 repair process Effects 0.000 abstract description 9
- 230000007547 defect Effects 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 17
- 230000006870 function Effects 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 5
- 230000010354 integration Effects 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 238000012216 screening Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000001737 promoting effect Effects 0.000 description 1
- 238000000275 quality assurance Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 230000000007 visual effect Effects 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
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 provides a static test method and a static test device for a JAVA interface, wherein the method comprises the following steps: acquiring an interface document before JAVA program development and operation and an xml mapping document of a JAVA program interface; analyzing the interface document to obtain a plurality of interface fields of each interface corresponding to the interface document; analyzing the xml mapping document to obtain a plurality of interface fields of each interface corresponding to the xml mapping document; and comparing the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a JAVA interface static test result. The method realizes the test of the program interface before the development and the compiling operation of the program, and reduces the repair cost caused by the defects appearing in the later stage of the development of the program.
Description
Technical Field
The invention relates to the technical field of software interface testing, in particular to a static testing method and device for a JAVA interface.
Background
Under a DevOps integrated system, software is developed, tested and released more quickly, frequently and reliably. As shown in fig. 1, the whole system is roughly divided into an automation test, an automation construction, an automation code review, an automation unit test, an automation deployment, an automation interface, a function test, a visual presentation, an end-to-end test, an automation deployment, and the like, and these automation tools capable of automatically operating bring great convenience and stability to the whole development process.
For the test and test of the JAVA interface, an interface test or a contract test is currently adopted, but both of them must wait until the middle stage or the later stage of program development, and even when an end-to-end test is performed, the problem can be found, and the repair cost is very high when the interface mismatch problem occurs in the later stage of program development, and a lot of energy is consumed in the aspects of time and labor.
Disclosure of Invention
The embodiment of the invention provides a static test method of a JAVA interface, which is used for testing the program interface before program development and compiling operation and reducing the repair cost caused by defects in the later stage of program development, and comprises the following steps:
acquiring an interface document before JAVA program development and operation and an xml mapping document of a JAVA program interface;
analyzing the interface document to obtain a plurality of interface fields of each interface corresponding to the interface document;
analyzing the xml mapping document to obtain a plurality of interface fields of each interface corresponding to the xml mapping document;
comparing the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a JAVA interface static test result.
The embodiment of the invention also provides a JAVA interface static test device, which is used for testing the program interface before program development and compiling operation and reducing the repair cost caused by defects in the later stage of program development, and comprises the following steps:
the data acquisition module is used for acquiring an interface document before JAVA program development and operation and an xml mapping document of a JAVA program interface;
the first analysis module is used for analyzing the interface document to obtain a plurality of interface fields of each interface corresponding to the interface document;
the second analysis module is used for analyzing the xml mapping document to obtain a plurality of interface fields of each interface corresponding to the xml mapping document;
and the comparison test module is used for comparing the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a JAVA interface static test result.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the JAVA interface static test method when executing the computer program.
An embodiment of the present invention also provides a computer-readable storage medium, which stores a computer program for executing the above JAVA interface static test method.
In the embodiment of the invention, an interface document before JAVA program development and operation and an xml mapping document of a JAVA program interface are obtained; analyzing the interface document to obtain a plurality of interface fields of each interface corresponding to the interface document; analyzing the xml mapping document to obtain a plurality of interface fields of each interface corresponding to the xml mapping document; and comparing the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a JAVA interface static test result. The method and the device realize the testing of the program interface before the development and the compiling operation of the program, and reduce the repair cost caused by the defects in the later stage of the development of the program.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of a static test method for a JAVA interface according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating a method for performing step 104 in an embodiment of the present invention.
FIG. 3 is a schematic diagram of an automated interface static test equipment platform in accordance with an embodiment of the present invention.
FIG. 4 is a logic diagram illustrating the operation of an automatic interface static test equipment platform in accordance with an embodiment of the present invention.
FIG. 5 is a block diagram illustrating the operation of an automatic interface static test equipment platform in an exemplary implementation of the present invention.
FIG. 6 is a diagram illustrating a document upload operation interface of an Automation interface static test device platform in an implementation of the present invention.
FIG. 7 is a diagram illustrating an interface field matching operation interface of an automatic interface static test equipment platform in an exemplary implementation of the present invention.
FIG. 8 is an exemplary diagram of a matching result display interface of an automatic interface static test equipment platform in accordance with an embodiment of the present invention.
FIG. 9 is a diagram illustrating a static test apparatus for a JAVA interface according to an embodiment of the present invention.
Detailed Description
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 only a part of the embodiments of the present invention, and not all of the embodiments. 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.
In this context, it is to be understood that the terms referred to:
interface documentation: and the interface definition form is unified, so that each related product can be downloaded from the interface document management platform in a word form by taking the document as the standard of the interface definition.
XML interface definition: the attributes of the interface are defined in the form of xml so as to be mapped into objects which can be used by a java program.
DevOps development, operation and maintenance integration: the system is a general term of a group of processes, methods and systems, is used for promoting communication cooperation and integration among development departments, technical operation departments and quality assurance departments, and is matched with a plurality of automation components or tools to ensure the efficiency and quality of integration.
And (3) static testing: the method is a method for checking the correctness of the program by analyzing or checking the grammar, the structure, the process, the interface and the like of the source program without running the tested program.
The embodiment of the invention provides a static test method for a JAVA interface, which is used for testing the program interface before program development and compiling operation and reducing the repair cost caused by defects in the later stage of program development, and as shown in figure 1, the method comprises the following steps:
step 101: acquiring an interface document before JAVA program development and operation and an xml mapping document of a JAVA program interface;
step 102: analyzing the interface document to obtain a plurality of interface fields of each interface corresponding to the interface document;
step 103: analyzing the xml mapping document to obtain a plurality of interface fields of each interface corresponding to the xml mapping document;
step 104: and comparing the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a JAVA interface static test result.
As can be known from the flow shown in fig. 1, in the embodiment of the present invention, an interface document before JAVA program development and operation and an xml mapping document of a JAVA program interface are obtained; analyzing the interface document to obtain a plurality of interface fields of each interface corresponding to the interface document; analyzing the xml mapping document to obtain a plurality of interface fields of each interface corresponding to the xml mapping document; and comparing the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a JAVA interface static test result. The method and the device realize the testing of the program interface before the development and the compiling operation of the program, and reduce the repair cost caused by the defects in the later stage of the development of the program.
When the method is specifically implemented, firstly, an interface document before JAVA program development and operation and an xml mapping document of a JAVA program interface are obtained. The interface document before development and operation of the JAVA program is exported from the interface document management platform in a word form, and can be exported according to a single interface, or can be exported according to the whole batch of interface documents which need to be modified or the whole batch of interface documents. The XML mapping document of the JAVA programming interface is an interface description document obtained according to XML interface definition, and can comprise an XML mapping document of a single interface or a batch of XML mapping documents of a plurality of interfaces.
After the interface document is obtained, the interface document is analyzed to obtain a plurality of interface fields of each interface corresponding to the interface document. In specific implementation, the table structure of the word-form interface document is scanned, and elements are extracted according to the interface keywords to obtain a plurality of interface fields of each interface corresponding to the interface document.
And after acquiring the xml mapping document, analyzing the xml mapping document to obtain a plurality of interface fields of each interface corresponding to the xml mapping document. In specific implementation, if a nested tag exists in an xml mapping document corresponding to an interface, when the xml mapping document corresponding to the interface is analyzed, a loop message in the xml mapping document corresponding to the interface is circularly expanded, and a plurality of interface fields of the interface corresponding to the xml mapping document are obtained.
After the analysis is completed, comparing the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a JAVA interface static test result. The specific process is shown in fig. 2, and includes:
step 201: comparing a plurality of interface fields of each interface corresponding to the interface document with a plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a comparison result of each interface field;
step 202: and determining interfaces with non-uniform definitions according to the comparison result of each interface field to obtain the static test result of the JAVA interface.
In step 201, when the lengths of the two interface fields to be compared are not the same, the next interface field is continuously read for the shorter interface field until the length of the next interface field is the same as the length of the longer interface field. Because several interface fields may be synthesized into one field display in the interface document, but the several fields are still separately defined in the xml mapping document, so that when performing comparison, the several fields cannot be in one-to-one correspondence, and therefore, the next interface field needs to be read continuously until the field lengths of the two compared parties are the same.
A specific example is given below to illustrate how embodiments of the present invention perform static testing of JAVA interfaces. This example is an automation interface static test apparatus platform developed by applying the JAVA interface static test method in the embodiment of the present invention, as shown in fig. 3.
The product specifically comprises: the system comprises an interface document uploading module, an xml mapping document uploading module and a comparison display result module.
The interface document uploading module is used for uploading a word format interface document which is downloaded from the interface document platform and is in the JAVA program before development and operation to the device platform, and meanwhile, when the word format interface document is uploaded, the interface document is analyzed and stored in a database of the device platform according to the table form of each interface. The interface document is parsed by a python processing word third party library win32 and a docx library of python.
And the xml mapping document uploading module is used for uploading the interface document definition in the xml format before the development and operation of the JAVA program, namely the xml mapping document to the device platform, directly storing the xml mapping document of each interface in the platform server, and analyzing the xml mapping document by using an xml.
And the comparison display result module displays each interface information of the interface documents in the platform after the two documents are uploaded, compares the analysis results of the two documents and finally obtains the comparison result state. And (3) screening all interfaces in a batch directly with or without screening each interface, and clicking a matching button in the platform to automatically compare the interfaces in the background. And finally judging whether the interface is defined uniformly by the platform through comparison of the two documents.
The process of analyzing the interface document and the xml mapping document and comparing the interface fields is shown in fig. 4, the interface document is analyzed by using a python-docx library, the xml mapping document is analyzed by using a python xml.
The specific operation steps are shown in fig. 5, and include:
the interface document in doc format is exported from the interface document platform, and the export can be carried out according to the transaction, or can be carried out by all interfaces in one batch.
And uploading the exported interface document in the Word format to the platform, wherein the uploading interface is as shown in FIG. 6, and selecting the interface document from the uploading document options.
The interface definition document of the XML code is uploaded to the platform, when the XML mapping document is uploaded, the XML mapping document can be uploaded in batches through a plurality of interfaces or singly through one interface, the uploading interface is shown in fig. 6, and the XML code is selected from the uploading document options.
After the two documents are uploaded, the interfaces can be matched by clicking 'matching' on the page shown in fig. 7, and after a matching result is obtained, if the rechecking is needed, a certain interface can be selected to be subjected to rechecking comparison individually, or all the interfaces in a batch can be subjected to rechecking comparison together.
And after the platform completes comparison in the background, displaying the result state in a page, and updating the state of each interface. For example, different alignments can be made with different color standards in the interface: red: representing where the interface document has a mismatch with the interface in the xml mapping document; blue color: the interface document and the interface in the xml document have unmatched places, but are controllable in a rule range, and interface errors cannot be influenced; yellow: representing interfaces that have not been aligned; green: indicating an interface for which the interface fields all match. The comparison result can also be presented in a list form, as shown in fig. 8, the field number 8 is a problematic field, the format of which is character format in the interface document, but is number mode in the xml document, so the comparison result in the box is that "the field is an error field and does not match with the interface document", and is presented in the 8 th line in the list to remind the user to view.
The automatic interface static test device platform is applied to carry out the JAVA interface static test, so that the problem of interface inconsistency caused by 'low-level errors' of simple attribute format inconsistency can be avoided, and the loss caused by the fact that the interfaces can be discovered in the later stage of test, function test or end-to-end even production is avoided. Because, the repair cost is high when the interface mismatching problem occurs at the later stage, because the team is not involved, the team also needs to communicate with other related teams of products continuously, and a great deal of energy is consumed in the aspects of time and labor.
The automatic interface static test device platform is applied to carry out JAVA interface static test, and can also carry out test and inspection of large batches of JAVA interfaces, so that development and test personnel can be not needed to carry out manual comparison, the working efficiency is improved, and the risk of accuracy reduction caused by manual comparison is also reduced.
The implementation of the above specific application is only an example, and the rest of the embodiments are not described in detail.
Based on the same inventive concept, embodiments of the present invention further provide a JAVA interface static test apparatus, where the principle of the problem solved by the JAVA interface static test apparatus is similar to that of the JAVA interface static test method, so that the implementation of the JAVA interface static test apparatus may refer to the implementation of the JAVA interface static test method, and repeated details are not described, and the specific structure is as shown in fig. 9:
the data acquisition module 901 is used for acquiring an interface document before the development and operation of the JAVA program and an xml mapping document of a JAVA program interface;
a first parsing module 902, configured to parse the interface document to obtain a plurality of interface fields corresponding to the interface document for each interface;
a second parsing module 903, configured to parse the xml mapping document to obtain a plurality of interface fields, where each interface corresponds to the xml mapping document;
and the comparison test module 904 is configured to compare the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one, so as to obtain a JAVA interface static test result.
In a specific embodiment, the first parsing module 902 is specifically configured to: and scanning the table structure of the interface document, and extracting elements according to the interface keywords to obtain a plurality of interface fields of each interface corresponding to the interface document.
In specific implementation, the second parsing module 903 is specifically configured to: if the xml mapping document corresponding to an interface has a nested tag, circularly expanding a circular message in the xml mapping document corresponding to the interface when the xml mapping document corresponding to the interface is analyzed to obtain a plurality of interface fields of the xml mapping document corresponding to the interface
In an embodiment, the comparison test module 904 is specifically configured to:
comparing a plurality of interface fields of each interface corresponding to the interface document with a plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a comparison result of each interface field;
and determining interfaces with non-uniform definitions according to the comparison result of each interface field to obtain the static test result of the JAVA interface.
In specific implementation, the comparison testing module 904 is specifically configured to: when the two compared interface fields are different in length, the next interface field is continuously read for the shorter interface field until the length of the next interface field is the same as that of the longer interface field, and then the comparison is carried out.
The embodiment of the invention also provides computer equipment which comprises a memory, a processor and a computer program which is stored on the memory and can run on the processor, wherein the processor realizes the JAVA interface static test method when executing the computer program.
The embodiment of the invention also provides a computer readable storage medium, which stores a computer program for executing the JAVA interface static test method.
In summary, the JAVA interface static test method and apparatus provided in the embodiment of the present invention have the following advantages:
the method comprises the steps of obtaining an interface document before JAVA program development and operation and an xml mapping document of a JAVA program interface; analyzing the interface document to obtain a plurality of interface fields of each interface corresponding to the interface document; analyzing the xml mapping document to obtain a plurality of interface fields of each interface corresponding to the xml mapping document; and comparing the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a JAVA interface static test result. The method and the device realize the testing of the program interface before the development and the compiling operation of the program, and reduce the repair cost caused by the defects in the later stage of the development of the program. The JAVA interface test system has the advantages that test and check of large batches of JAVA interfaces can be performed, so that manual comparison of development and testing personnel can be omitted, the working efficiency is improved, and the risk of accuracy reduction caused by manual comparison is reduced.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus 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 data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing 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 data processing 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 data processing 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.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes may be made to the embodiment of the present invention by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (12)
1. A JAVA interface static test method is characterized by comprising the following steps:
acquiring an interface document before JAVA program development and operation and an xml mapping document of a JAVA program interface;
analyzing the interface document to obtain a plurality of interface fields of each interface corresponding to the interface document;
analyzing the xml mapping document to obtain a plurality of interface fields of each interface corresponding to the xml mapping document;
comparing the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a JAVA interface static test result.
2. The method of claim 1, wherein parsing the interface document to obtain a plurality of interface fields for each interface corresponding to the interface document comprises:
and scanning the table structure of the interface document, and extracting elements according to the interface keywords to obtain a plurality of interface fields of each interface corresponding to the interface document.
3. The method of claim 1, wherein parsing the xml mapping document to obtain a plurality of interface fields for each interface corresponding to the xml mapping document comprises:
if the nested label exists in the xml mapping document corresponding to an interface, circularly expanding the circular message in the xml mapping document corresponding to the interface when the xml mapping document corresponding to the interface is analyzed, and obtaining a plurality of interface fields of the interface corresponding to the xml mapping document.
4. The method of claim 1, wherein comparing each interface with a plurality of interface fields of the interface document one by one to obtain a JAVA interface static test result, the method comprising:
comparing a plurality of interface fields of each interface corresponding to the interface document with a plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a comparison result of each interface field;
and determining interfaces with non-uniform definitions according to the comparison result of each interface field to obtain the static test result of the JAVA interface.
5. The method of claim 1 or 4, wherein comparing each interface to a plurality of interface fields of the interface document one by one with each interface to a plurality of interface fields of the xml mapping document comprises:
when the two compared interface fields are different in length, the next interface field is continuously read for the shorter interface field until the length of the next interface field is the same as that of the longer interface field, and then the comparison is carried out.
6. A JAVA interface static test apparatus, comprising:
the data acquisition module is used for acquiring an interface document before JAVA program development and operation and an xml mapping document of a JAVA program interface;
the first analysis module is used for analyzing the interface document to obtain a plurality of interface fields of each interface corresponding to the interface document;
the second analysis module is used for analyzing the xml mapping document to obtain a plurality of interface fields of each interface corresponding to the xml mapping document;
and the comparison test module is used for comparing the plurality of interface fields of each interface corresponding to the interface document with the plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a JAVA interface static test result.
7. The apparatus of claim 6, wherein the first parsing module is specifically configured to:
and scanning the table structure of the interface document, and extracting elements according to the interface keywords to obtain a plurality of interface fields of each interface corresponding to the interface document.
8. The apparatus of claim 6, wherein the second parsing module is specifically configured to:
if the nested label exists in the xml mapping document corresponding to an interface, circularly expanding the circular message in the xml mapping document corresponding to the interface when the xml mapping document corresponding to the interface is analyzed, and obtaining a plurality of interface fields of the interface corresponding to the xml mapping document.
9. The apparatus of claim 6, wherein the alignment test module is specifically configured to:
comparing a plurality of interface fields of each interface corresponding to the interface document with a plurality of interface fields of each interface corresponding to the xml mapping document one by one to obtain a comparison result of each interface field;
and determining interfaces with non-uniform definitions according to the comparison result of each interface field to obtain the static test result of the JAVA interface.
10. The apparatus of claim 6 or 9, wherein the alignment test module is specifically configured to:
when the two compared interface fields are different in length, the next interface field is continuously read for the shorter interface field until the length of the next interface field is the same as that of the longer interface field, and then the comparison is carried out.
11. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 5 when executing the computer program.
12. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program for executing the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010512102.7A CN111679983B (en) | 2020-06-08 | 2020-06-08 | JAVA interface static test method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010512102.7A CN111679983B (en) | 2020-06-08 | 2020-06-08 | JAVA interface static test method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111679983A true CN111679983A (en) | 2020-09-18 |
| CN111679983B CN111679983B (en) | 2023-10-24 |
Family
ID=72435153
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010512102.7A Active CN111679983B (en) | 2020-06-08 | 2020-06-08 | JAVA interface static test method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111679983B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114760236A (en) * | 2022-04-08 | 2022-07-15 | 中国银行股份有限公司 | Interface checking method, device, storage medium and equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170091210A1 (en) * | 2015-09-30 | 2017-03-30 | International Business Machines Corporation | Mapping non-generic markup language elements to generic object-oriented programming language objects |
| CN106991050A (en) * | 2017-04-05 | 2017-07-28 | 西安邮电大学 | A kind of static test null pointer dereference defect false positive recognition methods |
| CN107992306A (en) * | 2017-12-03 | 2018-05-04 | 中国直升机设计研究所 | A kind of avionics software interface realizes uniformity automatic check method |
| CN110287069A (en) * | 2019-05-21 | 2019-09-27 | 平安银行股份有限公司 | ESB automatic interface testing method, server and computer readable storage medium |
-
2020
- 2020-06-08 CN CN202010512102.7A patent/CN111679983B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170091210A1 (en) * | 2015-09-30 | 2017-03-30 | International Business Machines Corporation | Mapping non-generic markup language elements to generic object-oriented programming language objects |
| CN106991050A (en) * | 2017-04-05 | 2017-07-28 | 西安邮电大学 | A kind of static test null pointer dereference defect false positive recognition methods |
| CN107992306A (en) * | 2017-12-03 | 2018-05-04 | 中国直升机设计研究所 | A kind of avionics software interface realizes uniformity automatic check method |
| CN110287069A (en) * | 2019-05-21 | 2019-09-27 | 平安银行股份有限公司 | ESB automatic interface testing method, server and computer readable storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114760236A (en) * | 2022-04-08 | 2022-07-15 | 中国银行股份有限公司 | Interface checking method, device, storage medium and equipment |
| CN114760236B (en) * | 2022-04-08 | 2023-11-14 | 中国银行股份有限公司 | Interface checking method, device, storage medium and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111679983B (en) | 2023-10-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111813661B (en) | Global service data drive automatic test method, device, equipment and medium | |
| US20120150820A1 (en) | System and method for testing data at a data warehouse | |
| CN109977670B (en) | Android application security monitoring method based on plug-in loading and storage medium | |
| CN112486557A (en) | Development-based complete life cycle management platform and method | |
| CN106708718A (en) | Service framework interface testing method and device | |
| CN111198814A (en) | Continuously integrated acceptance system for continuous delivery | |
| EP2557499A1 (en) | A system and method for automatic impact variable analysis and field expansion in mainframe systems | |
| CN110704475A (en) | Method and system for comparing ETL loading table structures | |
| CN103955429B (en) | Determine the method and device of regression test scope | |
| US7283986B2 (en) | End-to-end business integration testing tool | |
| CN112131116A (en) | Automatic regression testing method for embedded software | |
| CN111782737A (en) | Information processing method, device, equipment and storage medium | |
| CN111598535B (en) | Basic material importing method, system and computer equipment | |
| CN111679983B (en) | JAVA interface static test method and device | |
| CN100428243C (en) | Method and system for realizing action on model | |
| CN110851361A (en) | Interface testing method and device, electronic equipment and readable storage medium | |
| CN113052501A (en) | Automatic safe operation and maintenance method and terminal based on assets | |
| JP4835859B2 (en) | State transition diagram creation device and state transition diagram creation method | |
| US11789712B2 (en) | Data configuration deployment framework | |
| CN113608727B (en) | Code processing method, device and system for visual programming | |
| US12008362B2 (en) | Software development environment | |
| CN111400190A (en) | Automatic test flow generation method and device and computer readable storage medium | |
| US20230266965A1 (en) | Software development environment | |
| CN113064811B (en) | Automatic testing method and device based on workflow and electronic equipment | |
| CN112748950B (en) | Software code examination 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |