CN112367220A - Interface testing method and device, storage medium and electronic equipment - Google Patents

Interface testing method and device, storage medium and electronic equipment Download PDF

Info

Publication number
CN112367220A
CN112367220A CN202011162873.4A CN202011162873A CN112367220A CN 112367220 A CN112367220 A CN 112367220A CN 202011162873 A CN202011162873 A CN 202011162873A CN 112367220 A CN112367220 A CN 112367220A
Authority
CN
China
Prior art keywords
test
test case
case
result
interface
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202011162873.4A
Other languages
Chinese (zh)
Other versions
CN112367220B (en
Inventor
廖根中
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Ubtech Robotics Corp
Original Assignee
Ubtech Robotics Corp
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Ubtech Robotics Corp filed Critical Ubtech Robotics Corp
Priority to CN202011162873.4A priority Critical patent/CN112367220B/en
Publication of CN112367220A publication Critical patent/CN112367220A/en
Application granted granted Critical
Publication of CN112367220B publication Critical patent/CN112367220B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/50Testing arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/02Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

The embodiment of the application discloses an interface testing method and device, a storage medium and electronic equipment. The method comprises the following steps: responding to the import operation of the test case, and importing the test case; the test case is filled and generated based on a test case template; responding to the test operation, and performing http interface test by adopting the test case to obtain a test result of the test case; and writing the test result back to the test case, and displaying the test result of the test case in the test process. According to the technical scheme, the test case can be filled based on the test case template, the filling operation is simple, the test case is more standardized, the test result can be written back to the test case, and the integrated management of the test parameters and the test result is realized.

Description

Interface testing method and device, storage medium and electronic equipment
Technical Field
The embodiment of the application relates to the technical field of interface testing, in particular to an interface testing method and device, a storage medium and electronic equipment.
Background
The Http (HyperText Transfer Protocol) Protocol is based on a TCP (Transmission Control Protocol) Protocol, and when a browser needs to obtain web page data from a server, an Http request is issued. Http establishes a connection channel to the server through TCP, and Http immediately disconnects TCP after the data required by the request is completed, which is very short. An Http connection is a short connection, which is a stateless connection.
Currently, in the field of http interface testing, there are two general test schemes. Firstly, testing is carried out by means of a third-party testing tool, and secondly, testing scripts are written based on third-party library requests, urllib and the like to carry out testing.
Tests were conducted with the aid of third party testing tools, the main interface testing tools being postman, soap ui and jmeter. The postman is only used for interface debugging and does not support the establishment of a test case set for test development; the soap UI and the meter support the establishment of a test case set for developing interface tests, and test parameters and test results cannot be integrated together to be output as a test report. Test scripts are compiled based on third-party libraries, requests, urllib and the like to carry out tests, the compiling requirements of the test scripts are high, the compiling is difficult, and the test logic is lack of standardization.
Disclosure of Invention
The embodiment of the application provides an interface testing method, an interface testing device, a storage medium and electronic equipment, which can fill in a test case based on a test case template, are simple to fill in and more standardized, and can write back a test result to the test case, so that integrated management of test parameters and the test result is realized.
In a first aspect, an embodiment of the present application provides an interface testing method, where the method includes:
responding to the import operation of the test case, and importing the test case; the test case is filled and generated based on a test case template;
responding to the test operation, and performing http interface test by adopting the test case to obtain a test result of the test case;
and writing the test result back to the test case, and displaying the test result of the test case in the test process.
In a second aspect, an embodiment of the present application provides an interface testing apparatus, including:
the test case importing module is used for responding to the importing operation of the test case and importing the test case; the test case is filled and generated based on a test case template;
the test result obtaining module is used for responding to the test operation and adopting the test case to carry out http interface test so as to obtain the test result of the test case;
and the test result write-back module is used for writing back the test result to the test case and displaying the test result of the test case in the test process.
In a third aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements an interface testing method according to an embodiment of the present application.
In a fourth aspect, an embodiment of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored on the memory and executable by the processor, where the processor executes the computer program to implement the interface testing method according to the embodiment of the present application.
According to the technical scheme provided by the embodiment of the application, the test case is imported in response to the import operation of the test case, wherein the test case is generated based on the filling of the test case template, the http interface test is carried out by adopting the test case in response to the test operation after the test case is determined, the test result of the test case is obtained, then the test result is written back to the test case, and the test result of the test case in the test process is displayed. By executing the technical scheme, the test case can be filled based on the test case template, the filling operation is simple, the test case is more standardized, the test result can be written back to the test case, and the integrated management of the test parameters and the test result is realized.
Drawings
Fig. 1 is a flowchart of an interface testing method according to an embodiment of the present application;
fig. 2 is an interface test operation interface of a client according to an embodiment of the present application;
FIG. 3 is a test case result display table provided in an embodiment of the present application;
fig. 4 is a schematic structural diagram of an interface testing apparatus according to a second embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present application.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some of the structures related to the present application are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the steps as a sequential process, many of the steps can be performed in parallel, concurrently or simultaneously. In addition, the order of the steps may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
Example one
Fig. 1 is a flowchart of an interface testing method provided in an embodiment of the present application, where the present embodiment is applicable to a case of performing an http interface test, and the method may be executed by an interface testing apparatus provided in the embodiment of the present application, where the apparatus may be implemented in a software and/or hardware manner, and may be integrated in a device such as an intelligent terminal for interface testing.
As shown in fig. 1, the interface testing method includes:
s110, responding to the import operation of the test case, and importing the test case; the test case is filled and generated based on the test case template.
In this embodiment, the test case template may be a tabular template. Preferably, an xlsx format form template can be adopted, and the xlsx format form template can be used for carrying out batch formatting editing on the test cases based on the rich form processing function of the electronic form software, so that the case compiling efficiency is greatly improved, and the representation forms of the test cases are enriched.
The user can fill in the test case according to the rule of the test case template. For example, the corresponding content may be filled in according to the requirements of different fields in the test case template, or the content in the corresponding format may be filled in according to the requirements of the test case template.
In this embodiment, in response to the import operation of the test case, the test case may be imported to the associated client. The associated client may be VHttpAutoTester client software for testing of test cases. The test case can be imported through the import operation of the click client software.
In this technical solution, optionally, the process of generating the test case includes:
displaying a template form file for filling in the content of the test case;
and generating the test case according to the content of the test case and the preset incidence relation in the template form file.
In this embodiment, the preset association relationship may be a rule for filling in the content of the test case, that is, the tester may fill in the content of the test case according to the preset association relationship in the template.
Through the test case template based on the electronic form, a user is liberated from the complicated test script compiling work, a tabular editing mode is adopted, the test case compiling efficiency is greatly improved by means of the strong form processing capacity and rich data expressive force of electronic form software, the test case management is more convenient and friendly, and the error probability is greatly reduced.
And S120, responding to the test operation, and performing http interface test by using the test case to obtain a test result of the test case.
In this embodiment, the test operation may be a button click operation or a parameter input operation. Preferably, the test operation may be a button click operation, and the test case may be tested by clicking a test start button on the client interface.
The interface test is a test for testing the interface between the system components. The interface test is mainly used for detecting interaction points between external systems and between internal subsystems. The key point of the test is to check the exchange of data, transfer and control management processes, mutual logic dependency relationship between systems and the like. In this embodiment, the http interface is mainly tested by using a test case.
Fig. 2 is an interface test operation interface of a client according to an embodiment of the present application, and as shown in fig. 2, the left side of the interface test operation interface includes a test case, a test parameter, a log setting module, a test control module, and a test monitoring module. The test case comprises a selection box for selecting a test case file and a selection box for detecting the validity of the test case file. The test case file selection box can be used for selecting a test case, and the test case file validity selection box can be used for selecting the validity of the test case. The log setting comprises a log level, and can be used for testing the detail degree of the display of the log monitoring content. For example, the test log monitoring content can be controlled by selecting the log level to display only the test result, or the test log monitoring content can be controlled by selecting the log level to display the detailed test process. And the right side of the interface test operation interface comprises a test log monitoring module which is used for monitoring the test process of the test case.
In the present technical solution, optionally, in response to the test operation, performing an http interface test using the test case to obtain a test result of the test case includes:
responding to the test operation, and carrying out file validity check on the test case;
if the file legality is met, performing http interface test by using the test case to obtain a test result of the test case;
if the file legality is not met, the test is finished, and the popup prompts abnormal information of the test case.
In this embodiment, the file validity check may be to check the integrity or syntax correctness of the test case. The validity of the file is checked, so that the influence on the test result due to basic errors can be avoided.
In this embodiment, when all test cases conform to the file validity, the test cases are subjected to interface testing. When the file legality is not met, the basic error occurs in the test case, the test is directly finished, and the popup window prompts abnormal information of the test case.
By checking the validity of the file, the influence on the test result caused by basic errors can be avoided, and the test efficiency is improved.
In this technical solution, optionally, the http interface test performed by using the test case includes:
performing parameter pre-analysis on the test case to determine whether a target parameter variable name exists;
if the http request parameter exists, analyzing a target parameter of the test case to obtain an http request parameter;
and initiating an http request according to the http request parameter, and obtaining a response result of the http request.
In this embodiment, after the validity check of the test case passes, one case is selected from the test cases for pre-analysis, and the pre-analysis mainly determines whether the variable name of the target parameter exists by replacing the variable in the test parameter with the known variable name.
In this embodiment, when the target parameter variable name exists, the pre-analyzed test parameters are further analyzed, and http request parameters are extracted. The http request parameters comprise method, url, query parameters, headers and body. And when the abnormity occurs in the analysis process, ending the test. For example, the exceptions has a headers parameter that is a non-Key-Value form json.
The test case can be tested by pre-analyzing, analyzing and initiating the request, and the test response result is obtained, so that the automation of the test case is realized, and the test efficiency is improved.
In this technical solution, optionally, obtaining the test result of the test case includes:
adopting a preset data extraction rule to extract data of a response result of the http request to obtain a test result;
and verifying the test result by adopting a preset verification rule.
In this embodiment, the data extraction rule may be a rule that shows the test result according to a certain rule. For example, the test result is 11000101, and according to the data extraction rule, the test result can be shown in the form of 11000101.
In this embodiment, the test result is verified by using a preset verification rule, which may be verifying the response body (json type), the response body (text related type), the response header, and the response status _ code.
The test result is displayed according to the data extraction rule, the consistency of the test result and the test case can be kept, the test result is verified, and the accuracy of the test result can be improved.
In this technical solution, optionally, the file validity includes: at least one of header integrity, test parameter type to model conformance, and json syntax compliance for json-type test parameters.
In this embodiment, the table structure is composed of field names, data types and lengths, and various integrity constraints that make up the table.
In this embodiment, the user may fill in the test content according to the requirement of the test template, and the test parameter type needs to be consistent with the model setting in the template.
Wherein the json syntax includes data in name/value pairs, data separated by commas, curly bracket containing objects, square bracket containing tuples. For example, the use case { "name": Bill Gates "} conforms to the json grammar form.
By checking the validity of the file, the influence on the test result caused by basic errors can be avoided, and the test efficiency is improved.
S130, writing the test result back to the test case, and displaying the test result of the test case in the test process.
In this embodiment, the obtained test result is written back to the test case, that is, the test result is added to the table of the test case, and the test result of the test process is displayed.
Fig. 3 is a test case result display table provided in an embodiment of the present application. As shown in FIG. 3, test results are added to the test case table.
In the present technical solution, optionally, the test case includes at least one test field;
correspondingly, the writing back the test result to the test case includes:
determining a target test field associated with the test result;
if the test result is successful, recording test success information in the target test field;
and if the test result is test failure, determining the reason of the test failure, and recording the test failure and the reason of the test failure in the target test field.
In this embodiment, the test result may be written back to the test case, that is, a target test field associated with the test result is added to the test case. For example, test _ result and result _ detail fields may be added to the test case. test _ result represents the test result, and there are three common results including PASS, FAIL, or ERROR, i.e., the test result is a test PASS, a test exception, or a test FAIL. The result _ detail field indicates the reason for the test exception or test failure.
The test result is written back to the corresponding field of the test case file, so that the integrated management of the test parameters and the test result is realized.
Example two
Fig. 4 is a schematic structural diagram of an interface testing apparatus according to a second embodiment of the present application, and as shown in fig. 4, the interface testing apparatus includes:
a test case importing module 410, configured to import a test case in response to an importing operation of the test case; the test case is filled and generated based on a test case template;
a test result obtaining module 420, configured to perform an http interface test by using the test case in response to a test operation, and obtain a test result of the test case;
and the test result write-back module 430 is configured to write back the test result to the test case, and display the test result of the test case in the test process.
In this embodiment, optionally, the test result obtaining module 420 includes:
the file legality checking unit is used for responding to the test operation and carrying out file legality checking on the test case;
the interface test unit is used for carrying out http interface test by adopting the test case if the file legality is met, and obtaining a test result of the test case;
and the abnormal information prompting unit is used for ending the test if the file legality is not met and prompting the abnormal information of the test case by a popup window.
In this technical solution, optionally, the interface testing unit includes:
the target parameter variable name determining subunit is used for performing parameter pre-analysis on the test case and determining whether a target parameter variable name exists or not;
the request parameter obtaining unit is used for analyzing the target parameters of the test case to obtain http request parameters if the test case exists;
and the response result obtaining unit is used for initiating the http request according to the http request parameter and obtaining the response result of the http request.
In this technical solution, optionally, the interface testing unit further includes:
the test result obtaining subunit is used for extracting data of the response result of the http request by adopting a preset data extraction rule to obtain a test result;
and the test result checking subunit is used for checking the test result by adopting a preset checking rule.
In this technical solution, optionally, the test case importing module 410 includes:
the template form file display unit is used for displaying the template form file for filling the test case content;
and the test case generating unit is used for generating the test case according to the test case content and the preset incidence relation in the template form file.
In the present technical solution, optionally, the test case includes at least one test field;
accordingly, the test result write-back module 430 includes:
the test success information recording unit is used for recording test success information in the target test field if the test result is successful;
and the test failure recording unit is used for determining the reason of the test failure if the test result is the test failure, and recording the test failure and the reason of the test failure in the target test field.
In this technical solution, optionally, the file validity includes: at least one of header integrity, test parameter type to model conformance, and json syntax compliance for json-type test parameters.
The product can execute the method provided by the embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method.
EXAMPLE III
Embodiments of the present application also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a method of interface testing, the method comprising:
responding to the import operation of the test case, and importing the test case; the test case is filled and generated based on a test case template;
responding to the test operation, and performing http interface test by adopting the test case to obtain a test result of the test case;
and writing the test result back to the test case, and displaying the test result of the test case in the test process.
Storage medium-any of various types of memory devices or storage devices. The term "storage medium" is intended to include: mounting media such as CD-ROM, floppy disk, or tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Lanbas (Rambus) RAM, etc.; non-volatile memory such as flash memory, magnetic media (e.g., hard disk or optical storage); registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in the computer system in which the program is executed, or may be located in a different second computer system connected to the computer system through a network (such as the internet). The second computer system may provide the program instructions to the computer for execution. The term "storage medium" may include two or more storage media that may reside in different locations, such as in different computer systems that are connected by a network. The storage medium may store program instructions (e.g., embodied as a computer program) that are executable by one or more processors.
Of course, the storage medium provided in the embodiments of the present application contains computer-executable instructions, and the computer-executable instructions are not limited to the interface testing operations described above, and may also perform related operations in the interface testing method provided in any embodiments of the present application.
Example four
The embodiment of the application provides electronic equipment, and the interface testing device provided by the embodiment of the application can be integrated in the electronic equipment. Fig. 5 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present application. As shown in fig. 5, the present embodiment provides an electronic device 500, which includes: one or more processors 520; the storage 510 is configured to store one or more programs, and when the one or more programs are executed by the one or more processors 520, the one or more processors 520 implement the interface testing method provided in the embodiment of the present application, the method includes:
responding to the import operation of the test case, and importing the test case; the test case is filled and generated based on a test case template;
responding to the test operation, and performing http interface test by adopting the test case to obtain a test result of the test case;
and writing the test result back to the test case, and displaying the test result of the test case in the test process.
Of course, those skilled in the art can understand that the processor 520 also implements the technical solution of the interface testing method provided in any embodiment of the present application.
The electronic device 500 shown in fig. 5 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 5, the electronic device 500 includes a processor 520, a storage 510, an input 530, and an output 540; the number of the processors 520 in the electronic device may be one or more, and one processor 520 is taken as an example in fig. 5; the processor 520, the storage 510, the input device 530, and the output device 540 in the electronic apparatus may be connected by a bus or other means, and are exemplified by a bus 550 in fig. 5.
The storage device 510 is a computer-readable storage medium, and can be used to store software programs, computer-executable programs, and module units, such as program instructions corresponding to the interface testing method in the embodiment of the present application.
The storage device 510 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the storage 510 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device. In some examples, storage 510 may further include memory located remotely from processor 520, which may be connected via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 530 may be used to receive input numbers, character information, or voice information, and to generate key signal inputs related to user settings and function control of the electronic apparatus. The output device 540 may include a display screen, speakers, etc. of electronic equipment.
The electronic equipment provided by the embodiment of the application can achieve the purposes of improving the interface testing speed and the processing effect.
The interface testing device, the storage medium and the electronic device provided in the above embodiments can execute the interface testing method provided in any embodiment of the present application, and have corresponding functional modules and beneficial effects for executing the method. For technical details that are not described in detail in the above embodiments, reference may be made to the interface test method provided in any embodiment of the present application.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present application and the technical principles employed. It will be understood by those skilled in the art that the present application is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, although the present application has been described in more detail with reference to the above embodiments, the present application is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present application, and the scope of the present application is determined by the scope of the appended claims.

Claims (10)

1. An interface testing method, comprising:
responding to the import operation of the test case, and importing the test case; the test case is filled and generated based on a test case template;
responding to the test operation, and performing http interface test by adopting the test case to obtain a test result of the test case;
and writing the test result back to the test case, and displaying the test result of the test case in the test process.
2. The method of claim 1, wherein in response to a test operation, performing an http interface test using the test case to obtain a test result of the test case comprises:
responding to the test operation, and carrying out file validity check on the test case;
if the file legality is met, performing http interface test by using the test case to obtain a test result of the test case;
if the file legality is not met, the test is finished, and the popup prompts abnormal information of the test case.
3. The method of claim 2, wherein performing an http interface test using the test case comprises:
performing parameter pre-analysis on the test case to determine whether a target parameter variable name exists;
if the http request parameter exists, analyzing a target parameter of the test case to obtain an http request parameter;
and initiating an http request according to the http request parameter, and obtaining a response result of the http request.
4. The method of claim 3, wherein obtaining test results for test cases comprises:
adopting a preset data extraction rule to extract data of a response result of the http request to obtain a test result;
and verifying the test result by adopting a preset verification rule.
5. The method according to claim 1, wherein the test case generation process comprises:
displaying a template form file for filling in the content of the test case;
and generating the test case according to the content of the test case and the preset incidence relation in the template form file.
6. The method of claim 1, wherein the test case includes at least one test field;
correspondingly, the writing back the test result to the test case includes:
determining a target test field associated with the test result;
if the test result is successful, recording test success information in the target test field;
and if the test result is test failure, determining the reason of the test failure, and recording the test failure and the reason of the test failure in the target test field.
7. The method of claim 2, wherein the file legitimacy comprises: at least one of header integrity, test parameter type to model conformance, and json syntax compliance for json-type test parameters.
8. An interface testing apparatus, comprising:
the test case importing module is used for responding to the importing operation of the test case and importing the test case; the test case is filled and generated based on a test case template;
the test result obtaining module is used for responding to the test operation and adopting the test case to carry out http interface test so as to obtain the test result of the test case;
and the test result write-back module is used for writing back the test result to the test case and displaying the test result of the test case in the test process.
9. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the interface testing method according to any one of claims 1 to 7.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the interface testing method according to any one of claims 1-7 when executing the computer program.
CN202011162873.4A 2020-10-27 2020-10-27 Interface testing method and device, storage medium and electronic equipment Active CN112367220B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011162873.4A CN112367220B (en) 2020-10-27 2020-10-27 Interface testing method and device, storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011162873.4A CN112367220B (en) 2020-10-27 2020-10-27 Interface testing method and device, storage medium and electronic equipment

Publications (2)

Publication Number Publication Date
CN112367220A true CN112367220A (en) 2021-02-12
CN112367220B CN112367220B (en) 2022-11-29

Family

ID=74510646

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011162873.4A Active CN112367220B (en) 2020-10-27 2020-10-27 Interface testing method and device, storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN112367220B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113609025A (en) * 2021-08-18 2021-11-05 深圳鼎盛电脑科技有限公司 Software program testing method, device, medium and equipment
CN115047836A (en) * 2022-06-27 2022-09-13 中国核动力研究设计院 Test case generation and loading method and system based on DCS system periodic test
CN115396332A (en) * 2022-06-20 2022-11-25 内蒙古电力(集团)有限责任公司内蒙古超高压供电分公司 Fuzzy test method of power communication protocol, terminal equipment and storage medium

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080040732A1 (en) * 2006-03-09 2008-02-14 International Business Machines Corporation Testing scenarios that sequentially execute a plurality of application program interfaces
CN105468524A (en) * 2015-11-25 2016-04-06 上海斐讯数据通信技术有限公司 Automatic test method and system of WEB interface
CN110362497A (en) * 2019-07-23 2019-10-22 上海金融期货信息技术有限公司 Cover the automation api interface test method and system of full unusual character
CN110704328A (en) * 2019-10-15 2020-01-17 北京城市网邻信息技术有限公司 Interface testing method and device, electronic equipment and readable storage medium
CN111679989A (en) * 2020-06-16 2020-09-18 贝壳技术有限公司 Interface robustness testing method and device, electronic equipment and storage medium
CN111813701A (en) * 2020-09-09 2020-10-23 平安国际智慧城市科技股份有限公司 HTTP-based interface testing method and device, computer equipment and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080040732A1 (en) * 2006-03-09 2008-02-14 International Business Machines Corporation Testing scenarios that sequentially execute a plurality of application program interfaces
CN105468524A (en) * 2015-11-25 2016-04-06 上海斐讯数据通信技术有限公司 Automatic test method and system of WEB interface
CN110362497A (en) * 2019-07-23 2019-10-22 上海金融期货信息技术有限公司 Cover the automation api interface test method and system of full unusual character
CN110704328A (en) * 2019-10-15 2020-01-17 北京城市网邻信息技术有限公司 Interface testing method and device, electronic equipment and readable storage medium
CN111679989A (en) * 2020-06-16 2020-09-18 贝壳技术有限公司 Interface robustness testing method and device, electronic equipment and storage medium
CN111813701A (en) * 2020-09-09 2020-10-23 平安国际智慧城市科技股份有限公司 HTTP-based interface testing method and device, computer equipment and storage medium

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113609025A (en) * 2021-08-18 2021-11-05 深圳鼎盛电脑科技有限公司 Software program testing method, device, medium and equipment
CN115396332A (en) * 2022-06-20 2022-11-25 内蒙古电力(集团)有限责任公司内蒙古超高压供电分公司 Fuzzy test method of power communication protocol, terminal equipment and storage medium
CN115396332B (en) * 2022-06-20 2024-03-15 内蒙古电力(集团)有限责任公司内蒙古超高压供电分公司 Fuzzy test method for power communication protocol, terminal equipment and storage medium
CN115047836A (en) * 2022-06-27 2022-09-13 中国核动力研究设计院 Test case generation and loading method and system based on DCS system periodic test

Also Published As

Publication number Publication date
CN112367220B (en) 2022-11-29

Similar Documents

Publication Publication Date Title
CN112367220B (en) Interface testing method and device, storage medium and electronic equipment
US8433733B2 (en) Web application record-replay system and method
US7996818B1 (en) Method for testing using client specified references
WO2018184361A1 (en) Application test method, server, terminal, and storage media
CN111897724B (en) Automatic testing method and device suitable for cloud platform
CN112597014B (en) Automatic test method and device based on data driving, medium and electronic equipment
CN103729294A (en) Method and device for testing performance script of application software
CN112540924A (en) Interface automation test method, device, equipment and storage medium
CN116841865A (en) Visual test method and device, electronic equipment and storage medium
CN113296653B (en) Simulation interaction model construction method, interaction method and related equipment
KR101792864B1 (en) System and Method for verifying application
CN111124937B (en) Method and system for assisting in improving test case generation efficiency based on instrumentation function
CN113836014A (en) Interface testing method and device, electronic equipment and storage medium
US20050203717A1 (en) Automated testing system, method and program product using testing map
CN112667219A (en) Code generation method and device, equipment and computer readable storage medium
CN111949537A (en) Interface test method, device, equipment and medium
CN115470152B (en) Test code generation method, test code generation device, and storage medium
CN116166533A (en) Interface testing method, device, terminal equipment and storage medium
CN113238940B (en) Interface test result comparison method, device, equipment and storage medium
Wang et al. Application of model-based testing on a quorum-based distributed storage
CN113886221A (en) Test script generation method and device, storage medium and electronic equipment
CN113282476A (en) Interface performance testing method and device and electronic equipment
CN111813665A (en) Big data platform interface data testing method and system based on python
CN113094281B (en) Test method and device for hybrid App
CN111522737B (en) Automatic test verification method and device for front-end interface and storage medium

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