CN113535590A - Program testing method and device - Google Patents

Program testing method and device Download PDF

Info

Publication number
CN113535590A
CN113535590A CN202110965088.0A CN202110965088A CN113535590A CN 113535590 A CN113535590 A CN 113535590A CN 202110965088 A CN202110965088 A CN 202110965088A CN 113535590 A CN113535590 A CN 113535590A
Authority
CN
China
Prior art keywords
execution machine
execution
machine
sub
registry
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
Application number
CN202110965088.0A
Other languages
Chinese (zh)
Inventor
张强
马超
李敏
朱文洁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Wodong Tianjun Information Technology Co Ltd
Original Assignee
Beijing Wodong Tianjun Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Wodong Tianjun Information Technology Co Ltd filed Critical Beijing Wodong Tianjun Information Technology Co Ltd
Priority to CN202110965088.0A priority Critical patent/CN113535590A/en
Publication of CN113535590A publication Critical patent/CN113535590A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3684Test management for test design, e.g. generating new test cases
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Abstract

The present disclosure provides a program testing method, including: determining at least one first execution machine which is in communication connection with the main control equipment; determining at least one second execution machine connected with the terminal equipment in the at least one first execution machine; and sending the test script to each execution machine in the at least one second execution machine, so that each execution machine tests the application program running on the terminal equipment connected with the execution machine by running the received test script. The present disclosure also provides a program testing apparatus, an electronic device, and a computer-readable storage medium.

Description

