CN110321278B - System testing method and device, computer equipment and storage medium - Google Patents
System testing method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN110321278B CN110321278B CN201910419762.8A CN201910419762A CN110321278B CN 110321278 B CN110321278 B CN 110321278B CN 201910419762 A CN201910419762 A CN 201910419762A CN 110321278 B CN110321278 B CN 110321278B
- Authority
- CN
- China
- Prior art keywords
- test
- background server
- test parameters
- end page
- parameters
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
Abstract
The application discloses a system testing method and device, and relates to the technical field of testing. The method comprises the following steps: when detecting that the currently executed test operation fails, acquiring test parameters executed by the test operation; sending the obtained test parameters to a background server, and executing the storage of the test parameters by the background server; when the test operation triggered in the front-end page is monitored, the test parameters stored in the background server are written back to the front-end page; and executing the test operation again according to the test parameters of the write back in the front-end page. The method disclosed by the application greatly improves the efficiency of testing the repaired system.
Description
Technical Field
The present disclosure relates to the field of testing technologies, and in particular, to a system testing method and apparatus, a computer device, and a computer-readable storage medium.
Background
After the program developer completes system development, in order to verify whether the functions of the developed system achieve the expected effect, a plurality of real users need to be simulated to input user information into the system respectively so as to perform system testing. If the system can not achieve the expected effect in the test process, program developers are required to carry out the system repair and then carry out the test again.
Because the user information input to the system by different users is different, for example, for drop-down box options in the system, the options selected by different users are different, and for text input boxes in the system, the information input by different users is different, a program developer needs to input a large amount of test data to the system when performing system test, and when performing retest on the repaired system, the program developer needs to input the test data to the system again, which is time-consuming, labor-consuming and seriously affects the development progress of the system.
Therefore, how to simplify the system testing process is a technical problem still to be solved at present.
Disclosure of Invention
Based on the above technical problem, the present application provides a system testing method and apparatus, a computer device, and a computer-readable storage medium.
The technical scheme disclosed by the application comprises the following steps:
a method of system testing, the method comprising: when detecting that the currently executed test operation fails, acquiring test parameters executed by the test operation; sending the obtained test parameters to a background server, and executing the storage of the test parameters by the background server; when the testing operation triggered to be carried out in the front-end page is monitored, the testing parameters stored in the background server are written back to the front-end page; and executing the test operation again according to the test parameters written back in the front-end page.
Further, when it is detected that the currently executed test operation fails, acquiring the test parameters executed by the test operation includes: when detecting that the currently executed test operation fails, traversing all controls in the front-end page; and collecting the test parameters input in each control.
Further, the sending the obtained test parameters to a background server, and the storing of the test parameters performed by the background server includes: and after receiving the test parameters, the background server stores the received test parameters in a temporary table or a cache of a database.
Further, when the test operation triggered to be performed in the front-end page is monitored, writing back the test parameters stored in the backend server to the front-end page includes: when monitoring that a local refresh button in the front-end page is triggered, initiating a test parameter acquisition request to the background service; and writing the test parameters returned by the background server according to the test parameter acquisition request into the front-end page.
Further, when it is monitored that the local refresh button in the front-end page is triggered, a test parameter acquisition request is initiated to the background service, including: when monitoring that a local refreshing button in the front-end page is triggered, creating a local refreshing object at the front end according to a method preset by the local refreshing button; establishing asynchronous communication connection with the background server through the created local refreshing object; and after the local refreshing object acquires the connection response of the background server, sending a test parameter acquisition request to the background server.
Further, the writing the test parameters returned by the background server according to the asynchronous request into the front-end page includes: after receiving the data in the specified format returned by the background server, analyzing the data to obtain the test parameters; and writing the test parameters into the corresponding HTML tags, and writing back the test parameters on the front-end page.
A system test apparatus, the apparatus comprising: the test parameter acquisition module is used for acquiring test parameters executed by the test operation when the test operation executed at present is detected to fail; the test parameter storage module is used for sending the obtained test parameters to a background server, and the background server stores the test parameters; the test parameter write-back module is used for writing back the test parameters stored in the background server to the front-end page when monitoring the test operation triggered in the front-end page; and the test execution module is used for executing the test operation again according to the test parameters written back in the front-end page.
A computer device, comprising:
a processor;
a memory having computer readable instructions stored thereon which, when executed by the processor, implement the system testing method as previously described.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the system testing method as set forth above.
The technical scheme provided by the embodiment of the application can have the following beneficial effects:
in the technical scheme, when the test operation executed by the system at present is failed, the test parameters executed by the current test operation are stored in the background server, and after the test operation triggered in the front-end page is monitored, the test parameters stored in the background server are written back to the front-end page, so that the system test is executed again according to the test parameters written back in the front-end page, the process that a program developer manually inputs the test parameters into the system is omitted, and the efficiency of testing the repaired system is greatly improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application;
FIG. 1 is a schematic illustration of an implementation environment to which the present application is directed;
FIG. 2 is a flow chart illustrating a method of system testing in accordance with an exemplary embodiment;
FIG. 3 is a flow chart in one embodiment according to step 130 of FIG. 2;
FIG. 4 is a flow chart in another embodiment according to step 130 of FIG. 2;
FIG. 5 is a block diagram illustrating a system test device in accordance with an exemplary embodiment;
FIG. 6 is a block diagram illustrating a hardware configuration of a computer device, according to an example embodiment.
While specific embodiments of the invention have been shown by way of example in the drawings and will be described in detail hereinafter, such drawings and description are not intended to limit the scope of the inventive concepts in any way, but rather to explain the inventive concepts to those skilled in the art by reference to the particular embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
Fig. 1 is a schematic diagram illustrating an implementation environment, which may be understood as a business system, according to an example embodiment. As shown in fig. 1, the implementation environment includes: a terminal 100 and a server 200.
The terminal 100 is configured to run a browser, and the browser is loaded with a front-end page to perform an interactive operation with a user. The terminal 100 may be a smart phone, a tablet computer, a notebook computer, a computer, or any other electronic device capable of running a browser, which is not limited herein.
The server 200 is configured to store mass data, so as to respond to a service request initiated by a terminal, and perform data processing according to the service request. The server 200 may be a server or a server cluster composed of several servers, which is not limited herein.
It should be noted that a wired or wireless network connection is pre-established between the terminal 100 and the server 200, so that the terminal 100 can perform data interaction with the server 200.
FIG. 2 is a flow chart illustrating a method of system testing according to an exemplary embodiment. As shown in fig. 1, the method may include the steps of:
It should be noted that the system described in this embodiment is applied to the implementation environment shown in fig. 1, which includes a front end and a back end. The front end is a user interactive interface running on the terminal and is used for providing a front end page to carry out interactive operation with a user; the back end is a background server and is used for providing data support for interactive operation performed by the front-end page.
The system testing method described in this embodiment is also applied to the implementation environment shown in fig. 1, and after the program developer completes system development, the program developer inputs testing parameters on the front-end page, so that the system runs according to the input testing parameters, thereby implementing system testing.
If the system cannot achieve the expected effect aiming at the operation of the test parameters input by the program developer, the currently executed test operation fails, and the program developer needs to correspondingly repair the system. After the system repair is completed, the program developer usually inputs the test parameters running before the system repair into the front-end page again to perform the system test again until the system achieves the expected effect on the running of the test parameters. That is, in the system test process, the program developer needs to input the same test parameters to the front-end page frequently, which is very troublesome.
In addition, when a program developer performs a system test, the program developer generally needs to simulate a plurality of users to input different test parameters to the system respectively so as to perform a comprehensive system test. During the system test of each simulated user, the program developer is required to execute the process of inputting the same test parameters to the front-end page frequently, which seriously affects the development progress of the system. Therefore, it is necessary to provide a system testing method to simplify the system testing operation in the existing implementation.
In the method provided by this embodiment, detecting that the test operation currently executed by the system fails means that the system fails to achieve the expected effect in the operation according to the test parameters input by the front-end page. For example, in a shopping system, the system cannot add items to the shopping cart of the currently simulated user, or the system cannot generate an order based on information selected by the currently simulated user.
The test parameters executed by the test operation refer to the test parameters input in the front-end page in the currently executed test operation by the system. Therefore, when the test operation currently executed by the system is detected to fail, the test parameters input in the front-end page are acquired.
In an exemplary embodiment, when it is detected that the test operation currently performed by the system fails, the test parameters performed by the test operation may be obtained by traversing all the controls in the front-end page and collecting the test parameters input in each control.
The controls in the front page may include common types of controls such as text controls, picture controls, button controls, check box controls, and progress bar controls. When the system executes the test operation, the control elements input the test parameters, so the test parameters input in the front-end page can be obtained by traversing all the control elements in the front-end page and collecting the test parameters input in each control element.
In another exemplary embodiment, by traversing all controls in the front page, the control type and ID information corresponding to each control are also obtained. The ID information of the control is set by the system for distinguishing different controls of the same type.
And step 120, sending the acquired test parameters to a background server, and executing the storage of the test parameters by the background server.
After the test parameters input in the front-end page are collected, the collected test parameters, the control type and the ID information corresponding to each control are sent to a background server to be stored.
In an exemplary embodiment, since the storage capacity of the database temporary table in the database configured by the background server is large and data modification and extraction are facilitated, the background server stores the test parameters in the database temporary table after receiving the test parameters.
The database configured by the background server may be a relational database, for example, an Oracle database, a MySQL database, or the like.
In another exemplary embodiment, since the efficiency of data reading from the cache of the background server is high, the background server stores the test parameters in the cache after receiving the test parameters.
Illustratively, if the background server adopts a MySQL database as a main database and a Redis database as an auxiliary cache database for data storage, the test parameters are stored in the Redis database. It should be noted that the backend server may also adopt other data storage forms, and this embodiment does not limit this to
In another exemplary embodiment, when the background server stores the test parameters, the background server stores the control types and the ID information corresponding to each control in association, so that when the background server reads the test parameters, the background server can read the corresponding control information at the same time.
For example, the test parameters are stored in a Redis database, and the test parameters corresponding to each control can be used as keys, and each control Value can be subjected to data storage. When the test parameters are read, the control type and the ID information of each control can be quickly inquired through the test parameters corresponding to each control.
And step 130, when the test operation triggered in the front-end page is monitored, writing back the test parameters stored in the background server to the front-end page.
The test operation triggered in the front-end page means that it is monitored that the local refresh button in the front-end page is triggered by a user.
The partial refresh button is one or more buttons disposed in the front-end page, and the manner in which the partial refresh button is triggered may include that a program developer clicks or touches the partial refresh button, for example, the program developer may click or double-click the partial refresh button with a mouse, or click or long-press the partial refresh button with a finger, which is not limited in this location.
When the program developer clicks the local refresh button, the system correspondingly monitors that the local refresh button in the front-end page is triggered, which indicates that the program developer has finished system repair and needs to use the test parameters input into the front-end page before system repair to execute the system test again. At this time, the test parameters stored in the background server need to be written back to the corresponding position in the front-end page, so that the test parameters executed before the system is modified are input into the front-end page again, and the complicated operation of manually inputting the test parameters by a program developer is omitted.
It should be noted that the partial refresh button is substantially different from the common types of controls in the aforementioned front-end page, such as text controls, picture controls, button control check box controls, progress bar controls, and the like. The control is used for bearing specific test parameters in system test operation, for example, when a program developer performs system test, the program developer inputs the test parameters into the system by clicking the control or inputting corresponding information into the control, and generally, each control corresponds to one test parameter respectively. However, the program developer only writes back the test parameters stored in the backend server to each control by triggering the local refresh button, and does not perform specific operations such as adding, modifying and the like on the test parameters in each control, so that the local refresh button is obviously different from the aforementioned controls.
For example, in order to distinguish the partial refresh button from the aforementioned control, the partial refresh button may be disposed at an edge portion in the front page, and the aforementioned control may be disposed at a middle region of the front page. Alternatively, the appearance of the partial refresh button may be specially designed, so that the partial refresh button is clearly distinguished from the aforementioned control, which is not limited herein.
In an exemplary embodiment, the partial refresh button set in the front page is an AJAX (asynchronous JavaScript and XML) button. AJAX is a web page development technique for creating interactive web page applications that can update data in portions of a web page without reloading the entire web page.
And when monitoring that the local refresh button in the front-end page is triggered, initiating a test parameter acquisition request to the background server to request the background server to return the stored test parameters to the front end, and writing the test parameters returned by the background server into a corresponding position in the front-end page by the front end.
As shown in fig. 3, in an exemplary embodiment, the process of initiating a test parameter obtaining request to a background server includes the following steps:
and step 131, creating a local refresh object at the front end according to a method preset by the local refresh button.
When the local refresh button is triggered, the method is started, and the local refresh object is created at the front end.
Illustratively, the partial refresh object created at the front end is an XMLHttpRequest object (hereinafter referred to as xhr object). Due to differences between different types of front ends (i.e., browsers), the method preset by each front end to create a partial refresh object may be different.
The differences between browsers are mainly reflected between IE browsers and other browsers. For non-IE browsers, the object may be created xhr directly on the browser; but for the IE browser, the property method of the microsoft.xmlhttp component needs to be called by the ActiveXObject object to create xhr objects on the browser.
And step 132, establishing asynchronous communication connection with the background server through the created partial refresh object.
The method for establishing asynchronous communication connection between the local refreshing object and the background server is realized by adopting an open method of xhr objects.
Illustratively, in the open method of the xhr object, the type of data submitted to the backend server is specified as post, and the url address and delivery parameters requested are specified, while the transport mode is specified as asynchronous.
After the asynchronous communication connection is established between the local refreshing object and the background server, the connection response returned by the background server is correspondingly received. And after receiving the connection response, the local refreshing object sends a test data acquisition request to the background server.
The local refreshing object sends a test data acquisition request to the background server, and the test data acquisition request is realized according to the send method of the xhr object. As described above, in the open method, the type of the data submitted to the background server by the local refresh object is post, and then, when the local refresh object sends a test data acquisition request to the background server, the local refresh object sends corresponding request data to the background server by the send method.
Therefore, the method provided by the exemplary embodiment can be used for initiating the test data acquisition request to the background server.
As shown in fig. 4, in an exemplary embodiment, the process of writing the test parameters returned by the background server into the front page may include the following steps:
and 135, after receiving the data in the specified format returned by the background server, analyzing the received data to obtain the test parameters.
After receiving the test parameter acquisition request, the background server responds to the request and returns the stored test parameters, the control type and the control ID information which are stored in association with the test parameters to the front end in a specified format.
For example, the format of the data returned by the backend server may be Javascript code or character string in json format, and may also be plain text stream in XML format or HTML format, which is not limited herein.
Through the analysis of the specified format data, the corresponding test parameters can be obtained, and the control type and the control ID information corresponding to each test parameter can be obtained at the same time. In an exemplary embodiment mode, the parsing of the data returned by the backend server is realized through a Javascript parser.
And 136, writing the test parameters into the corresponding HTML tags to write back the test parameters on the front-end page.
After the test parameters and the corresponding control information are obtained through analysis, HTML tags arranged in the front-end application program are searched according to the control types and the ID information, the test parameters are written into the corresponding HTML tags, and the write-back of the test parameters in the front-end page can be realized by reloading the HTML tags.
Therefore, after completing system repair, a program developer can write back the test parameters stored in the background server to the front-end page by touching a local refresh button in the front-end page according to the contents described in the embodiments corresponding to fig. 3 and fig. 4.
After the test parameters written back in the front-end page are identified, the system can execute the test operation again. If the test operation executed this time can not achieve the desired effect, the contents described in steps 110 to 140 are repeatedly executed until the test operation executed by the system achieves the desired effect.
In conclusion, the method provided by the application saves the process that program developers manually input the test parameters into the system, and greatly improves the efficiency of testing the repaired system.
FIG. 5 is a block diagram of a system test device, shown in accordance with an exemplary embodiment. As shown in fig. 5, the apparatus specifically includes:
a test parameter obtaining module 210, configured to obtain a test parameter executed by a test operation when it is detected that a currently executed test operation fails;
the test parameter storage module 220 is configured to send the obtained test parameters to the background server, and the background server stores the test parameters;
the test parameter write-back module 230 is configured to write back the test parameters stored in the background server to the front-end page when monitoring a test operation triggered in the front-end page;
and the test execution module 240 is configured to execute the test operation again according to the test parameter written back in the front-end page.
In another exemplary embodiment, the test parameter acquisition module 210 includes:
the control traversing unit is used for traversing all controls in the front-end page when detecting that the currently executed test operation fails;
and the test parameter acquisition unit is used for acquiring the test parameters input in each control.
In another exemplary embodiment, the test parameter write back module 230 includes:
the control triggering and monitoring unit is used for initiating a test parameter acquisition request to a background service when monitoring that a local refreshing button in the front-end page is triggered;
and the test parameter writing unit is used for writing the test parameters returned by the background server according to the test parameter acquisition request into the front-end page.
In another exemplary embodiment, the control triggering listening unit includes:
the object creating subunit is used for creating a local refreshing object at the front end according to a method preset by the local refreshing button when the local refreshing button in the front-end page is monitored to be triggered;
the asynchronous communication connection subunit is used for establishing asynchronous communication connection with the background server through the created local refreshing object;
and the request sending subunit is used for sending a test parameter obtaining request to the background server after the local refreshing object obtains the connection response of the background server.
In another exemplary embodiment, the test parameter writing unit includes:
the data analysis subunit is used for obtaining the test parameters through the analysis of the data after receiving the data in the specified format returned by the background server;
and the tag information writing subunit is used for writing the test parameters into the corresponding HTML tags to write back the test parameters on the front-end page.
It should be noted that the apparatus provided in the foregoing embodiment and the method provided in the foregoing embodiment belong to the same concept, and the specific manner in which each module performs operations has been described in detail in the method embodiment, and is not described again here.
In an exemplary embodiment, the present application further provides a computer device comprising:
a processor;
a memory having stored thereon computer readable instructions which, when executed by the processor, implement the method as set forth above.
FIG. 6 is a block diagram illustrating a hardware configuration of a computer device, according to an example embodiment. As shown in fig. 6, the computer device may include one or more of the following components: a processing component 401, a memory 402, a power component 403, a multimedia component 404, an audio component 405, a sensor component 407, and a communication component 408.
The above components are not all necessary, and the computer device may add other components or reduce some components according to its own functional requirements, which is not limited in this embodiment.
The processing component 401 generally controls overall operation of the computer device, such as operations associated with display, data communication, camera operation, and log data processing. The processing components 401 may include one or more processors 409 to execute instructions to perform all or a portion of the above-described operations. Further, processing component 401 may include one or more modules that facilitate interaction between processing component 401 and other components. For example, the processing component 401 may include a multimedia module to facilitate interaction between the multimedia component 404 and the processing component 401.
The memory 402 is configured to store various types of data to support operations at the terminal. Examples of such data include instructions for any application or method operating on a computer device. The memory 402 may be implemented by any type or combination of volatile or non-volatile memory devices, such as SRAM (static random access memory), EEPROM (electrically erasable programmable read only memory), EPROM (erasable programmable read only memory), PROM (programmable read only memory), ROM (read only memory), and the like. Also stored in the memory 402 are one or more modules configured to be executed by the one or more processors 409 to perform all or part of the steps of the system testing method described in the embodiments above.
The power supply component 403 provides power to the various components of the terminal. The power components 403 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for a computer device.
The multimedia component 404 includes a screen providing an output interface between the computer device and the user. In some embodiments, the screen may include an LCD (liquid crystal display) and a TP (touch panel). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.
The audio component 405 is configured to output and/or input audio signals. For example, the audio component 405 may include a microphone configured to receive external audio signals when the terminal is in an operational mode, such as a recording mode and a voice recognition mode. The received audio signal may further be stored in the memory 402 or transmitted via the communication component 408. The audio component 405 also includes a speaker for outputting audio signals to enable conversational operation between the computer device and the user.
The sensor component 407 includes one or more sensors for providing various aspects of status assessment for the computer device. For example, the sensor assembly 407 may detect an open/close state of the terminal, as well as a temperature change of the terminal. In some embodiments, the sensor assembly 407 may also include a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 408 is configured to facilitate wired or wireless communication between the computer device and other devices. The terminal may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 408 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel.
In an exemplary embodiment, the processor may be implemented by one or more ASICs (application specific integrated circuits), DSPs (digital signal processors), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), controllers, micro-controllers, microprocessors or other electronic components for performing the system test method described in detail in the above embodiments, which will not be described in detail herein.
In an exemplary embodiment, the present application further provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method as set forth above.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (7)
1. A method of system testing, the method comprising:
when detecting that the currently executed test operation fails, acquiring test parameters executed by the test operation;
sending the acquired test parameters to a background server, and storing the received test parameters in a temporary table or a cache of a database after the background server receives the test parameters;
when a local refresh button in a front-end page is monitored to be triggered, a local refresh object is created at the front end according to a method preset by the local refresh button;
establishing asynchronous communication connection with the background server through the local refreshing object;
after the local refreshing object acquires the connection response of the background server, sending a test parameter acquisition request to the background server;
writing the test parameters returned by the background server according to the test parameter acquisition request into the front-end page;
and executing the test operation again according to the test parameters written back in the front-end page.
2. The method of claim 1, wherein the obtaining test parameters executed by the test operation when the failure of the currently executed test operation is detected comprises:
when detecting that the currently executed test operation fails, traversing all controls in the front-end page;
and collecting the test parameters input in each control.
3. The method according to claim 1, wherein writing the test parameters returned by the background server according to the test parameter obtaining request into the front-end page comprises:
after receiving the data in the specified format returned by the background server, analyzing the data to obtain the test parameters;
and writing the test parameters into the corresponding HTML tags, and writing back the test parameters on the front-end page.
4. A system test apparatus, the apparatus comprising:
the test parameter acquisition module is used for acquiring test parameters executed by the test operation when the test operation executed at present is detected to fail;
the test parameter storage module is used for sending the obtained test parameters to a background server, and after receiving the test parameters, the background server stores the received test parameters in a temporary table or a cache of a database;
the test parameter write-back module is used for creating a local refresh object at the front end according to a method preset by a local refresh button when the fact that the local refresh button in the front-end page is triggered is monitored; establishing asynchronous communication connection with the background server through the local refreshing object; after the local refreshing object acquires the connection response of the background server, sending a test parameter acquisition request to the background server; writing the test parameters returned by the background server according to the test parameter acquisition request into the front-end page;
and the test execution module is used for executing the test operation again according to the test parameters written back in the front-end page.
5. The apparatus of claim 4, wherein the test parameter obtaining module comprises:
the control traversing unit is used for traversing all controls in the front-end page when detecting that the currently executed test operation fails;
and the test parameter acquisition unit is used for acquiring the test parameters input in each control.
6. A computer device, the device comprising:
a processor;
a memory having stored thereon computer readable instructions which, when executed by the processor, implement the method of any of claims 1 to 3.
7. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 3.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910419762.8A CN110321278B (en) | 2019-05-20 | 2019-05-20 | System testing method and device, computer equipment and storage medium |
| PCT/CN2019/103443 WO2020232900A1 (en) | 2019-05-20 | 2019-08-29 | System test method and apparatus, computer device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910419762.8A CN110321278B (en) | 2019-05-20 | 2019-05-20 | System testing method and device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110321278A CN110321278A (en) | 2019-10-11 |
| CN110321278B true CN110321278B (en) | 2022-09-13 |
Family
ID=68113161
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910419762.8A Active CN110321278B (en) | 2019-05-20 | 2019-05-20 | System testing method and device, computer equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110321278B (en) |
| WO (1) | WO2020232900A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110321278B (en) * | 2019-05-20 | 2022-09-13 | 平安科技（深圳）有限公司 | System testing method and device, computer equipment and storage medium |
| CN112685286A (en) * | 2019-10-18 | 2021-04-20 | 拉扎斯网络科技（上海）有限公司 | Test object generation method and device, electronic equipment and computer storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105808417A (en) * | 2014-12-29 | 2016-07-27 | 平安科技（深圳）有限公司 | Automated testing method and proxy server |
| CN109144856A (en) * | 2018-07-27 | 2019-01-04 | 北京皮尔布莱尼软件有限公司 | A kind of UI automated testing method calculates equipment and storage medium |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020147561A1 (en) * | 2001-04-09 | 2002-10-10 | William Baracat | System and method for intelligent wire testing |
| CN101487769B (en) * | 2008-01-18 | 2011-10-26 | 中兴通讯股份有限公司 | Automatic test system and method |
| CN104899149B (en) * | 2015-06-29 | 2017-12-19 | 上海瀚银信息技术有限公司 | A kind of automatic test management method |
| US9846633B2 (en) * | 2015-10-06 | 2017-12-19 | Ca, Inc. | Generating tests for testing software applications |
| CN107861864A (en) * | 2017-08-25 | 2018-03-30 | 平安普惠企业管理有限公司 | Automated testing method, system and computer-readable recording medium |
| CN107832206A (en) * | 2017-10-16 | 2018-03-23 | 深圳市牛鼎丰科技有限公司 | Method of testing, device, computer-readable recording medium and computer equipment |
| CN110321278B (en) * | 2019-05-20 | 2022-09-13 | 平安科技（深圳）有限公司 | System testing method and device, computer equipment and storage medium |
-
2019
- 2019-05-20 CN CN201910419762.8A patent/CN110321278B/en active Active
- 2019-08-29 WO PCT/CN2019/103443 patent/WO2020232900A1/en active Application Filing
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105808417A (en) * | 2014-12-29 | 2016-07-27 | 平安科技（深圳）有限公司 | Automated testing method and proxy server |
| CN109144856A (en) * | 2018-07-27 | 2019-01-04 | 北京皮尔布莱尼软件有限公司 | A kind of UI automated testing method calculates equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110321278A (en) | 2019-10-11 |
| WO2020232900A1 (en) | 2020-11-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103810089B (en) | Automatically testing gesture-based applications | |
| US11838350B2 (en) | Techniques for identifying issues related to digital interactions on websites | |
| WO2018223717A1 (en) | Webpage front-end testing method, device, system, apparatus and readable storage medium | |
| US8533532B2 (en) | System identifying and inferring web session events | |
| WO2015039566A1 (en) | Method and system for facilitating automated web page testing | |
| WO2018184361A1 (en) | Application test method, server, terminal, and storage media | |
| US20200050540A1 (en) | Interactive automation test | |
| CN108111364B (en) | Service system testing method and device | |
| US20170168913A9 (en) | Method and system for testing of applications in asset management software | |
| US20120254662A1 (en) | Automated test system and automated test method | |
| CN110321278B (en) | System testing method and device, computer equipment and storage medium | |
| WO2015043352A1 (en) | Method and apparatus for selecting test nodes on webpages | |
| CN110532159A (en) | Data decryptor method, apparatus, equipment and computer readable storage medium | |
| US10452723B2 (en) | Detecting malformed application screens | |
| CN109885793A (en) | Page data acquisition method and device, electronic equipment, storage medium | |
| CN108229980B (en) | Question feedback method and device and storage medium | |
| CN104156305A (en) | Application program testing method and device | |
| US9104573B1 (en) | Providing relevant diagnostic information using ontology rules | |
| US20130326466A1 (en) | Human Readable Software Program Test Step | |
| CN103136273A (en) | Method and device for displaying user information in webpage | |
| CN106959867A (en) | Method and system for monitoring application program unloading | |
| CN111381862B (en) | Multi-scene data adaptive display method and device, electronic equipment and storage medium | |
| US9009659B2 (en) | Method and system for displaying context-based completion values in an integrated development environment for asset management software | |
| CN111367898A (en) | Data processing method, device, system, electronic equipment and storage medium | |
| CN112306838A (en) | Page layout compatibility testing method, device and equipment and readable 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 |