CN111124936B - Building block type software testing method, testing device, testing equipment and storage medium - Google Patents

Building block type software testing method, testing device, testing equipment and storage medium Download PDF

Info

Publication number
CN111124936B
CN111124936B CN202010128468.4A CN202010128468A CN111124936B CN 111124936 B CN111124936 B CN 111124936B CN 202010128468 A CN202010128468 A CN 202010128468A CN 111124936 B CN111124936 B CN 111124936B
Authority
CN
China
Prior art keywords
building block
node
jump
test
flow chart
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
Application number
CN202010128468.4A
Other languages
Chinese (zh)
Other versions
CN111124936A (en
Inventor
师江帆
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shi Jiangfan
Original Assignee
Individual
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 Individual filed Critical Individual
Priority to CN202010128468.4A priority Critical patent/CN111124936B/en
Publication of CN111124936A publication Critical patent/CN111124936A/en
Application granted granted Critical
Publication of CN111124936B publication Critical patent/CN111124936B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The invention discloses a building block type software testing method, a testing device, testing equipment and a storage medium, wherein the testing method comprises the following steps: based on a pre-established topological flow chart, generating a corresponding building block sub-module, wherein the substantial content of the building block sub-module is the topological flow chart; selecting at least two building block sub-modules, connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, and connecting a tail node of a topology flow diagram corresponding to a front building block sub-module with each head node with the same node name as the tail node in the topology flow diagram corresponding to a rear building block sub-module in the execution sequence; compiling the building block diagram into test codes, including: performing depth traversal on the topology flow chart corresponding to the building block diagram to generate a test code corresponding to the topology flow chart; and running the test code in a test running environment to obtain a test result. The invention builds the building block diagram by utilizing the building block submodule in the automatic function test, so that the topology flow reduces the dimension, and the effect is particularly obvious in the complex webpage function test.

Description

Building block type software testing method, testing device, testing equipment and storage medium
Technical Field
The invention relates to the technical field of UI function test, in particular to a building block type software test method, a building block type software test device, building block type software test equipment and a building block type software storage medium.
Background
The UI interface (including APP interface or web page or wearable device) is an important platform for network information communication, and because of the diversity and uncertainty of the content and function carried by the UI interface, the UI interface needs to be designed according to different application requirements and network environments, and in order to ensure the reliability of the interface performance, the designed user interface needs to be tested.
At present, most software development companies basically use a manual test mode, a software test engineer writes test cases, then a user interface is manually tested, the efficiency is low, the test cases are easy to miss, and the test process cannot be effectively traced.
Based on this, development of automated testing techniques for user interface functions is particularly urgent. The user interface automatic test practice is to automatically verify the input and output of the tested user interface, namely simulate the input of a user and the click jump action of an interface button control, and verify the output result of the input operation. The prior art lacks a building block type software testing method for effectively finding out defects of a user interface.
In the prior art, a UI automation function test method is disclosed, for example, in the chinese patent application with publication number CN109857668A, but for the complex test of the web page function, especially for the case that the branch paths of the topology flow chart reach thousands or even tens of thousands, the drawbacks of the test method are easily exposed, that is, the drawing work of the topology flow chart becomes complex, a great deal of effort and time are required, and errors easily occur manually, so that the software test result fails or is not ideal.
Disclosure of Invention
In order to solve the problems in the prior art, the invention provides a building block type software testing method, a testing device, testing equipment and a storage medium, which are characterized in that a topology flow chart is simplified by using a building block diagram overlapping mode, and the efficiency and the accuracy of software testing are improved, wherein the technical scheme is as follows:
in one aspect, the invention provides a building block type software testing method, which comprises the following steps:
based on a pre-established topological flow chart, generating a corresponding building block sub-module, wherein the substantial content of the building block sub-module is the topological flow chart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node;
Selecting at least two building block sub-modules, and connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, wherein in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to a latter building block sub-module in the execution sequence;
compiling the building block diagram into test codes, including: performing deep traversal on the topology flow chart corresponding to the building block diagram, and generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
and operating the test code in a test operation environment to obtain a test result.
The first alternative solution is that after obtaining the building block diagram, the method further comprises:
selecting at least one building block sub-module, connecting the building block sub-module with the building block diagram according to the execution sequence to obtain a building block total diagram, and compiling the building block total diagram into a test code;
if the execution sequence of the building block sub-modules is prior to the building block diagram, connecting tail nodes of the topology flow diagram corresponding to the building block sub-modules with each head node with the same node name as the tail nodes in the topology flow diagram corresponding to the building block diagram;
If the execution sequence of the building block diagram is prior to the building block sub-module, connecting the tail node of the topology flow diagram corresponding to the building block diagram with each head node with the same node name as the tail node in the topology flow diagram corresponding to the building block sub-module.
The second alternative solution is that after obtaining the building block diagram, the method further comprises:
selecting at least two building block diagrams obtained in advance, connecting the building block diagrams according to an execution sequence to obtain a building block total diagram, and compiling the building block total diagram into a test code;
in the two connected building block diagrams, the tail node of the topology flow diagram corresponding to the former building block diagram is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to the latter building block diagram in the execution sequence.
Further, some or all of the building block total drawings can be copied, cut and/or pasted.
Further, the method further comprises acquiring an assertion setting result before or after acquiring the topology flow chart, wherein the assertion setting result is an expected value set for a display element in the interface node before or after the jump;
generating test code includes: the program of the assertion operation is referenced after jumping to the pre-jump interface node or the post-jump interface node corresponding to the set expected value.
Further, the step of running the test code in the test running environment includes a local running mode and/or a cloud running mode, where the local running mode includes: downloading the test code from the cloud to a local computer, and running the test code in test software in the computer to obtain a test result;
the cloud operation mode comprises the following steps: sending an operation request to a cloud, wherein the operation request comprises a user interface to be tested; acquiring a corresponding test code according to the operation request; and receiving a test result obtained by running the test code in the test software of the cloud based on the running request.
Further, the test result comprises a test report in the form of video, pictures and/or words, and the test report also comprises a test failure case description, wherein the test failure case comprises interface jump errors and/or assertion judgment errors.
On the other hand, the invention provides a building block type software testing device, which comprises the following modules:
the building block submodule generation module is used for generating a corresponding building block submodule based on a pre-established topological flow chart, and the substantial content of the building block submodule is the topological flow chart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node;
The building block diagram generation module is used for selecting at least two building block sub-modules, and connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, wherein in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to a latter building block sub-module in the execution sequence;
the test code generation module is used for compiling the building block diagram into a test code and comprises the following steps: performing deep traversal on the topology flow chart corresponding to the building block diagram, and generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
and the test code running module is used for running the test code in a test running environment to obtain a test result.
In yet another aspect, the present invention provides a building block type software testing apparatus, including a processor and a memory, wherein the memory stores a program, and when the processor executes the program, the following operations are performed:
Based on a pre-established topological flow chart, generating a corresponding building block sub-module, wherein the substantial content of the building block sub-module is the topological flow chart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node;
selecting at least two building block sub-modules, and connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, wherein in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to a latter building block sub-module in the execution sequence;
compiling the building block diagram into test codes, including: performing deep traversal on the topology flow chart corresponding to the building block diagram, and generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
And operating the test code in a test operation environment to obtain a test result.
In still another aspect, the present invention provides a storage medium storing a program which, when executed, performs the operations of:
based on a pre-established topological flow chart, generating a corresponding building block sub-module, wherein the substantial content of the building block sub-module is the topological flow chart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node;
selecting at least two building block sub-modules, and connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, wherein in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to a latter building block sub-module in the execution sequence;
Compiling the building block diagram into test codes, including: performing deep traversal on the topology flow chart corresponding to the building block diagram, and generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
and operating the test code in a test operation environment to obtain a test result.
The technical scheme provided by the invention has the following beneficial effects:
a. building a building block diagram by using building block sub-modules, so that the topology flow reduces the dimension, and the effect is particularly obvious in complex webpage function test;
b. the background of the built building block diagram is utilized to automatically generate a complex topological flow diagram, so that energy and time are saved;
c. the manual errors in the topology flow chart are reduced, the accuracy of the topology flow chart is improved, and the software testing accuracy is improved;
d. the method can automatically test interfaces such as computer pages, mobile terminal webpages, mobile terminal App, weChat applets, weChat public signals, PC application programs, industrial control software and the like, and has wide application range;
e. the test report is comprehensive and accurate, the report form comprises text, pictures and/or video formats, the traceability of the test process is strong, and the test result is clear at a glance.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flow chart of a building block type software testing method provided by an embodiment of the invention;
FIG. 2 is a schematic diagram of a topology flow chart provided by an embodiment of the present invention;
FIG. 3 is a flow chart of a building block type software testing method for adding parameter configuration and assertion provided by an embodiment of the invention;
FIG. 4 is a block diagram of a building block type software testing device according to an embodiment of the present invention;
FIG. 5 is an application interface diagram of a practical topology flow chart provided by an embodiment of the present invention;
FIG. 6 is an application interface diagram of a test report provided by an embodiment of the present invention;
FIG. 7 is a front display interface diagram of a toy sub-module according to an embodiment of the present invention;
FIG. 8 is a front display interface diagram of a building block diagram provided by an embodiment of the present invention;
FIG. 9 is a flowchart of a software testing method in a second building block diagram generating manner according to an embodiment of the present invention;
Fig. 10 is a flowchart of a software testing method in a third building block diagram generating manner according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, article, or device that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or device.
In one embodiment of the present invention, a building block type software testing method is provided, referring to fig. 1, comprising the following steps:
s1, generating corresponding building block sub-modules based on a pre-established topological flow chart.
Specifically, the establishing process of the topology flow chart includes:
s11, obtaining the jump information of the user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump.
Further, the UI (User Interface) generally refers to an operation Interface of a User, including interfaces such as a mobile APP, a web page, a WeChat applet, a WeChat public number, a PC application, and industrial control software, which will be hereinafter referred to as interfaces. The jump information includes a pre-jump interface node, a jump element, and a post-jump interface node, such as: a plurality of control buttons are arranged on the interface node before the jump, the control buttons can be pressed to jump to the next interface node, taking a first page interface of a travel carrying net as an example, and taking a hotel and an air ticket as an example, the jump elements respectively obtain a hotel booking interface and an air ticket booking interface; inputting inquiry conditions (date, address or hotel type and the like) at a hotel booking interface, searching to obtain a hotel inquiry result interface, inputting inquiry conditions (departure city, destination city, date and the like) at an air ticket booking interface, searching to obtain an air ticket inquiry result interface, then selecting one result item, entering an order placing interface, clicking a payment button at the order placing interface, entering a payment interface and the like, wherein at least the following jump information appears: (1) the method comprises the steps of (1) a first page- "hotel" -booking a hotel interface, (2) a first page- "air-ticket" -booking an air ticket interface, (3) a hotel booking interface- "search" -booking result interface, (4) an air ticket booking interface- "search" -booking result interface, (5) an air ticket booking result interface- "term1" -placing orders interface, (6) a placing orders interface- "pay" -paying interface, wherein the middle item of each jump information is a jump element (namely an interactive button), the jump element is named by the control name of the interface interactive button, and interface nodes before and after the jump element are preferably named freely according to a simple and clear principle.
S12, establishing a topology flow chart according to the jump information.
Specifically, as shown in fig. 5, the topology flow chart includes a root interface node and one or more branch paths, and at least one jump element and a corresponding jump interface node are located on each branch path, and the specific establishment process is as follows:
different jump elements corresponding to the same pre-jump interface node form different branch paths,
based on the fact that the interface node after the jump corresponding to the first jump element is the interface node before the jump corresponding to the second jump element, the first jump element and the second jump element are set to be adjacent jump elements on the same branch path, for example, taking six jump information in the carrying process as an example, a topology flow chart shown in fig. 2 can be established, the names of the jump elements in the diagram are only schematic, and the names of the bottom control elements of the object to be tested are actually used as the reference, as shown in fig. 5.
The building block sub-module is essentially the topology flow chart, but the front end is only in a single frame form with names, as shown in fig. 7, which shows the front end display of a plurality of building block sub-modules.
S2, selecting at least two building block sub-modules, and connecting the building block sub-modules according to the execution sequence to obtain a building block diagram.
Further, in the two connected building block sub-modules, a tail node of the topology flow chart corresponding to the former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow chart corresponding to the latter building block sub-module in the execution sequence. For example, the topology flow chart corresponding to the former building block submodule has 10 tail nodes, wherein the node names of 2 tail nodes are N1, the node names of 3 tail nodes are N2, the other 5 tail nodes are N3, the topology flow chart corresponding to the latter building block submodule has 9 head nodes, the node names of 5 head nodes are N2, the node names of the other 4 head nodes are N3, the building block chart formed by the two building block submodules is cut off until the head node of the topology flow chart corresponding to the latter building block submodule has 35 (i.e. 3×5+5×4) branch paths, and if the latter building block submodule itself has 20 tail nodes, the topology flow chart corresponding to the building block chart formed by the two building block submodules has 702 (i.e. 35×20+2) tail nodes in total. In one embodiment of the present invention, the flow chart is a tree structure, and has only one first node, and then, it is also within the scope of the present invention, for example, the name of the unique first node of the next building block sub-module is N2, then the building block chart composed of the two building block sub-modules is cut off until the first node of the topology flow chart corresponding to the next building block sub-module has 3 branch paths, and if the next building block sub-module itself has 15 tail nodes, then the topology flow chart corresponding to the building block chart composed of the two building block sub-modules has 52 (i.e. 3×15+2+5) tail nodes in total. Compared with the common topological flow chart, the invention has obvious progress, namely, the original topological flow chart of a plurality of branch paths only needs to be respectively drawn into two flow charts by utilizing the technical scheme of the invention and then lap joint the two flow charts into the building block chart, so that the topological dimension is greatly reduced, errors caused by manual operation are avoided, the UI function test can be realized with higher accuracy under the condition of low labor cost, and the superiority of the test method can be embodied under the condition that the webpage function test is more complex. The essence of the building block diagram is that the topology flow diagram corresponding to the elements of the overlapping building block diagram (such as building block sub-modules, and building block diagram units below) is a total topology flow diagram formed according to the overlapping relationship of the elements, but the front end of the building block diagram is only in a single frame form with naming, and as shown in fig. 8, the front ends of a plurality of building block diagrams are displayed.
S3, compiling the building block diagram into a test code.
Specifically, performing depth traversal on a topology flow chart corresponding to the building block diagram, and generating a test code corresponding to each complete branch path from a traversal starting node to the corresponding complete branch path; further specifically, the process of generating test code with the code engine is in effect the process of the code engine traversing the topology flow diagram: in the traversing process, when the jump element is detected, the control name is acquired to execute click jump operation, and the click jump operation can be realized by using a click (id) function, wherein the id is the control name corresponding to the jump element, and finally the generated test code comprises a program for executing user interface jump operation on each jump element.
And S4, running the test codes in a test running environment to obtain a test result.
And placing the test codes into a test operation environment in a template form conforming to operation conditions, and operating the test codes to obtain a test result. The manner of operation includes, but is not limited to, the following two ways:
cloud operation mode: sending an operation request to a cloud, wherein the operation request comprises a user interface to be tested; the cloud server obtains a test code corresponding to the user interface to be tested according to the operation request, and places the test code into a project template to enable the test code to meet the operation requirement of a cloud test environment, for example, copies the test code to a folder with a designated address, calls a source configuration file of the user interface to be tested, automatically fills parameters in the project template according to the source configuration file, and places the project template with the test code into test software of the cloud for operation after completion of filling, and receives a test result obtained by operating the test code in the test software of the cloud based on the operation request;
Local operation mode: the method comprises the steps of downloading test codes from a cloud to a local computer, running the test codes in test software in the computer, and carrying out project configuration on the test codes before running the test codes, wherein the configuration mode is consistent with the operation of putting the test codes into a project template in a cloud running mode. If the carrier of the interface is a mobile terminal, the mobile terminal needs to be connected to the local computer.
The test software includes, but is not limited to, intelliJ ideas, android Studio, which are used for testing interfaces in Android systems, and IntelliJ ideas can be used for testing Android, iOS systems, web or PC interfaces.
For most user interfaces to be tested, the initialization parameters, the input parameters and the assertion conditions need to be configured before the code is automatically generated, and the flow of the method is as shown in fig. 3, and the following description is given for parameter initialization before the corresponding test code is generated in step S3:
After the topology flow chart is acquired, initializing parameter configuration is carried out, the initializing parameter configuration result comprises a test initiation interface node and a URL thereof, and the initializing parameter configuration result is used for realizing parameter initialization when generating a test code and comprises the following steps: the method comprises initializing the traversal starting node as the test starting interface node, wherein the test starting interface node can be a pre-jump interface node corresponding to any jump element on any branch path in the topology flow chart, and it can be seen that the traversal starting node can be a root interface node of the topology flow chart, or can be a certain (not last) interface node in the middle of the topology flow chart, each complete branch path backwards from the traversal starting node comprises traversing to the last interface node, in one embodiment of the invention, the topology flow chart is a flow tree structure (unidirectional), in one preferred embodiment of the invention, two interface nodes in the topology flow chart can be in bidirectional jump, for example, a ticket booking interface in fig. 2 can be jumped to a ticket inquiry result interface through a search jump element, and then the ticket booking interface is jumped to a ticket booking interface through a back jump element, in the case that the ticket interface is the traversal starting node, the complete interface is the ticket booking interface is a URL (uniform resource locator) ticket booking interface, and the ticket booking interface is the ticket booking result interface of the ticket booking interface. The traversal starting node can select any node in the middle of the flow, so that when a new function is added to be tested, the new function is not required to be retested from the beginning, and only the interface node with the new function is required to be used as the traversal starting node, thereby effectively improving the testing efficiency. The automatic test system in the prior art can not realize the local test only aiming at the added new function, so that the automatic test efficiency is low, and the test process is long.
In addition to the test initiation interface node and the URL thereof, the initialization parameter configuration result further includes a test interface depth, where a configuration value of the test interface depth is greater than or equal to a longest depth value of the flowchart starting from the configured test initiation interface node, where the depth configuration value is equal to the longest depth value of the flowchart starting from the configured test initiation interface node, so as to ensure that each branch path flow starting from the test initiation interface node can be completely traversed; if there is interaction between multiple branch paths, for example, in a loan App, there is a loan business process interface and a repayment business process interface, and there is interaction between a loan business and a repayment business, for example, the loan should be performed before repayment, so if the interaction function between two branch paths is to be tested, the depth of the interface needs to be set to be the sum of the depth values of the two branch processes.
The following describes the configuration of the input parameters before the corresponding test code is generated in step S3:
the input parameter configuration result is obtained before or after the topology flow chart is obtained, and the input parameter configuration result comprises parameters which are required to be input in order to realize that the interface node jumps to the corresponding interface node after jumping, for example, in an air ticket booking interface, the input parameters which need to be configured comprise a departure place, a destination and a date, and can also comprise screening conditions, for example, a time period, an air company, a fare range and the like, and further, for example, in an air ticket inquiry result interface, selection item information, for example, the second air ticket information needs to be set, and the air ticket booking interface is entered after clicking. Of course, for some interfaces, it is not necessary to enter parameters, such as news apps or web pages, and it may take to randomly click on a news headline to enter the next interface. And setting the input parameters of the user at proper positions by the code engine in the process of generating the test code through the preset input parameters corresponding to each interface, namely assigning the input parameter configuration result to the input parameter element at the interface node before corresponding jump so as to finish the jump to the next interface.
The following describes the assertion configuration before the corresponding test code is generated in step S3:
performing assertion setting before or after obtaining a topology flow chart, wherein the assertion setting result is an expected value set for a display element in the interface node before or after the jump; in the process of generating codes, after jumping to a certain interface node preset with assertion configuration, referring to assertion operation, for example, performing assertion judgment by using asset (actual value= =expected value), for example, for an air ticket query result interface, if parameters input in the air ticket booking interface are Beijing to Shanghai, the displayed air ticket query result items are all in Beijing, the destination city is Shanghai, in the process of automatically generating test codes, list tables of the air ticket query result interface are retrieved from the background, according to the list table configuration, the first column of the list is take-off city information, the second column is a destination city, and assertion judgment inserted in the codes is to judge whether the first column value of the list table is equal to "Beijing" and whether the second column value is equal to "Shanghai".
The test result includes a text test report, where the test report includes a test failure case description, such as an interface jump error and/or an assertion judging error, referring to fig. 6, in a left Tests entry column, such as testCase004ab1 corresponds to a fail mark, and specific failure details appear on the right by clicking on the test report.
In a preferred embodiment of the invention, part or all of the topology flow graph is capable of moving, copying, cutting and/or pasting operations, which provides greater convenience in building the topology flow graph and reduces duplication of work.
Further, the flow information in each test case obtained by running the test code in the test running environment is associated with the data information and stored separately, and the flow information is effectively displayed on a product. Because the flow and the data are stored in different folders, the arrangement is clear, and the testers are clear at a glance, the work efficiency of the testers can be obviously improved no matter how the flow or the data are checked or modified.
The test process of the test method provided by the embodiment of the invention is as follows: converting the topology flow chart into a building block sub-module form (the substantial content is the same), providing module materials for generating the building block chart, wherein the process of generating the building block chart can be a construction process of a complex topology network in the background, namely, the tail node of the topology flow chart corresponding to the former building block sub-module (or the former building block chart) is connected with each head node with the same node name as the tail node in the topology flow chart corresponding to the latter building block sub-module (or the latter building block chart), compiling is carried out for each complete branch path of the huge topology network to form test codes, and finally, running in a test running environment to carry out a test to obtain a test result.
The above embodiment for generating a building block diagram by selecting at least two building block sub-modules is that only way to generate a building block diagram by the building block sub-modules in the initial building process of the building block diagram, that is, the first building block diagram is necessarily obtained by overlapping two or more building block sub-modules, but after the first building block diagram is obtained, the building block diagram is not generated in the manner of the above, which is specifically as follows:
in one embodiment of the present invention, as shown in fig. 9, after obtaining the building block diagram, the method further includes:
s2-2, selecting at least one building block sub-module, connecting the building block sub-module with the building block diagram according to the execution sequence to obtain a building block total diagram, and compiling the building block total diagram into a test code.
Specifically, if the execution sequence of the building block sub-modules is prior to the building block diagram, connecting tail nodes of the topology flow diagram corresponding to the building block sub-modules with each head node with the same node name as the tail nodes in the topology flow diagram corresponding to the building block diagram;
if the execution sequence of the building block diagram is prior to the building block sub-module, connecting the tail node of the topology flow diagram corresponding to the building block diagram with each head node with the same node name as the tail node in the topology flow diagram corresponding to the building block sub-module; a complicated situation may occur here, for example, when the building block diagram corresponds to the building block sub-module a-B-C, and the building block sub-modules a-B overlap, in the topology flow diagram corresponding to the building block sub-module B, there is no head node having the same node name as the tail node in the topology flow diagram corresponding to the building block sub-module a, for example, there is a tail node named N1 in the building block sub-module a as described in the above embodiment, and likewise, there is a tail node not connected to the head node of the building block sub-module C in the building block sub-module B, and then, together with all tail nodes of the last building block sub-module in the building block diagram, the tail nodes like this not connected to the head node of the following building block sub-module in the building block diagram are all used as the tail nodes of the topology flow diagram corresponding to the building block diagram, and these tail nodes all need to be matched with the head node of the building block sub-module (for example, module D) whose execution sequence is later than the building block diagram.
In one embodiment of the present invention, as shown in fig. 10, after obtaining the building block diagram, the method further includes:
s2-3, selecting at least two building block diagrams obtained in advance, connecting the building block diagrams according to an execution sequence to obtain a building block total diagram, and compiling the building block total diagram into a test code.
Specifically, in the two connected building block diagrams, the tail node of the topology flow diagram corresponding to the previous building block diagram is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to the next building block diagram in the execution sequence.
Likewise, the tail nodes of the topology flow diagram corresponding to the previous building block diagram are understood to be the sum of the tail nodes in the building block diagram not connected to the head node of the next building block sub-module and all the tail nodes of the last building block sub-module in the building block diagram, as described in the above embodiments.
In a preferred embodiment of the invention, some or all of the building blocks/block diagrams are capable of replication, cutting and/or pasting operations.
In one embodiment of the present invention, there is provided a building block type software testing apparatus, as shown in fig. 4, comprising the following modules:
Building block submodule generation module 410, configured to generate a corresponding building block submodule based on a pre-established topology flowchart, where the substantial content of the building block submodule is the topology flowchart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node;
the building block diagram generating module 420 is configured to select at least two building block sub-modules, and connect the building block sub-modules according to an execution sequence to obtain a building block diagram, where, in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a previous building block sub-module is connected with each head node having the same node name as the tail node in a topology flow diagram corresponding to a next building block sub-module in the execution sequence;
the test code generation module 430 is configured to compile the building block diagram into a test code, including: performing deep traversal on the topology flow chart corresponding to the building block diagram, and generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
And the test code running module 440 is configured to run the test code in a test running environment to obtain a test result.
In general, the testing operation of the building block type software testing module is as follows: the building block sub-module generating module 410 converts the topology flowchart into a building block sub-module form (the substantial content is the same), and the building block diagram generating module 420 generates building block diagram providing module materials, wherein the process of generating the building block diagram may be a complex topology network forming process in the background, namely, the tail node of the topology flowchart corresponding to the former building block sub-module or the former building block diagram is connected with each head node with the same node name as the tail node in the topology flowchart corresponding to the latter building block sub-module or the latter building block diagram, which is prepared for the test code generating module 430, and the test code generating module 430 compiles for each complete branch path of such a huge topology network to form a test code, so that the test code operating module 440 operates in a test operating environment to perform a test, and a test result is obtained.
The jump information module is used for obtaining jump information of each functional area according to the functional area of the user interface to be tested, jumping the interface node before jumping to the interface node after jumping, presetting information to be filled on the interface node before jumping as an input parameter, and setting assertion setting on the interface node after jumping; then, a topology flow chart is established according to the jump information, one node is selected in the topology flow chart as a test initial interface node, and the URL and the test depth value are initialized; and traversing the flow chart and automatically generating codes, wherein the essence of the automatically generated codes is to traverse to the interface node by using a code engine, if the assertion is set, judging the assertion, if the assertion is not set, adding the input parameters of the current interface node into the codes, after finishing the input parameters, clicking and jumping operation according to the id name of the jumping node, entering the next interface, and then performing the operation until jumping to the last interface node on the branch path (the corresponding assertion is finished, if the interface is set with the assertion).
It should be noted that: in the building block type software testing device provided in this embodiment, only the division of the above functional modules is used for illustration when the building block type software testing is performed, and in practical application, the above functional allocation may be completed by different functional modules according to needs, that is, the internal structure of the building block type software testing device is divided into different functional modules, so as to complete all or part of the functions described above. In addition, the embodiment of the building block type software testing device provided in this embodiment belongs to the same concept as the building block type software testing method provided in the foregoing embodiment, and detailed implementation processes of the embodiment of the building block type software testing device are shown in the method embodiment, that is, all features in the embodiment of the building block type software testing method embodiment may be introduced into the embodiment of the building block type software testing device by a reference manner, which is not repeated herein.
In one embodiment of the present invention, there is provided a building block type software testing apparatus including a processor and a memory, the memory storing a program, the processor executing the program to:
based on a pre-established topological flow chart, generating a corresponding building block sub-module, wherein the substantial content of the building block sub-module is the topological flow chart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node;
Selecting at least two building block sub-modules, and connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, wherein in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to a latter building block sub-module in the execution sequence;
compiling the building block diagram into test codes, including: performing deep traversal on the topology flow chart corresponding to the building block diagram, and generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
and operating the test code in a test operation environment to obtain a test result.
In one embodiment of the present invention, there is provided a storage medium storing a program which, when executed, performs the operations of:
based on a pre-established topological flow chart, generating a corresponding building block sub-module, wherein the substantial content of the building block sub-module is the topological flow chart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node;
Selecting at least two building block sub-modules, and connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, wherein in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to a latter building block sub-module in the execution sequence;
compiling the building block diagram into test codes, including: performing deep traversal on the topology flow chart corresponding to the building block diagram, and generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
and operating the test code in a test operation environment to obtain a test result.
It should be noted that: the building block type software testing device and the computer non-transitory readable storage medium provided by the above embodiment belong to the same conception as the building block type software testing method and the building block type software testing device provided by the above embodiment, and specific implementation processes of the building block type software testing device and the building block type software testing device are detailed in the method embodiment and the device embodiment, that is, all features in the building block type software testing method embodiment and the building block type software testing device embodiment can be introduced into the building block type software testing device embodiment and the storage medium embodiment by a reference manner, and are not repeated herein.
The invention builds the building block diagram by utilizing the building block submodule in the automatic function test, so that the topology flow reduces the dimension, and the effect is particularly obvious in the complex webpage function test.
The foregoing description of the preferred embodiments of the invention is not intended to limit the invention to the precise form disclosed, and any such modifications, equivalents, and alternatives falling within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims (8)

1. The building block type software testing method is characterized by comprising the following steps of:
based on a pre-established topological flow chart, generating a corresponding building block sub-module, wherein the substantial content of the building block sub-module is the topological flow chart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node; before or after establishing the topology flow chart, further comprising obtaining an assertion setting result, wherein the assertion setting result is an expected value set for a display element in the interface node before or after the jump;
Selecting at least two building block sub-modules, and connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, wherein in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to a latter building block sub-module in the execution sequence;
connecting the building block diagram with one or more building block sub-modules according to the execution sequence to obtain a building block total diagram, or connecting a plurality of building block diagrams according to the execution sequence to obtain the building block total diagram; the parts or all of the building block diagrams and/or the building block total diagrams can be subjected to copying, cutting and/or pasting operations; compiling the building block total map into a test code, including: performing deep traversal on the topology flow chart corresponding to the building block diagram, generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, and referring to a program of an assertion operation after jumping to a pre-jump interface node or a post-jump interface node corresponding to the expected value, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
And operating the test code in a test operation environment to obtain a test result.
2. The method for testing building block type software according to claim 1, further comprising after obtaining the building block diagram:
selecting at least one building block sub-module, connecting the building block sub-module with the building block diagram according to the execution sequence to obtain a building block total diagram, and compiling the building block total diagram into a test code;
if the execution sequence of the building block sub-modules is prior to the building block diagram, connecting tail nodes of the topology flow diagram corresponding to the building block sub-modules with each head node with the same node name as the tail nodes in the topology flow diagram corresponding to the building block diagram;
if the execution sequence of the building block diagram is prior to the building block sub-modules, the tail node of the topology flow diagram corresponding to the building block diagram is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to the building block sub-modules, wherein the building block diagram comprises at least two building block sub-modules connected in sequence, and the tail node of the topology flow diagram corresponding to the building block diagram comprises the tail node which is not connected with the head node of the latter building block sub-module in the building block diagram and all tail nodes of the last building block sub-module in the building block diagram.
3. The method for testing building block type software according to claim 1, further comprising after obtaining the building block diagram:
selecting at least two building block diagrams obtained in advance, connecting the building block diagrams according to an execution sequence to obtain a building block total diagram, and compiling the building block total diagram into a test code;
in the two connected building block diagrams, the tail node of the topology flow diagram corresponding to the former building block diagram is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to the latter building block diagram in the execution sequence, wherein the building block diagram comprises at least two building block sub-modules connected in sequence, and the tail node of the topology flow diagram corresponding to the building block diagram comprises the tail node which is not connected with the head node of the latter building block sub-module in the building block diagram and all tail nodes of the last building block sub-module in the building block diagram.
4. The building block software testing method according to claim 1, wherein the step of running the test code in the test running environment includes a local running mode and/or a cloud running mode, and the local running mode includes: downloading the test code from the cloud to a local computer, and running the test code in test software in the computer to obtain a test result;
The cloud operation mode comprises the following steps: sending an operation request to a cloud, wherein the operation request comprises a user interface to be tested; acquiring a corresponding test code according to the operation request; and receiving a test result obtained by running the test code in the test software of the cloud based on the running request.
5. The method according to claim 4, wherein the test result includes a test report in the form of video, picture, and/or text, and the test report includes a test failure case description, and the test failure case includes an interface jump error and/or an assertion judgment error.
6. The building block type software testing device is characterized by comprising the following modules:
the building block submodule generation module is used for generating a corresponding building block submodule based on a pre-established topological flow chart, and the substantial content of the building block submodule is the topological flow chart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node; before or after establishing the topology flow chart, further comprising obtaining an assertion setting result, wherein the assertion setting result is an expected value set for a display element in the interface node before or after the jump;
The building block diagram generation module is used for selecting at least two building block sub-modules, and connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, wherein in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to a latter building block sub-module in the execution sequence; connecting the building block diagram with one or more building block sub-modules according to the execution sequence to obtain a building block total diagram, or connecting a plurality of building block diagrams according to the execution sequence to obtain the building block total diagram; the parts or all of the building block diagrams and/or the building block total diagrams can be subjected to copying, cutting and/or pasting operations;
the test code generation module is used for compiling the building block total diagram into a test code and comprises the following steps: performing deep traversal on the topology flow chart corresponding to the building block diagram, generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, and referring to a program of an assertion operation after jumping to a pre-jump interface node or a post-jump interface node corresponding to the expected value, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
And the test code running module is used for running the test code in a test running environment to obtain a test result.
7. A building block type software testing device, comprising a processor and a memory, wherein a program is stored in the memory, and the building block type software testing device is characterized in that when the processor executes the program, the following operations are performed:
based on a pre-established topological flow chart, generating a corresponding building block sub-module, wherein the substantial content of the building block sub-module is the topological flow chart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node; before or after establishing the topology flow chart, further comprising obtaining an assertion setting result, wherein the assertion setting result is an expected value set for a display element in the interface node before or after the jump;
selecting at least two building block sub-modules, and connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, wherein in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to a latter building block sub-module in the execution sequence; connecting the building block diagram with one or more building block sub-modules according to the execution sequence to obtain a building block total diagram, or connecting a plurality of building block diagrams according to the execution sequence to obtain the building block total diagram; the parts or all of the building block diagrams and/or the building block total diagrams can be subjected to copying, cutting and/or pasting operations;
Compiling the building block total map into a test code, including: performing deep traversal on the topology flow chart corresponding to the building block diagram, generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, and referring to a program of an assertion operation after jumping to a pre-jump interface node or a post-jump interface node corresponding to the expected value, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
and operating the test code in a test operation environment to obtain a test result.
8. A storage medium storing a program, wherein the program, when executed, performs the operations of:
based on a pre-established topological flow chart, generating a corresponding building block sub-module, wherein the substantial content of the building block sub-module is the topological flow chart; the establishing process of the topological flow chart comprises the following steps: acquiring jump information of a user interface to be tested, wherein the jump information comprises interface nodes before jump, jump elements and interface nodes after jump; establishing a topology flow chart according to the jump information, wherein the topology flow chart comprises a root interface node and one or more branch paths, and each branch path is provided with at least one jump element and a corresponding jump interface node; before or after establishing the topology flow chart, further comprising obtaining an assertion setting result, wherein the assertion setting result is an expected value set for a display element in the interface node before or after the jump;
Selecting at least two building block sub-modules, and connecting the building block sub-modules according to an execution sequence to obtain a building block diagram, wherein in the two building block sub-modules connected, a tail node of a topology flow diagram corresponding to a former building block sub-module is connected with each head node with the same node name as the tail node in the topology flow diagram corresponding to a latter building block sub-module in the execution sequence; connecting the building block diagram with one or more building block sub-modules according to the execution sequence to obtain a building block total diagram, or connecting a plurality of building block diagrams according to the execution sequence to obtain the building block total diagram; the parts or all of the building block diagrams and/or the building block total diagrams can be subjected to copying, cutting and/or pasting operations;
compiling the building block total map into a test code, including: performing deep traversal on the topology flow chart corresponding to the building block diagram, generating a test code corresponding to each complete branch path from a traversal starting node to each complete branch path, and referring to a program of an assertion operation after jumping to a pre-jump interface node or a post-jump interface node corresponding to the expected value, wherein the test code comprises a program for executing user interface jumping operation on each jumping element;
And operating the test code in a test operation environment to obtain a test result.
CN202010128468.4A 2020-02-28 2020-02-28 Building block type software testing method, testing device, testing equipment and storage medium Active CN111124936B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010128468.4A CN111124936B (en) 2020-02-28 2020-02-28 Building block type software testing method, testing device, testing equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010128468.4A CN111124936B (en) 2020-02-28 2020-02-28 Building block type software testing method, testing device, testing equipment and storage medium

Publications (2)

Publication Number Publication Date
CN111124936A CN111124936A (en) 2020-05-08
CN111124936B true CN111124936B (en) 2023-10-31

Family

ID=70493503

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010128468.4A Active CN111124936B (en) 2020-02-28 2020-02-28 Building block type software testing method, testing device, testing equipment and storage medium

Country Status (1)

Country Link
CN (1) CN111124936B (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6426947B1 (en) * 1998-10-21 2002-07-30 Kim K. Banker Apparatus and method for unilateral topology discovery in network management
CN101404596A (en) * 2008-11-17 2009-04-08 福建星网锐捷网络有限公司 Multi-topological environmental test method, system and equipment
CN102662644A (en) * 2012-02-29 2012-09-12 浙江大学 Method for generating test case by using flow chart
CN108075938A (en) * 2016-11-17 2018-05-25 迈普通信技术股份有限公司 A kind of automated testing method and device
CN109857668A (en) * 2019-02-03 2019-06-07 苏州市龙测智能科技有限公司 UI automated function test method, test device, test equipment and storage medium

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6426947B1 (en) * 1998-10-21 2002-07-30 Kim K. Banker Apparatus and method for unilateral topology discovery in network management
CN101404596A (en) * 2008-11-17 2009-04-08 福建星网锐捷网络有限公司 Multi-topological environmental test method, system and equipment
CN102662644A (en) * 2012-02-29 2012-09-12 浙江大学 Method for generating test case by using flow chart
CN108075938A (en) * 2016-11-17 2018-05-25 迈普通信技术股份有限公司 A kind of automated testing method and device
CN109857668A (en) * 2019-02-03 2019-06-07 苏州市龙测智能科技有限公司 UI automated function test method, test device, test equipment and storage medium

Also Published As

Publication number Publication date
CN111124936A (en) 2020-05-08

Similar Documents

Publication Publication Date Title
CN109857667B (en) Interface automation test method, test device, test equipment and storage medium
WO2020155777A1 (en) Ui automated function testing method, testing device, testing apparatus, and storage medium
CN102567198B (en) System and method for testing application program in physical system environment
CN107908542B (en) Test case creating method and device, computer equipment and storage medium
CN111832236B (en) Chip regression testing method and system, electronic equipment and storage medium
CN105138448A (en) Method and device for page test at front end
US20200174917A1 (en) Rapid Automation First-pass Testing Framework
CN109739855B (en) Method and system for realizing data sheet splicing and automatically training machine learning model
CN103597469A (en) Live browser tooling in an integrated development environment
CN109815119B (en) APP link channel testing method and device
CN110362490B (en) Automatic testing method and system for integrating iOS and Android mobile applications
CN103246606A (en) Method and system for testing performances of ESB (enterprises service bus) platform
US20100153919A1 (en) Systems and methods for tracking software stands in a software production landscape
CN104252413A (en) Automatic script generation method, device and system
CN111124936B (en) Building block type software testing method, testing device, testing equipment and storage medium
CN106155665B (en) Conformity evidence-presenting system and method
CN116893822A (en) Workflow engine multi-environment deployment method and system, electronic device and storage medium
CN111008011A (en) System builder for power platform application development
CN116069303A (en) Code generation method, device, equipment and storage medium
CN111221546A (en) Map data and map updating method and device, terminal equipment and server
CN115495374A (en) Method and device for testing asset management
CN101976196A (en) Quality of service oriented code automatic code generating method
CN113377468A (en) Script execution method and device, electronic equipment and storage medium
CN114860566A (en) Source code testing method and device, electronic equipment and storage medium
CN112463126A (en) Software development method based on information technology consulting technology

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
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20220104

Address after: 100000 No. 107, 1st floor, jingyuanju, Cuiwei Nanli, Haidian District, Beijing

Applicant after: Shi Jiangfan

Address before: 215028 unit 2-a310, creative industry park, 328 Xinghu street, Suzhou Industrial Park, Jiangsu Province

Applicant before: SUZHOU DRAGON TESTING INTELLIGENT TECHNOLOGY Co.,Ltd.

GR01 Patent grant
GR01 Patent grant