Program testing method and device
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a program testing method and apparatus.
Background
In the development cycle of products, program testing is an indispensable part. With the continuous popularization of agility testing, a business party puts new requirements on the delivery and iteration period of software products. However, since the developed product is oriented to both the brand side of the B-side (i.e., management platform) and the user of the C-side (i.e., consumer, personal user side), how to quickly adapt the system of the brand side to the mass browser in the market and the mainstream model of the user of the C-side becomes a challenge.
In the course of implementing the inventive concept of the present disclosure, the inventors found that at least the following problems exist in the related art:
in the related art, the testing efficiency of the program test is not high.
Disclosure of Invention
One aspect of the present disclosure provides a program testing method, including: determining at least one first execution machine which is in communication connection with the main control equipment; determining at least one second execution machine connected with the terminal equipment in the at least one first execution machine; and sending the test script to each execution machine in the at least one second execution machine, so that each execution machine tests the application program running on the terminal equipment connected with the execution machine by running the received test script.
Optionally, determining at least one second execution machine connected with the terminal device in the at least one first execution machine includes: querying a registry on each first execution machine in the at least one first execution machine to obtain at least one corresponding query result, wherein each query result corresponds to one first execution machine; and determining the at least one second execution machine connected with the terminal equipment in the at least one first execution machine based on the at least one query result.
Optionally, determining, based on the at least one query result, the at least one second execution machine connected to the terminal device in the at least one first execution machine includes: and aiming at each query result, responding to the version information related to the terminal equipment in the current query result representation registry, determining that the first execution machine corresponding to the current query result is connected with the terminal equipment, and taking the first execution machine as a second execution machine.
Optionally, the sending the test script to each of the at least one second execution machine includes one of: respectively sending the whole test script to each execution machine in the at least one second execution machine; the whole test script is divided into a plurality of sub scripts, and then the plurality of sub scripts are distributed to corresponding execution machines in the at least one second execution machine according to a preset rule.
Optionally, the distributing the plurality of sub-scripts to corresponding execution machines in the at least one second execution machine according to a preset rule includes at least one of: when the number of the sub scripts is smaller than the number of the second execution machines, each sub script in the plurality of sub scripts is randomly sent to one second execution machine in the at least one second execution machine, so that different sub scripts run on different second execution machines; and under the condition that the number of the sub scripts is greater than or equal to the number of the second execution machines and the number of the sub scripts is integral multiple of the number of the second execution machines, distributing the plurality of sub scripts to each of the at least one second execution machine in an average manner.
Optionally, the application program includes a program for implementing a UI interface.
Optionally, the program testing method further includes: and for each execution machine in the at least one second execution machine, responding to the successful completion of the program test of the current execution machine, and acquiring and displaying a test result returned by the current execution machine.
Another aspect of the present disclosure provides a processing method for an execution machine, including: generating a registry; storing the registry on an execution machine; and responding to the fact that the terminal equipment is connected with the execution machine, recording version information of the terminal equipment in the registry, so that the main control equipment which is in communication connection with the execution machine can determine whether the terminal equipment is connected with the execution machine or not based on the information recorded in the registry.
Optionally, the program testing apparatus further includes: and deleting the version information of the terminal equipment disconnected with the executive machine in the registry in response to the disconnection of the terminal equipment from the executive machine.
Another aspect of the present disclosure provides a program testing apparatus including: the method comprises the steps of determining a first execution machine module, wherein the first execution machine module is used for determining at least one first execution machine which is in communication connection with a main control device; a second execution machine determining module, configured to determine at least one second execution machine connected to the terminal device in the at least one first execution machine; and the test script sending module is used for sending the test script to each execution machine in the at least one second execution machine, so that each execution machine tests the application program running on the terminal equipment connected with the execution machine by running the received test script.
Optionally, the determining the second execution engine module includes: the query submodule is used for querying the registry on each first execution machine in the at least one first execution machine to obtain at least one corresponding query result, wherein each query result corresponds to one first execution machine; and a second execution machine determining submodule, configured to determine, based on the at least one query result, the at least one second execution machine connected to the terminal device in the at least one first execution machine.
Optionally, the determining the second execution engine submodule includes: and aiming at each query result, responding to the version information related to the terminal equipment in the current query result representation registry, determining that the first execution machine corresponding to the current query result is connected with the terminal equipment, and taking the first execution machine as a second execution machine.
Optionally, the test script sending module includes one of: the script sending submodule is used for respectively sending the whole test script to each execution machine in the at least one second execution machine; and the script distribution submodule is used for dividing the whole test script into a plurality of sub-scripts and distributing the plurality of sub-scripts to corresponding execution machines in the at least one second execution machine according to a preset rule.
Optionally, the script distribution sub-module includes at least one of: a first distributing unit, configured to randomly send each of the plurality of sub-scripts to one of the at least one second execution machine when the number of the sub-scripts is smaller than the number of the second execution machines, so that different sub-scripts run on different second execution machines; and a second distribution unit which distributes the plurality of sub-scripts to each of the at least one second execution machine in an average manner when the number of the sub-scripts is equal to or greater than the number of the second execution machines and the number of the sub-scripts is an integral multiple of the number of the second execution machines.
Optionally, the application program includes a program for implementing a UI interface.
Optionally, the program testing method further includes: and the result display unit is used for responding to the successful completion of the program test of the current execution machine by each execution machine in the at least one second execution machine, and acquiring and displaying the test result returned by the current execution machine.
Another aspect of the disclosure provides a processing apparatus for an execution machine, comprising: the registry generation module is used for generating a registry; the storage module is used for storing the registry on an execution machine; and a first response module, configured to record version information about the terminal device in the registry in response to that the terminal device is connected to the execution machine, so that a main control device in communication connection with the execution machine can determine whether the terminal device is connected to the execution machine based on the information recorded in the registry.
Optionally, the program testing apparatus further includes: and the second response module is used for responding to the disconnection between the terminal equipment and the executive machine and deleting the version information of the terminal equipment disconnected with the executive machine in the registry.
Another aspect of the present disclosure provides an electronic device including: one or more processors; a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method as described above.
Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the method as described above when executed.
Another aspect of the present disclosure provides a computer program comprising computer executable instructions for implementing the method as described above when executed.
Drawings
For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
FIG. 1 schematically illustrates a system architecture suitable for program testing methods and apparatus according to an embodiment of the present disclosure;
FIG. 2 schematically shows a flow chart of a program testing method according to an embodiment of the present disclosure;
FIG. 3 schematically illustrates a flow chart of a program testing method according to another embodiment of the present disclosure;
FIG. 4 schematically illustrates a flow diagram for determining a second execution engine based on query results according to another embodiment of the disclosure;
FIG. 5 schematically illustrates a flow chart of a program testing method according to another embodiment of the present disclosure;
FIG. 6 schematically shows a flow chart of a program test method according to yet another embodiment of the present disclosure;
FIG. 7 schematically illustrates a flow chart of a processing method for an execution engine according to an embodiment of the present disclosure;
FIG. 8 schematically shows a block diagram of a program test device according to an embodiment of the present disclosure;
FIG. 9 schematically illustrates a block diagram of determining a second execution engine module, in accordance with an embodiment of the present disclosure;
FIG. 10 schematically illustrates a block diagram of a send test script module, according to an embodiment of the present disclosure;
FIG. 11 schematically illustrates a block diagram of another send test script module, in accordance with an embodiment of the present disclosure;
FIG. 12 schematically illustrates a block diagram of a script distribution submodule, according to an embodiment of the present disclosure;
FIG. 13 schematically shows a block diagram of a program test apparatus according to another embodiment of the present disclosure;
figure 14 schematically shows a block diagram of a processing device for an execution machine according to an embodiment of the present disclosure;
figure 15 schematically shows a block diagram of a processing device for an execution machine according to another embodiment of the present disclosure; and
fig. 16 schematically shows a block diagram of an electronic device adapted to implement the above described method according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.
Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). In addition, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system.
Embodiments of the present disclosure provide a program testing method and a program testing apparatus capable of applying the method. The method comprises the following steps: determining at least one first execution machine which is in communication connection with the main control equipment; determining at least one second execution machine connected with the terminal equipment in the at least one first execution machine; and sending the test script to each execution machine in the at least one second execution machine, so that each execution machine tests the application program running on the terminal equipment connected with the execution machine by running the received test script.
Fig. 1 schematically illustrates a system architecture suitable for a program testing method and apparatus according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, the system architecture 100 includes: terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired and/or wireless communication links, and so forth.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have installed thereon various communication client applications, such as a shopping-like application, a web browser application, a search-like application, an instant messaging tool, a mailbox client, and/or social platform software, etc. (by way of example only).
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites browsed by users using the terminal devices 101, 102, 103. The background management server may analyze and perform other processing on the received data such as the user request, and feed back a processing result (e.g., a webpage, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the program testing method provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the program testing device provided by the embodiment of the present disclosure may be generally disposed in the server 105. The program testing method provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the program testing system provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Alternatively, the program testing method provided by the embodiment of the present disclosure may also be executed by the terminal device 101, 102, or 103, or may also be executed by another terminal device different from the terminal device 101, 102, or 103. Accordingly, the program testing apparatus provided in the embodiments of the present disclosure may also be disposed in the terminal device 101, 102, or 103, or in another terminal device different from the terminal device 101, 102, or 103.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
FIG. 2 schematically shows a flow chart of a program testing method according to an embodiment of the present disclosure.
As shown in fig. 2, the method includes operations S210 to S230.
In operation S210, at least one first execution machine that has a communication connection with a master device is determined.
In this operation, the main control device may add one or more first execution machines, and each time the addition is completed, the main control device may establish a corresponding communication connection with the first execution machine.
The master control device can check the connection condition of each first execution machine and the master control device. If the main control device does not check a certain first execution machine, the main control device is characterized to fail to add the first execution machine. If the master control device cannot check the connection condition of a certain first execution machine and the master control device, the fact that the first execution machine and the master control device are not successfully established is represented, or the communication connection between the first execution machine and the master control device is interrupted.
If the addition of the first execution machine by the master control device fails, the operation of adding the first execution machine by the master control device can be repeatedly executed until the first execution machine is successfully added by the master control device.
In operation S220, at least one second execution machine to which the terminal device is connected among the at least one first execution machine is determined.
In this operation, each first execution machine in operation S210 may be bound with the terminal device, and after the binding is completed, the terminal device may establish a connection with the first execution machine.
Each first execution machine can display the connection state of the terminal equipment. If a first execution machine displays that the connected terminal equipment is successfully connected, the first execution machine can be determined to be one of the second execution machines.
The number of the first execution machines which are in communication connection with the main control device can be multiple. Accordingly, the number of first execution machines that are successfully connected to the terminal device may be multiple, and accordingly, the number of second execution machines that can be determined may be multiple.
In operation S230, the test script is transmitted to each of the at least one second execution machine, so that each execution machine tests the application program running on the terminal device connected to itself by running the received test script.
In this operation, a test script is sent to each of the plurality of second execution machines in operation S220. And after receiving the test script, each second execution machine runs the test script and tests the application program running on the terminal equipment connected with the second execution machine.
For example, each second execution machine may test the function of an application program running on the terminal device connected to the second execution machine, test the running condition of each function of the application program, and display the test result.
For example, each second execution machine may test a UI (User Interface, abbreviated as User Interface) running on a browser of the terminal device connected to the second execution machine, test each functional button on the UI, test whether operation and interaction of each button meet expected requirements, and display a test result.
It can be understood that, according to the program testing method provided by the embodiment of the present disclosure, at least one first execution machine in communication connection with the main control device is determined, at least one second execution machine in the at least one first execution machine, to which the terminal device is connected, is determined, and a test script is sent to each execution machine in the at least one second execution machine, so that each execution machine tests an application program running on the terminal device connected to the execution machine by running the received test script.
According to the program testing method provided by the embodiment of the disclosure, the main control device is added with the first execution machine, the first execution machine is connected with the first execution machine, the second execution machine connected with the terminal device is confirmed, and the main control device can dynamically discover the terminal device and check the connection state of the terminal device in real time. If the connection between the terminal equipment and the second execution machine is interrupted, the running interruption of the script can be known in real time, and the failed script can be run again in real time, so that the efficiency of the program test is improved. And testing the application program running on the terminal equipment connected with the second execution machine through the second execution machine, generating a test report of the application program, and returning the test report to the main control equipment for displaying.
FIG. 3 schematically shows a flow chart of a program testing method according to another embodiment of the present disclosure.
As shown in fig. 3, the method includes operations S210, S310 to S320, and S230.
In operation S210, at least one first execution machine that has a communication connection with a master device is determined.
This operation is the same as operation S210 shown in fig. 2, and is not described again here.
In operation S310, a registry on each of the at least one first execution machine is queried to obtain at least one query result, where each query result corresponds to one first execution machine.
In this operation, the main control device queries the registry on each first execution machine to obtain the query result on each corresponding first execution machine, so as to determine the connection condition between the terminal device and the first execution machine.
For example, when testing the UI running on the browser of the terminal device, the main control device may query the registry on each first execution machine to obtain a query result on each corresponding first execution machine, thereby determining the connection condition between the terminal device and the first execution machine.
In operation S320, at least one second execution machine connected with the terminal device among the at least one first execution machine is determined based on the at least one query result.
In this operation, based on the query result obtained by the main control device in operation S310 on each first execution machine, it is determined whether each first execution machine is connected to the terminal device, and a plurality of second execution machines are determined.
In operation S230, the test script is transmitted to each of the at least one second execution machine, so that each execution machine tests the application program running on the terminal device connected to itself by running the received test script.
This operation is the same as operation S230 shown in fig. 2, and is not described again here.
According to the program testing method of the embodiment of the disclosure, the main control device queries the registry on each first execution machine to obtain the query result on each corresponding first execution machine, so as to judge the connection condition between the terminal device and the first execution machine, and determine the plurality of second execution machines based on the connection condition.
According to the program testing method of the embodiment of the disclosure, the main control device adds the plurality of first execution machines, judges whether the addition of the plurality of first execution machines is successful, and if the addition is successful, the main control device traverses the registry on each first execution machine in a circulating manner, checks the connection state of each terminal device and the execution machine, and determines the second execution machine, thereby binding the terminal device and the second execution machine.
For example, multiple first execution machines may be added by jenkins. It should be appreciated that Jenkins is an open-source, continuously integrated tool that provides a friendly operating interface, primarily for continuously, automatically building or testing software projects to detect the execution of external tasks.
After the main control device binds the terminal device and the second execution machines, traversing all the second execution machines, judging whether each second execution machine is connected with the main control device, if the second execution machine is connected with the main control device, traversing the registry of each second execution machine by the main control device, judging whether the terminal device is connected with the second execution machine, and displaying the connection state of the terminal device.
According to the program testing method of the embodiment of the disclosure, the main control device checks the connection state of each terminal device and the execution machine by adding the plurality of first execution machines, determines the second execution machine, and queries the registry on each second execution machine, so that the terminal device can be dynamically discovered, the connection state of each terminal device and the execution machine can be checked in real time, and whether the program test of the terminal device is interrupted or not can be judged in real time.
FIG. 4 schematically shows a flow diagram for determining a second execution engine based on query results according to another embodiment of the present disclosure.
As shown in fig. 4, the determining, in operation S320, at least one second execution machine to which the terminal device is connected among the at least one first execution machine based on the at least one query result may include operations S321 to S323.
In operation S321, for each query result, version information about the terminal device in the registry is characterized in response to the current query result.
In operation S322, it is determined, for each query result, that a terminal device is connected to the first execution machine corresponding to the current query result.
In operation S323, the first execution engine is treated as a second execution engine for each query result.
According to the program testing method of the embodiment of the disclosure, the registry on each first execution machine contains much information. For example, version information of the terminal device. For example, browser version information that the terminal device runs. The main control device may obtain version information related to the terminal device by querying the registry on each first execution machine, and determine the connection condition between the terminal device and the first execution machine in response to the version information related to the terminal device in the query result.
It should be understood that, in the related art, before the program is tested, the configuration file needs to be modified manually so that the test script is adapted to the terminal device. According to the program testing method of the embodiment of the disclosure, the main control device obtains the version information related to the terminal device by querying the registry on each first execution machine, and the manual operation of modifying the configuration file can be replaced by using the version information. Therefore, when the subsequent program test is carried out on the terminal equipment, the configuration file in the test script does not need to be manually modified before each test, the connection between the main control equipment and the first execution machine is established, the connection between the second execution machine and the terminal equipment is established, the main control equipment can dynamically discover the terminal equipment and check the connection state of the terminal equipment in real time, so that the automatic program test can be realized, the program test efficiency is improved, and the program test convenience is also improved.
For example, when testing the UI running on the browser of the terminal device, the main control device may query the registry on each first execution machine to obtain the browser version information related to the UI running test on the terminal device, thereby determining the connection condition between the terminal device and the first execution machine.
According to the program testing method of the embodiment of the disclosure, the query result about the version information of the terminal device in the registry on each first execution machine obtained by the main control device can determine that each first execution machine connected with the terminal device is the second execution machine.
It can be understood that, according to the program testing method of the embodiment of the present disclosure, the main control device may obtain version information related to the terminal device by querying the registry on each first execution machine, and may determine, in response to the version information related to the terminal device in the query result, a connection condition between the terminal device and the first execution machine, and may determine that each first execution machine connected with the terminal device is the second execution machine.
According to the program testing method of the embodiment of the disclosure, based on the version information about the terminal device in the registry on each first execution machine, whether the terminal device is connected with the execution machine or not can be judged, so that whether the program testing on the terminal device is interrupted or not can be judged.
According to the program testing method of the embodiment of the disclosure, sending the test script to each of the at least one second execution machine may include one of: respectively sending the whole test script to each execution machine in at least one second execution machine; the whole test script is divided into a plurality of sub scripts, and then the plurality of sub scripts are distributed to corresponding execution machines in at least one second execution machine according to preset rules.
According to the program testing method of the embodiment of the disclosure, the main control device may send the entire test script to each of the plurality of second execution machines, respectively.
According to the program testing method of the embodiment of the present disclosure, the main control device may also divide the whole test script into a plurality of sub-scripts, and then distribute the plurality of sub-scripts to corresponding execution machines in the plurality of second execution machines according to a preset rule.
According to the program testing method of the embodiment of the disclosure, the main control device may send the whole test script to each of the execution machines, or may divide the whole test script into a plurality of sub-scripts first, and then distribute the plurality of sub-scripts to corresponding execution machines in the plurality of second execution machines according to a preset rule, and the execution machines may run the whole script or the sub-scripts, so that the running condition of the script may be known in detail.
FIG. 5 schematically shows a flow chart of a program testing method according to another embodiment of the present disclosure.
As shown in fig. 5, the method includes operations S210 to S220, S510 to S560.
In operation S210, at least one first execution machine that has a communication connection with a master device is determined.
This operation is the same as operation S210 shown in fig. 2, and is not described again here.
In operation S220, at least one second execution machine to which the terminal device is connected among the at least one first execution machine is determined.
This operation is the same as operation S220 shown in fig. 2, and is not described again here.
In operation S510, the entire test script is divided into a plurality of sub-scripts.
In the operation, the whole test script is divided into a plurality of sub-scripts, for example, the script can be divided according to tabs or drawers, so that the subsequent automatic program test on the terminal equipment is facilitated.
In operation S520, it is determined whether the number of the sub-scripts is less than the number of the second execution machines, and if so, the following operation S540 is performed. If not, the subsequent operation S530 is performed.
In the present operation, it is determined whether the number of the plurality of sub-scripts obtained in operation S510 is smaller than the number of the second execution machines.
In operation S530, it is determined whether the number of the sub-scripts is greater than or equal to the second number of execution machines and the number of the sub-scripts is an integer multiple of the second number of execution machines, and if so, a subsequent operation S550 is performed.
In this operation, when the number of the plurality of sub-scripts obtained in operation S510 is not less than the second number of execution machines, it is determined whether the number of the plurality of sub-scripts obtained in operation S510 is greater than or equal to the second number of execution machines and the number of the sub-scripts is an integer multiple of the second number of execution machines.
In operation S540, in the case that the number of the sub-scripts is less than the number of the second execution machines, each of the plurality of sub-scripts is randomly transmitted to one of the at least one second execution machine, so that different sub-scripts run on different second execution machines.
In this operation, in the case where the number of the plurality of sub-scripts obtained in operation S510 is smaller than the number of the second execution machines, each of the plurality of sub-scripts is randomly transmitted to one of the at least one second execution machine, so that different second execution machines execute different sub-scripts and some second execution machines may not execute scripts.
In operation S550, in the case that the number of the sub-scripts is equal to or greater than the number of the second execution machines and the number of the sub-scripts is an integer multiple of the number of the second execution machines, the plurality of sub-scripts are equally distributed to each of the at least one second execution machine.
In this operation, in the case where the number of the plurality of sub-scripts obtained in operation S510 is greater than or equal to the number of the second execution machines and the number of the sub-scripts is an integer multiple of the number of the second execution machines, the plurality of sub-scripts are equally distributed to each of the at least one second execution machine, so that different second execution machines execute different sub-scripts and the number of scripts executed by each second execution machine is the same.
In operation S560, each execution machine tests an application program running on the terminal device connected to itself by running the received test script.
According to the program testing method of the embodiment of the disclosure, the scripts are distributed according to the number of the sub-scripts and the number of the second execution machines, so that the plurality of second execution machines execute different sub-scripts concurrently. Once the connection between the terminal device and the corresponding second execution machine is disconnected, the execution of the sub-scripts is stopped, and which terminal devices successfully test which sub-scripts and which terminal devices fail to test which sub-scripts can be known.
It should be understood that, in the related art, in the program test, the whole script is executed on a plurality of execution machines concurrently, once a certain terminal device is disconnected from the execution machines, the test of the terminal device is stopped, but the whole program test is not stopped, thereby causing a waste of time.
According to the program testing method of the embodiment of the disclosure, when a connection between a certain terminal device and a corresponding second execution machine is disconnected, the second execution machine stops executing the sub-script. Since the whole script is divided into a plurality of sub scripts, even if the connection between the terminal device and the corresponding second execution machine is disconnected, which terminal devices fail in testing which sub scripts can be known. The failed sub-scripts can be retested subsequently instead of the whole script, so that the program testing time is saved, and the program testing efficiency is improved.
According to the program testing method of the embodiment of the present disclosure, the application program may include a program that implements a UI interface.
For example, the program testing method of the embodiment of the disclosure can test the functions of UI interfaces on different browsers of the terminal device. The second execution machine may run the script through Airtest.
Airtest is a cross-platform user interface automated testing framework. Airtest uses image recognition techniques to locate elements of a user interface. Airtest can easily run scripts on large-scale clusters of devices.
At present, Airtest mainly supports concurrent execution of android devices, and for PC devices, when ordinary automatic script developers develop scripts, complex configuration is required.
According to the program testing method of the embodiment of the disclosure, the main control device obtains the version information related to the terminal device by querying the registry on each first execution machine, and by using the version information, the configuration file in the test script is not required to be manually modified before each test, so that the automatic program test can be realized, the program testing efficiency is further improved, and the convenience of the program test is also improved.
Airtest multi-script concurrent execution is inefficient. According to the program testing method of the embodiment of the disclosure, the whole script is divided into the plurality of sub scripts, and even if the connection between the terminal device and the corresponding second execution machine is disconnected, which terminal devices fail in testing which sub scripts can be known. The failed sub-scripts can be re-run subsequently instead of re-testing the whole script, so that the program testing time is saved, and the program testing efficiency is improved.
FIG. 6 schematically shows a flow chart of a program testing method according to yet another embodiment of the present disclosure.
As shown in fig. 6, the method includes operations S210 to S230, S610.
In operation S210, at least one first execution machine that has a communication connection with a master device is determined.
This operation is the same as operation S210 shown in fig. 2, and is not described again here.
In operation S220, at least one second execution machine to which the terminal device is connected among the at least one first execution machine is determined.
This operation is the same as operation S220 shown in fig. 2, and is not described again here.
In operation S230, the test script is transmitted to each of the at least one second execution machine, so that each execution machine tests the application program running on the terminal device connected to itself by running the received test script.
This operation is the same as operation S230 shown in fig. 2, and is not described again here.
In operation S610, for each of the at least one second execution machine, in response to that the current execution machine successfully completes the program test, a test result returned by the current execution machine is obtained and displayed.
In this operation, for each of the plurality of second execution machines, the main control device responds to the current execution machine to successfully complete the program test, and obtains and displays a test result returned by the current execution machine.
For example, the master device may add multiple first execution machines through jenkins, validate the second execution machine, and perform program testing on the second execution machine through Airtest. When a program is tested by jenkins, a task needs to be created.
And creating a main task according to the divided sub-scripts, wherein each main task represents the final running condition of the corresponding sub-script. And creating a subtask corresponding to the main task according to the processing flows of distribution, operation and the like of each sub script in the operation process of each sub script, wherein each subtask represents the operation condition of the corresponding sub script processing flow.
When the executive machine carries out program test, the executive machine can acquire the task state as a main task in execution in real time, traverse a plurality of subtasks under the main task and judge whether each subtask fails. And once the sub task fails, setting the task state of the main task corresponding to the sub task as failure. And if the task state of the subtask under the main task is in execution, setting the task state of the main task corresponding to the subtask to be in execution. And when the task states of all the main tasks are completed and the tasks are successful, storing the execution conditions of all the main tasks.
After the current execution machine successfully completes the program test, the main control device obtains and displays the execution conditions of all main tasks, namely the final program test result.
Figure 7 schematically shows a flow chart of a processing method for an execution machine according to an embodiment of the present disclosure.
As shown in fig. 7, the method includes operations S710 to S730.
In operation S710, a registry is generated.
In operation S720, the registry is stored on the execution machine.
In operation S730, in response to the connection of the terminal device to the execution engine, version information about the terminal device is recorded in the registry, so that the main control device having a communication connection with the execution engine can determine whether the terminal device is connected to the execution engine based on the information recorded in the registry.
According to the program testing method of the embodiment of the disclosure, when the terminal device is connected with the execution machine, the execution machine generates the registry and stores the registry on the execution machine. The registry has version information about the terminal device, and whether the terminal device is connected to the execution machine can be determined according to the version information.
According to the program testing method of the embodiment of the disclosure, when the terminal device is disconnected from the execution machine, the execution machine responds to the disconnection between the terminal device and the execution machine, and deletes the version information of the terminal device disconnected from the execution machine in the registry.
According to the program testing method of the embodiment of the disclosure, the execution machine can check the connection condition of the terminal device and the execution machine in real time based on the version information about the terminal device in the registry on the execution machine, so as to judge the testing condition of the program test.
FIG. 8 schematically shows a block diagram of a program test device according to an embodiment of the disclosure.
As shown in fig. 8, the program test apparatus 800 includes: a determine first execution machine module 810, a determine second execution machine module 820, and a send test script module 830. The program testing apparatus may perform the method described above with reference to the method embodiment, and is not described herein again.
Specifically, the determine first execution engine module 810 may be configured to determine at least one first execution engine that has a communication connection with the master device.
The determine second execution machine module 820 may be configured to determine at least one second execution machine connected with the terminal device from among the at least one first execution machine.
The send test script module 830 may be configured to send a test script to each of the at least one second execution machine, so that each execution machine tests an application running on a terminal device connected to the execution machine by running the received test script.
Figure 9 schematically illustrates a block diagram of determining a second execution engine module according to an embodiment of the disclosure.
As shown in fig. 9, the determine second execution engine module 820 includes: query submodule 821 and determine second execution engine submodule 822.
Specifically, the query submodule 821 may be configured to query a registry on each of the at least one first execution machine to obtain at least one corresponding query result, where each query result corresponds to one first execution machine.
The determine second execution machine sub-module 822 may be configured to determine, based on the at least one query result, at least one of the at least one first execution machine to which the terminal device is connected.
The determine second execution machine sub-module 822 may determine, for each query result, that the first execution machine corresponding to the current query result is connected to the terminal device in response to the version information about the terminal device in the current query result representation registry, and use the first execution machine as a second execution machine.
FIG. 10 schematically shows a block diagram of a send test script module according to an embodiment of the present disclosure.
As shown in fig. 10, the transmission test script module 830 may include a script transmission sub-module 831.
Specifically, the script sending sub-module 831 is configured to send the entire test script to each of the at least one second execution machine.
FIG. 11 schematically illustrates a block diagram of another send test script module, according to an embodiment of the present disclosure.
As shown in fig. 11, the send test script module 830 may include a script distribution sub-module 832.
Specifically, the script distributing sub-module 832 is configured to divide the whole test script into a plurality of sub-scripts, and then distribute the plurality of sub-scripts to corresponding ones of the at least one second execution machine according to a preset rule.
FIG. 12 schematically illustrates a block diagram of a script distribution submodule, according to an embodiment of the present disclosure.
As shown in fig. 12, the script distribution submodule 832 may include a first distribution unit 8321 and a second distribution unit 8322.
Specifically, the first distribution unit 8321 randomly transmits each of the plurality of sub-scripts to one of the at least one second execution machine in the case that the number of the sub-scripts is smaller than the number of the second execution machines, so that different sub-scripts run on different second execution machines.
The second distribution unit 8322 distributes the plurality of sub-scripts to each of the at least one second execution machine in average in the case where the number of the sub-scripts is equal to or greater than the number of the second execution machines and the number of the sub-scripts is an integral multiple of the number of the second execution machines.
According to the program testing apparatus of the embodiment of the present disclosure, the application program may include a program that implements a UI interface.
Fig. 13 schematically shows a block diagram of a program test device according to another embodiment of the present disclosure.
The program testing apparatus 800 includes: a determine first execution machine module 810, a determine second execution machine module 820, a send test script module 830, and a show results unit 840.
Specifically, a determine first execution machine module 810, a determine second execution machine module 820, and a send test script module 830
A result displaying unit 840, configured to, for each of the at least one second execution machine, respond to that the current execution machine successfully completes the program test of this time, and obtain and display a test result returned by the current execution machine.
FIG. 14 schematically illustrates a block diagram of a handler test device for an execution machine according to an embodiment of the present disclosure.
The program testing apparatus 900 includes: a generate registry module 910, a store module 920, and a first response module 930.
Specifically, the generate registry module 910 is configured to generate a registry;
a storage module 920, configured to store the registry on the execution machine; and
a first response module 930, configured to record version information about the terminal device in the registry in response to the terminal device being connected to the execution machine, so that the master control device having a communication connection with the execution machine can determine whether the terminal device is connected to the execution machine based on the information recorded in the registry.
Figure 15 schematically shows a block diagram of a processing device for an execution machine according to another embodiment of the present disclosure.
The program testing apparatus 800 includes: a generate registry module 910, a storage module 920, a first response module 930, and a second response module 940.
Specifically, the second response module 940 is configured to, in response to that there is a terminal device disconnected from the execution machine, delete the version information of the terminal device disconnected from the execution machine in the registry.
It should be noted that the embodiments of the apparatus portion and the method portion are similar to each other, and the achieved technical effects are also similar to each other, which are not described herein again.
Any of the modules, sub-modules, and units according to embodiments of the present disclosure, or at least part of the functionality of any of them, may be implemented in one module. Any one or more of the modules and units according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, units according to the embodiments of the present disclosure may be implemented at least partially as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented by any other reasonable means of hardware or firmware by integrating or packaging the circuits, or in any one of three implementations of software, hardware and firmware, or in any suitable combination of any of them. Alternatively, one or more of the modules, units according to embodiments of the present disclosure may be implemented at least partly as computer program modules, which, when executed, may perform the respective functions.
For example, any of the first execution machine module 810, the second execution machine module 820, and the test script sending module 830 may be combined and implemented in one module, or any of them may be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the determining first execution machine module 810, the determining second execution machine module 820, and the sending test script module 830 may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or may be implemented in any one of three implementations of software, hardware, and firmware, or in a suitable combination of any of them. Alternatively, at least one of the determine first execution machine module 810, the determine second execution machine module 820 and the send test script module 830 may be at least partially implemented as a computer program module that, when executed, may perform corresponding functions.
Fig. 16 schematically shows a block diagram of an electronic device adapted to implement the above described method according to an embodiment of the present disclosure. The electronic device shown in fig. 16 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 16, an electronic apparatus 1000 according to an embodiment of the present disclosure includes a processor 1001 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)1002 or a program loaded from a storage section 1008 into a Random Access Memory (RAM) 1003. Processor 1001 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or associated chipset, and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), among others. The processor 1001 may also include onboard memory for caching purposes. The processor 1001 may include a single processing unit or multiple processing units for performing different actions of a method flow according to embodiments of the present disclosure.
In the RAM1003, various programs and data necessary for the operation of the system 1000 are stored. The processor 1001, ROM 1002, and RAM1003 are connected to each other by a bus 1004. The processor 1001 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 1002 and/or the RAM 1003. Note that the programs may also be stored in one or more memories other than the ROM 1002 and the RAM 1003. The processor 1001 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
System 1000 may also include an input/output (I/O) interface 1005, the input/output (I/O) interface 1005 also being connected to bus 1004, according to an embodiment of the present disclosure. The system 1000 may also include one or more of the following components connected to the I/O interface 1005: an input section 1006 including a keyboard, a mouse, and the like; an output section 1007 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 1008 including a hard disk and the like; and a communication section 1009 including a network interface card such as a LAN card, a modem, or the like. The communication section 1009 performs communication processing via a network such as the internet. The driver 1010 is also connected to the I/O interface 1005 as necessary. A removable medium 1011 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 1010 as necessary, so that a computer program read out therefrom is mounted into the storage section 1008 as necessary.
According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication part 1009 and/or installed from the removable medium 1011. The computer program performs the above-described functions defined in the system of the embodiment of the present disclosure when executed by the processor 1001. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.
The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The computer-readable storage medium carries one or more programs which, when executed, implement the method according to an embodiment of the disclosure.
According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM 1002 and/or the RAM1003 described above and/or one or more memories other than the ROM 1002 and the RAM 1003.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.
The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims (20)

