CN115952508A - Test case test generation method, system, computer device and storage medium - Google Patents
Test case test generation method, system, computer device and storage medium Download PDFInfo
- Publication number
- CN115952508A CN115952508A CN202211611579.6A CN202211611579A CN115952508A CN 115952508 A CN115952508 A CN 115952508A CN 202211611579 A CN202211611579 A CN 202211611579A CN 115952508 A CN115952508 A CN 115952508A
- Authority
- CN
- China
- Prior art keywords
- interface
- parameter
- request
- test case
- generating
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The application relates to a test case test generation method, a test case test generation system, computer equipment and a storage medium. The method comprises the following steps: setting a plug-in for capturing interface information in a browser, wherein the plug-in automatically captures interface request data of a clicked target function and generates a data exchange file for recording all interface information; acquiring interface request data in the data exchange file, and analyzing the parameter types, parameter lengths and parameter values of all parameters; combining and generating an interface parameter test case according to a request mode of an interface and the content of the interface request data; generating an interface safety test case according to the user-free identity authentication and the SOL injection direction of the interface; and storing all the interface information, the interface parameter test cases and the interface safety test cases into a database. The method can automatically generate the test case and improve the efficiency.
Description
Technical Field
The present application relates to the field of software development technologies, and in particular, to a test case test generation method, system, computer device, and storage medium.
Background
With the continuous update and iteration of software projects, functions are more and more, and more backend interfaces are developed. The interface test is very important, and the interface test generally comprises the parameter and function test of the interface and the safety test of the interface. Interface parameters and interface information documents which need to be input by developers in the functional test of the interface are compiled and used by testers. The number of the interfaces is increased, so that the time cost of developers and the time cost of testers are increased continuously, and due to the limitation of project time, the test case is frequently missed and the quality of a project is affected. However, the safety test of the interface is often not taken into consideration, so that the project has great potential safety hazard.
To solve these problems, the conventional solutions are: interface parameter testing and functional testing often introduce automated testing techniques to replace most interface regression testing. The traditional interface automation test needs to go through the following five major steps: the method comprises the following steps: manually inputting a large number of interface parameters by a developer, and performing the following steps: the tester designs an automatic test case scheme according to the input interface parameters, and the third step is that: compiling the interface automatic test case in the excel according to the interface automatic test case scheme designed in the step two, and the step four: executing an interface automation test case program, and performing the following steps: and obtaining a report of the interface of the automatic test case of the execution interface. And the safety test of the interface is manually tested.
The traditional interface parameter test and function automation test scheme needs a lot of time for developers to input interface information, and if the interface information is not subjected to document landing in the past, more time is needed to fill the previous interface. The input of a large amount of interface information often causes interface parameter recording errors or missing records, and the design and compiling quality of test cases of later-stage testers is affected. For testers, the scheme has high dependency on technical level, high learning cost and high case writing time cost, and the defects finally cause that the interface automation test case project is difficult to land. However, although the interface security test is performed once, the interface code is not changed and then the security test is not performed again, which has a drawback in terms of security.
Disclosure of Invention
In view of the above, it is necessary to provide a test case test generation method, system, computer device and storage medium, which can solve at least one of the following deficiencies of the prior art: when a developer supplements a large amount of interface information data of historical versions and continuously increasing new requirements, records need to be manually filled; the interface parameter automatic test case needs to be manually compiled; interface safety test cases need to be manually compiled; the interface safety test is not included in the automatic test system; the interface automation test case is stored in the excel, data is disordered, and the excel storage mode is unsafe.
In one aspect, a test case test generation method is provided, and the method includes:
setting a plug-in for capturing interface information in a browser, wherein the plug-in automatically captures interface request data of a clicked target function and generates a data exchange file for recording all interface information;
acquiring interface request data in the data exchange file, and analyzing the parameter types, parameter lengths and parameter values of all parameters;
combining and generating an interface parameter test case according to the request mode of the interface and the content of the interface request data;
generating an interface safety test case according to the user-free identity verification and the SOL injection direction of the interface;
and storing all the interface information, the interface parameter test cases and the interface safety test cases into a database.
In one embodiment, in the step of automatically capturing the interface request data of the clicked target function by the plug-in, the method includes:
synchronously starting a plug-in for capturing interface information when a browser is started;
detecting whether a clicked target function exists in a browser page or not in real time;
when the clicked target function exists, the plug-in automatically captures interface request data of the clicked target function, wherein the interface request data comprises a uniform resource locator, a request header, a request body, a request protocol and a return parameter of an interface;
and generating the interface request data into a data exchange file for recording all interface information.
In one embodiment, the step of obtaining the interface request data in the data exchange file and analyzing the parameter types, the parameter lengths and the parameter values of all the parameters includes:
analyzing uniform resource locators, request headers, request bodies, request protocols and return parameters of all interfaces in the data exchange file;
and recursively analyzing the parameter types, the parameter lengths and the parameter values of all parameters of each request body.
In one embodiment, the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data includes:
acquiring a request mode of an interface, wherein the request mode of the interface comprises a get request, a post request, a head request, a put request, a delete request and an options request;
obtaining parameter types, wherein the parameter types comprise String, int, long and double;
acquiring parameter lengths, wherein the parameter lengths comprise a parameter minimum length and a parameter maximum length;
acquiring a parameter value range, wherein the parameter value range comprises an upper boundary value, a lower boundary value and a normal value between the upper boundary value and the lower boundary value;
acquiring a combination set composed of a plurality of combination modes according to a request mode, a parameter type, a parameter minimum length, a parameter maximum length and a parameter value range of an interface;
and respectively generating an interface parameter test case according to each combination mode in the combination set.
In one embodiment, in the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data, if the interface is analyzed as an enumeration type, an interface parameter test case is generated for each enumeration type.
In one embodiment, in the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data, the method includes:
judging whether the value range of the parameter value is limited or not;
if the parameter value range is limited, acquiring an upper boundary value and a lower boundary value within the parameter value range and a plurality of normal values between the upper boundary value and the lower boundary value, and acquiring a plurality of out-of-domain parameter values outside the parameter value range;
and respectively taking values of the normal value, the upper boundary value, the lower boundary value and the out-of-domain parameter value to generate an interface parameter test case.
In one embodiment, the step of generating the interface security test case according to the user-less identity authentication and the SOL injection direction of the interface includes:
acquiring a storage position of user identity authentication information; the user identity authentication information storage position comprises a cookie stored in a browser end and/or a session stored in a server end;
generating an interface security test case without cookie or session according to the storage position of the user identity authentication information;
and generating a cookie or session interface safety test case carrying error information according to the storage position of the user identity authentication information.
In one embodiment, the step of storing all the interface information, the interface parameter test cases and the interface security test cases in the database includes:
acquiring all interface information, naming each interface name to annotate each interface function, and asynchronously importing the interface information into an interface information table of a database for storage;
storing all interface parameter test cases and all interface safety test cases into a database;
and acquiring a test report generated after the interface parameter test case and the interface safety test case are operated, and storing the test report into a database.
In another aspect, a test case generation system is provided, the system including:
the plug-in management module is used for setting a plug-in for capturing interface information in the browser, automatically capturing interface request data of a clicked target function by the plug-in and generating a data exchange file for recording all interface information;
the interface parameter analysis module is used for acquiring interface request data in the data exchange file and analyzing the parameter types, parameter lengths and parameter values of all parameters;
the interface parameter test case generation module is used for generating an interface parameter test case according to the request mode of the interface and the content of the interface request data in a combined mode;
the interface safety test case generation module is used for generating an interface safety test case according to the user identity authentication-free direction and the SOL (sequence of load) injection direction of the interface;
and the data storage management module is used for storing all the interface information, the interface parameter test cases and the interface safety test cases into a database.
In another aspect, a computer device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to perform the following steps:
setting a plug-in for capturing interface information in a browser, wherein the plug-in automatically captures interface request data of a clicked target function and generates a data exchange file for recording all interface information;
acquiring interface request data in the data exchange file, and analyzing the parameter types, parameter lengths and parameter values of all parameters;
combining and generating an interface parameter test case according to a request mode of an interface and the content of the interface request data;
generating an interface safety test case according to the user-free identity authentication and the SOL injection direction of the interface;
and storing all the interface information, the interface parameter test cases and the interface safety test cases into a database.
In yet another aspect, a computer-readable storage medium is provided, having stored thereon a computer program which, when executed by a processor, performs the steps of:
setting a plug-in for capturing interface information in a browser, wherein the plug-in automatically captures interface request data of a clicked target function and generates a data exchange file for recording all interface information;
acquiring interface request data in the data exchange file, and analyzing the parameter types, parameter lengths and parameter values of all parameters;
combining and generating an interface parameter test case according to a request mode of an interface and the content of the interface request data;
generating an interface safety test case according to the user-free identity authentication and the SOL injection direction of the interface;
and storing all the interface information, the interface parameter test cases and the interface safety test cases into a database.
The test case test generation method, the test case test generation system, the computer equipment and the storage medium can automatically capture the interface request data of the target function and automatically generate the interface safety test case and the interface parameter test case, so that the working time cost of developers and software testers is greatly saved, the quality and the success rate of the interface automatic test case are greatly improved, and the quality of a project is greatly guaranteed.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be 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 block diagram illustrating the front-end and back-end functionality of a test case generation system in one embodiment;
FIG. 2 is a schematic view of a workflow of a browser plug-in one embodiment;
FIG. 3 is a flow diagram that illustrates the use of the test case generation system in one embodiment;
FIG. 4 is a diagram of an application environment of the test case generation method according to an embodiment;
FIG. 5 is a flowchart illustrating a test case generation method according to an embodiment;
FIG. 6 is a flowchart illustrating the steps of the plug-in automatically capturing the interface request data of the clicked target function in one embodiment;
FIG. 7 is a flowchart illustrating steps of obtaining interface request data in the data exchange file, and analyzing the parameter types, parameter lengths, and parameter values of all parameters according to an embodiment;
FIG. 8 is a flowchart illustrating a step of generating an interface parameter test case according to a request mode of an interface and contents of interface request data in one embodiment;
FIG. 9 is a flowchart illustrating a step of generating an interface parameter test case according to a request manner of an interface and contents of the interface request data in an embodiment;
FIG. 10 is a flowchart illustrating steps of generating interface security test cases according to the SOL injection direction of the interface without user authentication in one embodiment;
FIG. 11 is a flowchart illustrating the steps of storing all interface information, interface parameter test cases, and interface security test cases in a database in one embodiment;
FIG. 12 is a block diagram showing the structure of a test case generation system according to another embodiment;
FIG. 13 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
As described in the background, the prior art has disadvantages including: when a developer supplements a large amount of interface information data of historical versions and continuously increasing new requirements, records need to be manually filled; the interface parameter automatic test case needs to be manually compiled; interface safety test cases need to be manually compiled; the interface safety test is not included in the automatic test system; the interface automation test case is stored in the excel, data is disordered, and the excel storage mode is unsafe.
In order to solve at least one of the above problems, embodiments of the present invention creatively provide a test case generation method and a test case generation system, which can automatically generate interface information, an interface security test case (hereinafter, referred to as an interface security test case test for short), and an interface parameter test case.
The browser (Chrome) plug-in for developing and capturing interface request information has the specific functions of: after the plug-in is started, a recording button is clicked, a specific function is clicked on a page needing to capture interface information, the plug-in can automatically capture detailed interface request data after the page is clicked, wherein the detailed interface request data comprises an interface url, a request head, a request body, a request protocol and a return parameter, and finally a json file recording all interface information is generated after clicking and stopping recording and is used for importing the interface information into a test case test generation system.
And designing a front-end page ui pattern and function of the test case test generation system, wherein the front-end page ui pattern and function mainly comprise an interface information module and an automatic test case module. The interface information module has the functions of interface information list display, interface information import, interface information addition, deletion, modification and check, interface debugging and automatic generation of automatic test cases. The automatic test case module has the functions of an automatic test case display list, automatic test case adding, deleting, modifying and checking, automatic test case running and the like.
The interface information importing function and the Chrome plug-in recording interface information function which is developed by matching the automatic test case generating function enable the automatic test to be intelligent.
The interface information importing function imports an interface information json file recorded by a Chrome plug-in, then the test case test generation system intelligently analyzes url, a request head, a request body, a request protocol and return parameters of all interfaces in the json file, recursively analyzes types and parameter values of all parameters of the request body, and newly adds and enters an interface information module after the required interfaces are screened.
And (3) automatically generating (interface parameter) automatic test case function, namely, after the asynchronous request automatically generates a case request, analyzing the parameter automatic test case of the specified interface and the safety automatic test case of the interface by the system. The parameter automatic test case can be combined to generate a test case according to the request mode, the parameter type, the parameter minimum length, the parameter maximum length and whether the parameters need to be filled in or not of the interface, the interface types include String, int, long, double and the like, if an enumeration type is met in interface analysis, each enumeration needs to be tested, and the normal value, the upper boundary value, the lower boundary value and the value outside the range need to be evaluated for limited entry parameters. And generating an interface safety test case according to the user identity authentication-free direction and the SOL injection direction of the interface.
And selecting vue to develop the front-end page of the test case test generation system.
And (4) selecting a flash framework of python to develop the rear end of the test case test generation system, storing all interface information and the automatic test cases into a mySOL database, and performing persistent management.
As shown in fig. 1, the front-end page function of the test case generation system includes an interface management module and a case management module. The interface management module manages an interface list, interface information import, interface information, automatic test case generation and interface information addition, deletion, modification and check. And the case management module is used for managing the increase, deletion, modification and check of the use cases in the use case list and the operation of the automatic test cases.
As shown in fig. 1, a back-end core component of the test case test generation system includes an interface information import module and an automatic test case generation module. The interface information import module is used for intelligently analyzing the imported interface data in the json file; acquiring information of each interface, wherein the information comprises an interface url, a request head, a request body, a request protocol and a return parameter; and connecting the database, and storing the interface information into an interface information table of the mysgl database. The automatic test case generation module is used for intelligently analyzing the request protocol, the parameter type, the minimum parameter length, the maximum parameter length and whether the parameters need to be filled to generate an interface parameter test case in a combined mode; and generating an interface safety test case according to the identity verification of the user and the injection of the interface sal.
As shown in fig. 2, when the test case generation system is used, the test case generation system includes the following steps:
setting an interface domain name to be captured;
entering a page needing to capture an interface;
starting a plug-in;
a function of clicking a page by a mouse;
the plug-in monitors a page click event;
monitoring a page request by the plug-in;
screening out static resource requests;
removing the duplicate of the grabbed interface;
the interface information is exported locally.
As shown in fig. 3, based on the test case test generation system (referred to as system a in fig. 3 for short), the test case test generation method includes the following steps:
the method comprises the following steps: project interface information is captured using a developed browser plug-in provided by the present invention, with a workflow diagram as in fig. 1. In order to prevent other irrelevant interfaces from polluting data, the domain name of the interface to be captured needs to be set in advance, and a plurality of target domain names can be set at the same time. After entering a page after the items are required to be captured, starting a plug-in to start recording an interface. The plug-in monitors a rear-end interface request generated by a user in a page clicking event in real time and records interface information, and supports different page skipping and new window interface information recording. Then, static resource requests including css files, js files, picture files and html files are screened out, and repeated interfaces obtained through capturing are removed. And after the page function needing to be captured is clicked, the export button is clicked, and all interfaces captured during the recording period are exported to the local json file.
Step two: and entering an interface information module of the test case test generation system, clicking an interface import function, after importing a json file exported by a browser plug-in, intelligently analyzing interface information recorded in the file, wherein the interface information comprises an interface url, a request header, a request body, a request protocol and a return parameter, and finally naming each interface name to annotate each interface function and then asynchronously importing the interface name into an interface information table of a mySOL database for storage.
Step three: and (4) the tester enters the interface list to select an interface, and after clicking the automatic generation case button, an interface parameter test case and an interface safety test case are generated.
The parameter test case can be combined to generate a test case according to an interface request mode, a parameter type, a parameter minimum length, a parameter maximum length and whether parameters need to be filled or not of an interface, wherein the interface types comprise String, int, long, double and the like. The interface request modes include get, post, put, delete, etc., and one interface is tested by using the commonly used request modes.
And generating an interface safety test case according to the user identity authentication-free direction of the interface and the SOL injection direction of the interface. The logic of no user authentication is: the user identity verification refers to verifying whether a user has a behavior of accessing a system in a right way, the second permission is generally that after logging in an interface, a cookie stored in a user browser by a Web server or a session id generated by the server and stored in the server is carried in an interface request head needing the user identity verification to request, the identity verification can be used for carrying out logic processing on a continuous rear end through the rear part, and aiming at the point, an interface safety test case which does not carry the cookie or session or carries an error cookie or session when the user identity verification interface request is generated. The injection of the interface SOL refers to that the rationality of data input by a user is not judged, parameters transmitted from the front end to the back end are controllable by an attacker, and the parameters are brought into a database for query, and the attacker can carry out random query on the database by constructing different SOL statements. Through the loophole, SOL injection safety test cases of two schemes of digital injection and character injection are automatically generated.
Wherein, the session and the cookie are distinguished as follows:
1) The stored positions are different
The cookie is stored in the browser end, and the session is stored in the server end.
2) Different using modes
If the cookie is set at the browser end for the corresponding time, the cookie is stored in the local hard disk, and at the moment, if the cookie is not expired, the cookie can be used, and if the cookie is expired, the cookie is deleted. If no time is set for the cookie, the cookie is deleted by default if the browser is closed.
session: in the request, if there is a sessionId in the sent request, a corresponding sessionobject is found, if there is no sessionId, a sessionobject is created on the server side, and the sessionId is returned to the browser, which can be put into a cookie for transmission, if the browser does not support the cookie, it should be called through encoderl (sessionId) and then put into url.
3) The storage contents are different: the cookie can only store character strings, and the session storage structure is similar to a hash table structure and can store any type.
4) Storage size: the cookie can store content of 4k size at most, and session is not limited.
5) sessions are more secure than cookies.
6) Application scenario of session of cookie: the cookie can be used for storing login information of the user, and if the cookie is deleted, the user still needs to log in again next time; session is similar to the situation that a key is taken to unlock the lock, the information that we take is personal information, and generally, the information of the person or the information of a shopping cart can be stored in the session.
7) session and cookie drawbacks: the cookie is limited in size and unsafe for use if the user disables the cookie. If too many users rely on session, when many users log on at the same time, the server is over stressed. sessionId is stored in cookie, which is also unsafe if cookie is not supported for some browsers, when code needs to be rewritten and sessionId is put in url.
Step four: and (4) the tester checks the generated test case, and names the test case after assertion addition debugging (the default case name generated automatically is the interface name). The test case combination is added to the test suite.
Step five: and carrying out manual test case suite running or timing running according to the actual project test strategy.
Step six: and generating a test report after the test case suite is operated, so that the test result can be conveniently analyzed.
The above describes the automatic generation of interface information, interface security, and interface parameter automation test case system and method in detail through the actual implementation and use steps. The invention greatly saves the working time cost of developers and software testers, greatly improves the quality and the success rate of the interface automation test case, and ensures the quality of the project to be more ensured.
Example 2
Based on the same inventive concept as that of embodiment 1, embodiment 2 includes all the technical features of embodiment 1. The test case test generation method provided in embodiment 2 of the present application can be applied to an application environment shown in fig. 4. Wherein the terminal 102 communicates with the server 104 via a network. The terminal 102 may be, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the terminal 102 can display a browser and can install a plug-in the browser. The server 104 may be implemented as a stand-alone server or a server cluster comprised of multiple servers. The server 104 has a database, and can control the operation of the plug-in, acquire the interface parameter data acquired by the plug-in, analyze and process the interface parameter data, and automatically generate a test case, where the generated test case includes interface information, an interface security test case (hereinafter, referred to as an interface security test case test) and an interface parameter test case.
In an embodiment, as shown in fig. 5, a test case test generation method is provided, which is described by taking the method as an example applied to the server 104 in fig. 4, and includes the following steps:
s1, a plug-in for capturing interface information is arranged in a browser, automatically captures interface request data of a clicked target function and generates a data exchange file for recording all interface information;
s2, acquiring interface request data in the data exchange file, and analyzing the parameter types, parameter lengths and parameter values of all parameters;
s3, combining and generating an interface parameter test case according to the request mode of an interface and the content of the interface request data;
s4, generating an interface safety test case according to the user-free identity verification and the SOL injection direction of the interface;
and S5, storing all the interface information, the interface parameter test cases and the interface safety test cases into a database.
The data exchange file in step S1 is preferably a json file; the json file is a file used for storing simple data structures and objects, and can exchange data in a web application program; json is known collectively as JavaScript object notification, and is a well-organized, easily accessible method of storing information.
SOL injection (SOLinjecton), also called SOL injection or SOL annotation, occurs in step S4, which is a security hole in the application and database layers. In short, SOL instructions are injected into the input character strings, character check is omitted in a poorly designed program, and the injected malicious instructions are mistakenly regarded as normal SOL instructions by the database server to run, so that the SOL instructions are damaged or invaded.
As shown in fig. 6, in this embodiment, the step of automatically capturing the interface request data of the clicked target function by the plug-in includes:
s11, synchronously starting a plug-in for capturing interface information when the browser is started;
s12, detecting whether a clicked target function exists in the browser page in real time;
step S13, when the clicked target function exists, the plug-in automatically captures interface request data of the clicked target function, wherein the interface request data comprises a uniform resource locator (url) of an interface, a request head, a request body, a request protocol and a return parameter;
and step S14, generating the interface request data into a data exchange file for recording all interface information.
As shown in fig. 7, in the step of acquiring the interface request data in the data exchange file and analyzing the parameter types, the parameter lengths, and the parameter values of all the parameters, the method includes:
step S21, analyzing uniform resource locators, request headers, request bodies, request protocols and return parameters of all interfaces in the data exchange file;
step S22, recursively analyzing the parameter types, parameter lengths and parameter values of all parameters of each request body.
As shown in fig. 8, in this embodiment, the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data includes:
step S31, acquiring a request mode of an interface, wherein the request mode of the interface comprises a get request, a post request, a head request, a put request, a delete request and an options request;
step S32, acquiring parameter types, wherein the parameter types comprise String, int, long and double;
step S33, acquiring parameter lengths, wherein the parameter lengths comprise a parameter minimum length and a parameter maximum length;
step S34, acquiring a parameter value range, wherein the parameter value range comprises an upper boundary value, a lower boundary value and a normal value between the upper boundary value and the lower boundary value;
step S35, acquiring a combination set composed of a plurality of combination modes according to the request mode, the parameter type, the minimum parameter length, the maximum parameter length and the value range of the parameter value of the interface;
and S36, respectively generating an interface parameter test case according to each combination mode in the combination set.
The basic data types are: byte, short, int, long, float, double, boolean, char, 8. And the String type is a java.
In this embodiment, in the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data, if the interface is analyzed as an enumeration type, an interface parameter test case is generated for each enumeration type.
As shown in fig. 9, in the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data in the embodiment, the step includes:
step S361, judging whether the value range of the parameter value has limitation;
step S362, if the parameter value range is limited, acquiring an upper boundary value and a lower boundary value within the parameter value range and a plurality of normal values between the upper boundary value and the lower boundary value, and acquiring a plurality of out-of-domain parameter values outside the parameter value range;
and step S363, taking the normal value, the upper boundary value, the lower boundary value and the out-of-domain parameter value respectively to generate an interface parameter test case.
As shown in fig. 10, in the step of generating an interface security test case according to the user-less identity authentication and the SOL injection direction of the interface in the embodiment, the step includes:
step S41, obtaining a storage position of user identity authentication information; the user identity authentication information storage position comprises a cookie stored in a browser end and/or a session stored in a server end;
step S42, generating an interface security test case without cookie or session according to the storage position of the user identity authentication information;
and S43, generating a cookie or session interface safety test case carrying error information according to the storage position of the user identity authentication information.
As shown in fig. 11, in this embodiment, the step of storing all the interface information, the interface parameter test cases, and the interface security test cases in the database includes:
s51, acquiring all interface information, naming each interface name to annotate each interface function, and asynchronously importing the interface name into an interface information table of a database for storage;
step S52, storing all interface parameter test cases and all interface safety test cases into a database;
and S53, acquiring a test report generated after the interface parameter test case and the interface safety test case are operated, and storing the test report into a database.
According to the test case generation method, the interface request data of the target function can be automatically captured, the interface safety test case and the interface parameter test case can be automatically generated, the working time cost of developers and software testers is greatly saved, the quality and the success rate of the interface automatic test case are greatly improved, and the quality of a project is greatly guaranteed.
It should be understood that, although the respective steps in the flowcharts of fig. 5 to 11 are sequentially shown as indicated by arrows, the steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 5-11 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performing the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.
In one embodiment, as shown in fig. 12, there is provided a test case test generation system 10, including: the system comprises a plug-in management module 1, an interface parameter analysis module 2, an interface parameter generating test case module 3, an interface safety generating test case module 4 and a data storage management module 5.
The plug-in management module 1 is used for setting a plug-in for capturing interface information in a browser, and the plug-in automatically captures interface request data of a clicked target function and generates a data exchange file for recording all interface information. Wherein the data exchange file is preferably a json file; the json file is a file used for storing a simple data structure and an object, and can exchange data in a web application program; json is known collectively as JavaScriptObjectNotation, and is a well-organized, easy-to-access method of storing information.
The interface parameter analysis module 2 is configured to obtain interface request data in the data exchange file, and analyze parameter types, parameter lengths, and parameter values of all parameters.
The interface parameter test case generation module 3 is used for generating an interface parameter test case by combining the request mode of the interface and the content of the interface request data.
The interface safety test case generating module 4 is used for generating an interface safety test case according to the direction of injection of the interface SOL without user identity verification.
The data storage management module 5 is used for storing all interface information, interface parameter test cases and interface safety test cases into a database.
In this embodiment, the step of automatically capturing the interface request data of the clicked target function by the plug-in includes:
synchronously starting a plug-in for capturing interface information when a browser is started;
detecting whether a clicked target function exists in a browser page or not in real time;
when the clicked target function exists, the plug-in automatically captures interface request data of the clicked target function, wherein the interface request data comprises a uniform resource locator, a request header, a request body, a request protocol and a return parameter of an interface;
and generating the interface request data into a data exchange file for recording all interface information.
In this embodiment, the step of obtaining the interface request data in the data exchange file and analyzing the parameter types, the parameter lengths, and the parameter values of all the parameters includes:
analyzing uniform resource locators, request headers, request bodies, request protocols and return parameters of all interfaces in the data exchange file;
and recursively analyzing the parameter types, the parameter lengths and the parameter values of all parameters of each request body.
In this embodiment, the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data includes:
acquiring a request mode of an interface, wherein the request mode of the interface comprises a get request, a post request, a head request, a put request, a delete request and an options request;
obtaining parameter types, wherein the parameter types comprise String, int, long and double;
acquiring parameter lengths, wherein the parameter lengths comprise a parameter minimum length and a parameter maximum length;
acquiring a parameter value range, wherein the parameter value range comprises an upper boundary value, a lower boundary value and a normal value between the upper boundary value and the lower boundary value;
acquiring a combination set composed of a plurality of combination modes according to a request mode, a parameter type, a parameter minimum length, a parameter maximum length and a parameter value range of an interface;
and respectively generating an interface parameter test case according to each combination mode in the combination set.
In this embodiment, in the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data, if the interface is analyzed as an enumeration type, an interface parameter test case is generated for each enumeration type.
In this embodiment, the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data includes:
judging whether the value range of the parameter value is limited or not;
if the parameter value range is limited, acquiring an upper boundary value and a lower boundary value within the parameter value range and a plurality of normal values between the upper boundary value and the lower boundary value, and acquiring a plurality of out-of-domain parameter values outside the parameter value range;
and respectively carrying out value taking on the normal value, the upper boundary value, the lower boundary value and the out-of-domain parameter value to generate an interface parameter test case.
In this embodiment, the step of generating the interface security test case according to the interface identity verification without user and the interface SOL injection direction includes:
acquiring a user identity authentication information storage position; the user identity authentication information storage position comprises a cookie stored in a browser end and/or a session stored in a server end;
generating an interface security test case without cookie or session according to the storage position of the user identity authentication information;
and generating a cookie or session interface safety test case carrying error information according to the storage position of the user identity authentication information.
In this embodiment, the step of storing all the interface information, the interface parameter test cases, and the interface security test cases in the database includes:
acquiring all interface information, naming each interface name to annotate each interface function, and asynchronously importing the interface information into an interface information table of a database for storage;
storing all interface parameter test cases and all interface safety test cases into a database;
and acquiring a test report generated after the interface parameter test case and the interface safety test case are operated, and storing the test report into a database.
In the test case generation system, the interface request data of the target function can be automatically captured, and the interface safety test case and the interface parameter test case can be automatically generated, so that the working time cost of developers and software testers is greatly saved, the quality and the success rate of the interface automatic test case are greatly improved, and the quality of a project is greatly guaranteed.
For specific limitations of the test case generation system, reference may be made to the above limitations of the test case generation method, which is not described herein again. All or part of each module in the test case test generation system can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent of a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 13. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operating system and the computer program to run on the non-volatile storage medium. The database of the computer device is used for storing test case test generation data. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a test case test generation method.
Those skilled in the art will appreciate that the architecture shown in fig. 13 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
setting a plug-in for capturing interface information in a browser, wherein the plug-in automatically captures interface request data of a clicked target function and generates a data exchange file for recording all interface information;
acquiring interface request data in the data exchange file, and analyzing the parameter types, parameter lengths and parameter values of all parameters;
combining and generating an interface parameter test case according to a request mode of an interface and the content of the interface request data;
generating an interface safety test case according to the user-free identity authentication and the SOL injection direction of the interface;
and storing all the interface information, the interface parameter test cases and the interface safety test cases into a database.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
in the step of automatically capturing interface request data of the clicked target function by the plug-in, the method comprises the following steps:
synchronously starting a plug-in for capturing interface information when a browser is started;
detecting whether a clicked target function exists in a browser page in real time;
when the clicked target function exists, the plug-in automatically captures interface request data of the clicked target function, wherein the interface request data comprise a uniform resource locator, a request head, a request body, a request protocol and a return parameter of an interface;
and generating the interface request data into a data exchange file for recording all interface information.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
in the step of obtaining the interface request data in the data exchange file and analyzing the parameter types, the parameter lengths and the parameter values of all the parameters, the method comprises the following steps:
analyzing uniform resource locators, request headers, request bodies, request protocols and return parameters of all interfaces in the data exchange file;
and recursively analyzing the parameter types, the parameter lengths and the parameter values of all parameters of each request body.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data comprises the following steps:
acquiring a request mode of an interface, wherein the request mode of the interface comprises a get request, a post request, a head request, a put request, a delete request and an options request;
obtaining parameter types, wherein the parameter types comprise String, int, long and double;
acquiring parameter lengths, wherein the parameter lengths comprise a parameter minimum length and a parameter maximum length;
acquiring a parameter value range, wherein the parameter value range comprises an upper boundary value, a lower boundary value and a normal value between the upper boundary value and the lower boundary value;
acquiring a combination set composed of a plurality of combination modes according to a request mode, a parameter type, a parameter minimum length, a parameter maximum length and a parameter value range of an interface;
and respectively generating an interface parameter test case according to each combination mode in the combination set.
In one embodiment, the processor when executing the computer program further performs the steps of:
in the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data, if the interface is analyzed to be an enumeration type, the interface parameter test case is generated for each enumeration type.
In one embodiment, the processor when executing the computer program further performs the steps of:
in the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data, the method comprises the following steps:
judging whether the value range of the parameter value is limited or not;
if the parameter value range is limited, acquiring an upper boundary value and a lower boundary value within the parameter value range and a plurality of normal values between the upper boundary value and the lower boundary value, and acquiring a plurality of out-of-domain parameter values outside the parameter value range;
and respectively carrying out value taking on the normal value, the upper boundary value, the lower boundary value and the out-of-domain parameter value to generate an interface parameter test case.
In one embodiment, the processor when executing the computer program further performs the steps of:
in the step of generating the interface safety test case according to the user identity verification-free direction and the SOL injection direction of the interface, the method comprises the following steps:
acquiring a storage position of user identity authentication information; the user identity authentication information storage position comprises a cookie stored in a browser end and/or a session stored in a server end;
generating an interface security test case without cookie or session according to the storage position of the user identity authentication information;
and generating a cookie or session interface safety test case carrying error information according to the storage position of the user identity authentication information.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
the step of storing all the interface information, the interface parameter test cases and the interface safety test cases into a database comprises the following steps:
acquiring all interface information, naming each interface name to annotate each interface function, and asynchronously importing the interface information into an interface information table of a database for storage;
storing all the interface parameter test cases and all the interface safety test cases into a database;
and acquiring a test report generated after the interface parameter test case and the interface safety test case are operated, and storing the test report into a database.
For specific limitations of implementing steps when the processor executes the computer program, reference may be made to the above limitations of the test case test generation method, which is not described herein again.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
a plug-in for capturing interface information is arranged in the browser, automatically captures interface request data of a clicked target function and generates a data exchange file for recording all interface information;
acquiring interface request data in the data exchange file, and analyzing the parameter types, parameter lengths and parameter values of all parameters;
combining and generating an interface parameter test case according to a request mode of an interface and the content of the interface request data;
generating an interface safety test case according to the user-free identity authentication and the SOL injection direction of the interface;
and storing all the interface information, the interface parameter test cases and the interface safety test cases into a database.
In one embodiment, the computer program when executed by the processor further performs the steps of:
in the step of automatically capturing interface request data of the clicked target function by the plug-in, the method comprises the following steps:
synchronously starting a plug-in for capturing interface information when a browser is started;
detecting whether a clicked target function exists in a browser page in real time;
when the clicked target function exists, the plug-in automatically captures interface request data of the clicked target function, wherein the interface request data comprise a uniform resource locator, a request head, a request body, a request protocol and a return parameter of an interface;
and generating the interface request data into a data exchange file for recording all interface information.
In one embodiment, the computer program when executed by the processor further performs the steps of:
in the step of acquiring the interface request data in the data exchange file and analyzing the parameter types, the parameter lengths and the parameter values of all the parameters, the method comprises the following steps:
analyzing uniform resource locators, request headers, request bodies, request protocols and return parameters of all interfaces in the data exchange file;
and recursively analyzing the parameter types, the parameter lengths and the parameter values of all parameters of each request body.
In one embodiment, the computer program when executed by the processor further performs the steps of:
the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data comprises the following steps:
acquiring a request mode of an interface, wherein the request mode of the interface comprises a get request, a post request, a head request, a put request, a delete request and an options request;
obtaining parameter types, wherein the parameter types comprise String, int, long and double;
acquiring parameter lengths, wherein the parameter lengths comprise a parameter minimum length and a parameter maximum length;
acquiring a parameter value range, wherein the parameter value range comprises an upper boundary value, a lower boundary value and a normal value between the upper boundary value and the lower boundary value;
acquiring a combination set composed of a plurality of combination modes according to a request mode, a parameter type, a parameter minimum length, a parameter maximum length and a parameter value range of an interface;
and respectively generating an interface parameter test case according to each combination mode in the combination set.
In one embodiment, the computer program when executed by the processor further performs the steps of:
in the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data, if the interface is analyzed to be an enumeration type, the interface parameter test case is generated for each enumeration type.
In one embodiment, the computer program when executed by the processor further performs the steps of:
in the step of generating the interface parameter test case by combining the request mode of the interface and the content of the interface request data, the method comprises the following steps:
judging whether the value range of the parameter value has limitation or not;
if the parameter value range is limited, acquiring an upper boundary value and a lower boundary value within the parameter value range and a plurality of normal values between the upper boundary value and the lower boundary value, and acquiring a plurality of out-of-domain parameter values outside the parameter value range;
and respectively carrying out value taking on the normal value, the upper boundary value, the lower boundary value and the out-of-domain parameter value to generate an interface parameter test case.
In one embodiment, the computer program when executed by the processor further performs the steps of:
in the step of generating the interface safety test case according to the user identity verification-free direction and the SOL injection direction of the interface, the method comprises the following steps:
acquiring a user identity authentication information storage position; the user identity authentication information storage position comprises a cookie stored in a browser end and/or a session stored in a server end;
generating an interface security test case without cookie or session according to the storage position of the user identity authentication information;
and generating a cookie or session interface safety test case carrying error information according to the storage position of the user identity authentication information.
In one embodiment, the computer program when executed by the processor further performs the steps of:
the step of storing all the interface information, the interface parameter test cases and the interface safety test cases into a database comprises the following steps:
acquiring all interface information, naming each interface name to annotate each interface function, and asynchronously importing the interface information into an interface information table of a database for storage;
storing all interface parameter test cases and all interface safety test cases into a database;
and acquiring a test report generated after the interface parameter test case and the interface safety test case are operated, and storing the test report into a database.
For specific limitations of the implementation steps when the computer program is executed by the processor, reference may be made to the above limitations of the method for test case generation, which are not described herein again.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above may be implemented by hardware instructions of a computer program, which may be stored in a non-volatile computer-readable storage medium, and when executed, may include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent application shall be subject to the appended claims.
Claims (10)
1. A test case test generation method is characterized by comprising the following steps:
a plug-in for capturing interface information is arranged in the browser, automatically captures interface request data of a clicked target function and generates a data exchange file for recording all interface information;
acquiring interface request data in the data exchange file, and analyzing the parameter types, parameter lengths and parameter values of all parameters;
combining and generating an interface parameter test case according to the request mode of the interface and the content of the interface request data;
generating an interface safety test case according to the user-free identity authentication and the SOL injection direction of the interface;
and storing all the interface information, the interface parameter test cases and the interface safety test cases into a database.
2. The method for generating test cases according to claim 1, wherein the step of automatically capturing interface request data of the clicked target function by the plug-in includes:
synchronously starting a plug-in for capturing interface information when a browser is started;
detecting whether a clicked target function exists in a browser page in real time;
when the clicked target function exists, the plug-in automatically captures interface request data of the clicked target function, wherein the interface request data comprise a uniform resource locator, a request head, a request body, a request protocol and a return parameter of an interface;
and generating the interface request data into a data exchange file for recording all interface information.
3. The method for generating test cases according to claim 2, wherein the step of acquiring the interface request data in the data exchange file and analyzing the parameter types, the parameter lengths, and the parameter values of all the parameters includes:
analyzing uniform resource locators, request headers, request bodies, request protocols and return parameters of all interfaces in the data exchange file;
and recursively analyzing the parameter types, the parameter lengths and the parameter values of all parameters of each request body.
4. The method for generating test cases according to claim 3, wherein the step of generating the interface parameter test cases by combining the request mode of the interface and the content of the interface request data comprises:
acquiring a request mode of an interface, wherein the request mode of the interface comprises a get request, a post request, a head request, a put request, a delete request and an options request;
obtaining parameter types, wherein the parameter types comprise String, int, long and double;
acquiring parameter lengths, wherein the parameter lengths comprise a parameter minimum length and a parameter maximum length;
acquiring a parameter value range, wherein the parameter value range comprises an upper boundary value, a lower boundary value and a normal value between the upper boundary value and the lower boundary value;
acquiring a combination set composed of a plurality of combination modes according to a request mode, a parameter type, a parameter minimum length, a parameter maximum length and a parameter value range of an interface;
and respectively generating an interface parameter test case according to each combination mode in the combination set.
5. The method for generating test cases according to claim 4, wherein the step of generating the interface parameter test cases by combining the request mode of the interface and the content of the interface request data comprises:
judging whether the value range of the parameter value is limited or not;
if the parameter value range is limited, acquiring an upper boundary value and a lower boundary value within the parameter value range and a plurality of normal values between the upper boundary value and the lower boundary value, and acquiring a plurality of out-of-domain parameter values outside the parameter value range;
and respectively taking values of the normal value, the upper boundary value, the lower boundary value and the out-of-domain parameter value to generate an interface parameter test case.
6. The method for generating the test case test according to claim 1, wherein in the step of generating the interface security test case according to the user identity authentication-free direction and the SOL injection direction of the interface, the method comprises the steps of:
acquiring a storage position of user identity authentication information; the user identity authentication information storage position comprises a cookie stored in a browser end and/or a session stored in a server end;
generating an interface security test case without cookie or session according to the storage position of the user identity authentication information;
and generating a cookie or session interface safety test case carrying error information according to the storage position of the user identity authentication information.
7. The method for generating test cases according to claim 1, wherein the step of storing all interface information, interface parameter test cases, and interface security test cases in a database comprises:
acquiring all interface information, naming each interface name to annotate each interface function, and asynchronously importing the interface information into an interface information table of a database for storage;
storing all interface parameter test cases and all interface safety test cases into a database;
and acquiring a test report generated after the interface parameter test case and the interface safety test case are operated, and storing the test report into a database.
8. A test case generation system, the system comprising:
the plug-in management module is used for setting a plug-in for capturing interface information in the browser, automatically capturing interface request data of a clicked target function by the plug-in and generating a data exchange file for recording all interface information;
the interface parameter analysis module is used for acquiring interface request data in the data exchange file and analyzing the parameter types, parameter lengths and parameter values of all parameters;
the interface parameter test case generation module is used for generating an interface parameter test case according to the request mode of the interface and the content of the interface request data in a combined mode;
the interface safety test case generation module is used for generating an interface safety test case according to the user identity authentication-free direction and the SOL (sequence of load) injection direction of the interface;
and the data storage management module is used for storing all the interface information, the interface parameter test cases and the interface safety test cases into a database.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 7 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211611579.6A CN115952508A (en) | 2022-12-14 | 2022-12-14 | Test case test generation method, system, computer device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211611579.6A CN115952508A (en) | 2022-12-14 | 2022-12-14 | Test case test generation method, system, computer device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115952508A true CN115952508A (en) | 2023-04-11 |
Family
ID=87281902
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211611579.6A Pending CN115952508A (en) | 2022-12-14 | 2022-12-14 | Test case test generation method, system, computer device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115952508A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117130941A (en) * | 2023-10-24 | 2023-11-28 | 易方信息科技股份有限公司 | Interface automation method, system, equipment and medium based on browser plug-in |
| CN118132448A (en) * | 2024-05-06 | 2024-06-04 | 成都赛力斯科技有限公司 | Test case processing method, device, computer equipment and storage medium |
-
2022
- 2022-12-14 CN CN202211611579.6A patent/CN115952508A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117130941A (en) * | 2023-10-24 | 2023-11-28 | 易方信息科技股份有限公司 | Interface automation method, system, equipment and medium based on browser plug-in |
| CN117130941B (en) * | 2023-10-24 | 2024-03-26 | 易方信息科技股份有限公司 | Interface automation method, system, equipment and medium based on browser plug-in |
| CN118132448A (en) * | 2024-05-06 | 2024-06-04 | 成都赛力斯科技有限公司 | Test case processing method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Azad et al. | Less is more: Quantifying the security benefits of debloating web applications | |
| Milani Fard et al. | Leveraging existing tests in automated test generation for web applications | |
| CN115952508A (en) | Test case test generation method, system, computer device and storage medium | |
| Mesbah et al. | Automated cross-browser compatibility testing | |
| Cortellessa et al. | A model-driven approach for continuous performance engineering in microservice-based systems | |
| Wu et al. | Combinatorial testing of restful apis | |
| Landman et al. | Empirical analysis of the relationship between CC and SLOC in a large corpus of Java methods and C functions | |
| US11436133B2 (en) | Comparable user interface object identifications | |
| Tonella et al. | Recent advances in web testing | |
| Felício et al. | Rapitest: Continuous black-box testing of restful web apis | |
| Li et al. | LogicScope: Automatic discovery of logic vulnerabilities within web applications | |
| Wang et al. | Using combinatorial testing to build navigation graphs for dynamic web applications | |
| Koçi et al. | A data-driven approach to measure the usability of web apis | |
| Sampath et al. | Composing a framework to automate testing of operational web-based software | |
| Jiang et al. | Assuring the model evolution of protocol software specifications by regression testing process improvement | |
| Aliero et al. | A component based SQL injection vulnerability detection tool | |
| Noseevich et al. | Detecting insufficient access control in web applications | |
| Li et al. | Automatically crawling dynamic web applications via proxy-based javascript injection and runtime analysis | |
| CN114117426B (en) | WEB application vulnerability detection method and system | |
| CN117009972A (en) | Vulnerability detection method, vulnerability detection device, computer equipment and storage medium | |
| Chen et al. | A Selenium-based Web Application Automation Test Framework | |
| Shen | A survey of access control misconfiguration detection techniques | |
| CN114003916A (en) | Method, system, terminal and storage medium for testing WEB role longitudinal override vulnerability | |
| Marchetto et al. | An empirical validation of a web fault taxonomy and its usage for web testing | |
| Ocariza Jr et al. | Localizing software performance regressions in web applications by comparing execution timelines |
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 |