1. A program testing method, comprising:
determining at least one first execution machine which is in communication connection with the main control equipment;
determining at least one second execution machine connected with terminal equipment in the at least one first execution machine; and
and sending the test script to each execution machine in the at least one second execution machine, so that each execution machine tests the application program running on the terminal equipment connected with the execution machine by running the received test script.
2. The method of claim 1, wherein determining at least one second execution machine of the at least one first execution machine to which a terminal device is connected comprises:
querying a registry on each first execution machine in the at least one first execution machine to obtain at least one corresponding query result, wherein each query result corresponds to one first execution machine; and
and determining the at least one second execution machine connected with the terminal equipment in the at least one first execution machine based on the at least one query result.
3. The method of claim 2, wherein determining the at least one second of the at least one first execution machine to which a terminal device is connected based on the at least one query result comprises: for each of the results of the query,
and responding to the version information related to the terminal equipment in the current query result representation registry, determining that the first execution machine corresponding to the current query result is connected with the terminal equipment, and taking the first execution machine as a second execution machine.
4. The method of any of claims 1 to 3, wherein sending a test script to each of the at least one second execution machine comprises one of:
respectively sending the whole test script to each execution machine in the at least one second execution machine;
the whole test script is divided into a plurality of sub scripts, and then the plurality of sub scripts are distributed to corresponding execution machines in the at least one second execution machine according to preset rules.
5. The method of claim 4, wherein distributing the plurality of sub-scripts to corresponding ones of the at least one second execution machine according to preset rules comprises at least one of:
under the condition that the number of the sub scripts is smaller than the number of the second execution machines, randomly sending each sub script in the plurality of sub scripts to one second execution machine in the at least one second execution machine, and enabling different sub scripts to run on different second execution machines;
and in the case that the number of the sub scripts is greater than or equal to the number of the second execution machines and the number of the sub scripts is integral multiple of the number of the second execution machines, distributing the plurality of sub scripts to each of the at least one second execution machine in an average manner.
6. The method of claim 1, wherein the application comprises a program that implements a UI interface.
7. The method of claim 1, further comprising: for each of the at least one second execution engine,
and responding to the successful completion of the program test of the current execution machine, and acquiring and displaying a test result returned by the current execution machine.
8. A processing method for an execution machine, comprising:
generating a registry;
storing the registry on an execution machine; and
in response to the execution machine being connected with the terminal device, recording version information about the terminal device in the registry, so that a main control device in communication connection with the execution machine can determine whether the terminal device is connected with the execution machine based on the information recorded in the registry.
9. The method of claim 8, further comprising:
and in response to the disconnection between the terminal equipment and the executive machine, deleting the version information of the terminal equipment disconnected with the executive machine in the registry.
10. A program test device, comprising:
the method comprises the steps of determining a first execution machine module, wherein the first execution machine module is used for determining at least one first execution machine which is in communication connection with a main control device;
a second execution machine determining module, configured to determine at least one second execution machine connected to the terminal device in the at least one first execution machine; and
and the test script sending module is used for sending the test script to each execution machine in the at least one second execution machine, so that each execution machine tests the application program running on the terminal equipment connected with the execution machine by running the received test script.
11. The apparatus of claim 10, wherein the determining a second execution engine module comprises:
the query submodule is used for querying the registry on each first execution machine in the at least one first execution machine to obtain at least one corresponding query result, wherein each query result corresponds to one first execution machine; and
and the determining second execution machine submodule is used for determining the at least one second execution machine connected with the terminal equipment in the at least one first execution machine based on the at least one query result.
12. The apparatus of claim 11, wherein the determining a second execution engine sub-module comprises: for each of the results of the query,
and responding to the version information related to the terminal equipment in the current query result representation registry, determining that the first execution machine corresponding to the current query result is connected with the terminal equipment, and taking the first execution machine as a second execution machine.
13. The apparatus of any of claims 10 to 12, wherein the send test script module comprises one of:
the script sending submodule is used for respectively sending the whole test script to each execution machine in the at least one second execution machine;
and the script distribution submodule is used for dividing the whole test script into a plurality of sub scripts and distributing the plurality of sub scripts to corresponding execution machines in the at least one second execution machine according to a preset rule.
14. The apparatus of claim 13, wherein the script distribution submodule comprises at least one of:
the first distribution unit is used for randomly sending each sub script in the plurality of sub scripts to one second execution machine in the at least one second execution machine under the condition that the number of the sub scripts is smaller than the number of the second execution machines, so that different sub scripts run on different second execution machines;
and the second distribution unit is used for distributing the plurality of sub scripts to each second execution machine in the at least one second execution machine in an average way under the condition that the number of the sub scripts is greater than or equal to the number of the second execution machines and the number of the sub scripts is integral multiple of the number of the second execution machines.
15. The apparatus of claim 10, wherein the application comprises a program that implements a UI interface.
16. The apparatus of claim 10, further comprising: a presentation result unit for presenting, for each of the at least one second execution engine,
and responding to the successful completion of the program test of the current execution machine, and acquiring and displaying a test result returned by the current execution machine.
17. A processing apparatus for an execution machine, comprising:
the registry generation module is used for generating a registry;
the storage module is used for storing the registry on an execution machine; and
the first response module is used for responding to the fact that the terminal equipment is connected with the execution machine, recording version information of the terminal equipment in the registry, and therefore the main control equipment which is in communication connection with the execution machine can determine whether the terminal equipment is connected with the execution machine or not based on the information recorded in the registry.
18. The apparatus of claim 17, further comprising:
and the second response module is used for responding to the disconnection between the terminal equipment and the executive machine and deleting the version information of the terminal equipment disconnected with the executive machine in the registry.
19. An electronic device, comprising:
one or more processors;
a memory for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-9.
20. A computer-readable storage medium storing computer-executable instructions for implementing the method of any one of claims 1 to 9 when executed.
CN202110965088.0A 2021-08-20 2021-08-20 Program testing method and device Pending CN113535590A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110965088.0A CN113535590A (en) 2021-08-20 2021-08-20 Program testing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110965088.0A CN113535590A (en) 2021-08-20 2021-08-20 Program testing method and device

Publications (1)

Publication Number Publication Date
CN113535590A true CN113535590A (en) 2021-10-22

Family

ID=78122767

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110965088.0A Pending CN113535590A (en) 2021-08-20 2021-08-20 Program testing method and device

Country Status (1)

Country Link
CN (1) CN113535590A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114706773A (en) * 2022-03-29 2022-07-05 网宿科技股份有限公司 Automated testing method, automated testing equipment and readable storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114706773A (en) * 2022-03-29 2022-07-05 网宿科技股份有限公司 Automated testing method, automated testing equipment and readable storage medium

Similar Documents

Publication Publication Date Title
CN112799940B (en) Regression testing method, regression testing device, computer system and computer readable storage medium
US11303729B2 (en) Virtual workspace experience visualization and optimization
US10164848B1 (en) Web service fuzzy tester
US11269756B1 (en) Self-healing web applications
CN111782988B (en) Method, apparatus, computer system and storage medium for determining source of application program
US20170161171A1 (en) Tenant Code Debugging in Multi-Tenant Systems
CN112965916B (en) Page testing method, page testing device, electronic equipment and readable storage medium
US10025697B2 (en) Generation of automated unit tests for a controller layer system and method
CN113918864A (en) Website page testing method, testing system, testing device, electronic equipment and medium
CN113535590A (en) Program testing method and device
CN111859077A (en) Data processing method, device, system and computer readable storage medium
CN110717992B (en) Method, apparatus, computer system and readable storage medium for scheduling model
CN113362173A (en) Anti-duplication mechanism verification method, anti-duplication mechanism verification system, electronic equipment and storage medium
CN111930629A (en) Page testing method and device, electronic equipment and storage medium
CN112506781B (en) Test monitoring method, device, electronic equipment, storage medium and program product
CN111859403B (en) Dependency vulnerability determination method and device, electronic equipment and storage medium
CN115134228A (en) Environment link supply and detection method, device, equipment, medium and program product
CN113495498A (en) Simulation method, simulator, device, and medium for hardware device
Wang et al. A software quality framework for mobile application testing
US20240095157A1 (en) Systems and methods for operating web management software
US10097399B1 (en) Distributed computing management links
CN113158166B (en) Peripheral calling method, system, electronic equipment and medium
CN114064484A (en) Interface testing method and device, electronic equipment and readable storage medium
CN114756329A (en) Business process simulation method and device, electronic equipment and readable storage medium
CN113760735A (en) Application debugging method, device, computer system and computer 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