CN111427760A - Page testing method, device, equipment and storage medium - Google Patents
Page testing method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN111427760A CN111427760A CN201910019677.2A CN201910019677A CN111427760A CN 111427760 A CN111427760 A CN 111427760A CN 201910019677 A CN201910019677 A CN 201910019677A CN 111427760 A CN111427760 A CN 111427760A
- Authority
- CN
- China
- Prior art keywords
- page
- test
- application system
- test case
- tested
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 387
- 238000003860 storage Methods 0.000 title claims abstract description 17
- 238000000034 method Methods 0.000 claims abstract description 50
- 230000009471 action Effects 0.000 claims description 23
- 238000001514 detection method Methods 0.000 claims description 22
- 238000004590 computer program Methods 0.000 claims description 15
- 230000004044 response Effects 0.000 claims description 14
- 230000008569 process Effects 0.000 abstract description 27
- 238000001545 Page's trend test Methods 0.000 description 25
- 238000010586 diagram Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 9
- 238000004088 simulation Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 230000009286 beneficial effect Effects 0.000 description 5
- 238000013461 design Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 4
- 101150071434 BAR1 gene Proteins 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000012216 screening Methods 0.000 description 3
- 238000010998 test method Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000003825 pressing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The embodiment of the application provides a page testing method, a page testing device, page testing equipment and a storage medium. In the page testing method, the test operation of the application system is responded, the test case is automatically generated, then the element to be tested in the application system can be positioned based on the test rule, and the operation of the element to be tested is simulated, so that the dependency of the page testing process on manually compiling the test case can be effectively reduced, the time cost spent on testing the page is reduced, and the page testing efficiency is improved.
Description
Technical Field
The present application relates to the field of internet technologies, and in particular, to a page testing method, apparatus, device, and storage medium.
Background
User interface testing (User interface testing, abbreviated as UI testing) is generally used for testing whether an object on a User interface can complete an expected function, so as to ensure good User experience. In the prior art, the UI test is usually realized by manually writing a test case. However, the time cost required by the UI test method for manually writing test cases is high, especially under the condition of a large number of tested pages. Therefore, a solution is urgently needed.
Disclosure of Invention
Various aspects of the present disclosure provide a page testing method, device, apparatus, and storage medium, which are beneficial to effectively reduce the time cost required for page testing and improve the efficiency of page testing.
The embodiment of the application provides a test method, which comprises the following steps: responding to the test operation of the application system, and generating a test case corresponding to the application system; and running the test case to position the element to be tested in the application system and simulate the operation on the element to be tested.
An embodiment of the present application further provides a testing apparatus, including: the case generating module is used for responding to the test operation of the application system and generating a test case corresponding to the application system; and the test module is used for operating the test case to position the element to be tested in the application system and simulate the operation on the element to be tested.
An embodiment of the present application further provides a page testing device, including: a memory and a processor; the memory is to store one or more computer instructions; the processor is to execute the one or more computer instructions to: responding to the test operation of the application system, and generating a test case corresponding to the application system; and running the test case to position the element to be tested in the application system and simulate the operation on the element to be tested.
The embodiment of the present application further provides a computer-readable storage medium storing a computer program, and the computer program can implement the steps in the page testing method provided by the embodiment of the present application when executed.
The embodiment of the application provides a page testing method, a page testing device, a page testing equipment and a page testing storage medium.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic flowchart of a page testing method according to an exemplary embodiment of the present application;
FIG. 2 is a schematic flowchart of a page testing method according to another exemplary embodiment of the present application;
FIG. 3a is a schematic flowchart of a page testing method according to another exemplary embodiment of the present application;
FIG. 3b is a schematic diagram of a logical structure of an application system provided in accordance with yet another exemplary embodiment of the present application;
FIG. 4 is a schematic flowchart of a page testing method according to another exemplary embodiment of the present application;
FIG. 5 is a schematic structural diagram of a page testing apparatus according to an exemplary embodiment of the present application;
fig. 6 is a schematic structural diagram of a page testing apparatus according to an exemplary embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Aiming at the technical problem that the time cost of page testing is high due to the fact that test cases are manually compiled in the prior art, in some embodiments of the application, a solution is provided, in the solution, the test cases are automatically generated in response to the test operation of an application system, then elements to be tested in the application system can be positioned based on the test rules, and the operation on the elements to be tested is simulated, so that the dependence of a page testing process on the manual compiling of the test cases can be effectively reduced, the time cost spent on testing the page is reduced, and the efficiency of page testing is improved. The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Fig. 1 is a schematic flowchart of a page testing method according to an exemplary embodiment of the present application, and as shown in fig. 1, the method includes:
And 102, running the test case to position the element to be tested in the application system and simulate the operation on the element to be tested.
In this embodiment, the application system may include various websites, an application installed on a computer, an application installed on a mobile smart device, and the like.
The test case refers to a group of test programs compiled for the application system. Generally, a test case may contain preconditions of a test, execution conditions of the test, objects of the test, inputs during the test, and screening rules of expected results, etc. to test whether the application system meets specific requirements.
In this embodiment, in response to the test operation on the application system, the test case corresponding to the application system may be automatically generated. When the test case is operated, the positioning operation aiming at the element to be tested in the application system can be executed, and the operation of the element to be tested can be simulated after the element to be tested is positioned.
The element to be tested may include various controls in the application system, such as a text label, an input box, a progress bar, a button, a dialog box, and the like, and further include elements that can be used as test objects, such as characters, pictures, audio, animation, and video, which are not limited in this embodiment.
The step of positioning the element to be tested in the application system refers to a process of screening the element serving as a test object from the application system.
Generally, the element to be tested in the application system can provide a man-machine interaction function. The simulation of the operation on the element to be tested can be equivalent to the simulation of the operation on the element to be tested by the user in the human-computer interaction process. For example, a user's clicking operation, scrolling operation, long-pressing operation, hovering operation, etc. on the element to be tested are simulated, and it is further possible to test whether the element to be tested meets the user requirements or meets the functional requirements of the application system.
In this embodiment, a test case is automatically generated in response to a test operation on the application system, and then, based on the test rule, an element to be tested in the application system is positioned and an operation on the element to be tested is simulated, so that the dependency of a page test process on manually compiling the test case can be effectively reduced, the time cost spent on testing the page is reduced, and the page test efficiency is improved.
In some exemplary embodiments, the operation of generating the test case corresponding to the application system described in the above embodiments may be implemented based on a pre-configured test rule and a test case template.
The test rule may indicate a test object, a test target, a test method, a test completion standard and/or a test result output requirement, which is not limited to this embodiment. The test rule may be set by a user according to the characteristics and/or the test requirements of the application system, which is not limited in this embodiment.
The test case template may include necessary formats and necessary contents of test cases, general parameters required for testing different objects, and the like, and may be pre-written by a user according to test experience. In the process of page testing, the test case template can be configured by combining the pre-configured test rule, so that the test case meeting the test requirement of the application system is automatically generated, and the time cost required by page testing is reduced. After the test case corresponding to the application system is automatically generated, the test case is operated, so that the element to be tested contained in the application system can be positioned, and the operation on the element to be tested is simulated. As will be described in detail below.
Fig. 2 is a schematic flowchart of a page testing method according to another exemplary embodiment of the present application, and as shown in fig. 2, the method includes:
And step 204, identifying an error result from the result of simulating the operation on the element to be tested according to the error identification parameters in the test case, and taking the error result as a test result.
Optionally, the page testing method provided by this embodiment may be implemented by a page testing device. The page test device includes an electronic device capable of running a test case, such as a computer or a server, and the present embodiment is not limited thereto.
In step 201, the test operation on the application system may be initiated by the user or initiated by the page test device.
In some optional embodiments, the page testing device may consider that the user initiates the test operation on the application system when detecting the setting operation of the page testing device by the user. For example, a test icon may be displayed on the page test device, and when a trigger operation of the user on the test icon is detected, the page test device may consider that the user initiates a test operation for the application system. In other alternative embodiments, the page testing device may automatically initiate a testing operation for the application system according to a set testing period, which is not limited in this embodiment.
Optionally, in this embodiment, the test rule may include: element matching rules, element operation rules, and error recognition rules.
First, an element matching rule is exemplified with reference to a specific example.
The element matching rule is used for indicating which elements in the application system are used as test objects to be tested. For example, the element matching rules may include: buttons on the matching page, text labels with links on the matching page, scroll bars on the matching page, menu bar controls on the matching page, and so forth.
In some exemplary embodiments, the element matching rules may be automatically configured by the page test device according to common element matching rules in the page test process. For example, common element matching rules in a page test process may include: all controls on the page are matched.
In other exemplary embodiments, the element matching rules may be custom configured by the user. In the embodiment, a user can define part of elements in the application system as test objects, so that the page test equipment can execute page test operation with high pertinence, and the page test efficiency is improved.
Alternatively, the user may configure the positioning path of the partial element as an element matching rule.
In such an embodiment, optionally, the user may configure the location Path of an element based on Xpath (XM L Path L anguage ). XPath, a language used to determine nodes in an XM L document.XPath uses a Path expression to pick a node or set of nodes in an XM L document.
Alternatively, the user may configure the attributes of some elements as element matching rules. The attributes of the element include, but are not limited to, the type, name, ID, style, etc. of the element. For example, the user-configurable element matching rule is: the element on the matching page is an element of which the type is button, the name is "ok", the ID is "button 1", and the background color is gray.
In such an embodiment, the operation of the user to configure the attributes of the elements may optionally be implemented by a CSS (cascading style Sheets) selector. The user may configure at least one of a type, name, ID, and style of the element in the CSS selector.
Besides the above two implementation manners, the user may also use the positioning path and the attribute of a part of the elements as the element matching rule at the same time to improve the accuracy of element matching, which is not described again.
Next, the element operation rule is exemplarily described with reference to a specific example.
And the element operation rule indicates what operation needs to be performed on the element in the test process. In general, an operation rule of an element may consist of a correspondence of the element and an operation action. In this embodiment, the operation actions include, but are not limited to: one or more of a single click, a double click, a long press, a scroll, a move, and an input action.
In some exemplary embodiments, the element operation rules may be automatically configured by the page test equipment according to common element operation rules in the page test process. Generally, the general element operation rule in the page test process describes the corresponding relation between elements and operation actions with a larger classification granularity. For example, the common element operation rules may include: executing click operation on the elements with the element types of the buttons on the page; performing single click operation on the elements with the element types of the text labels with the links on the page; and executing the scrolling operation on the elements of which the element types are scroll bars on the page.
In other exemplary embodiments, the element operation rules may be custom configured by the user according to the test requirements. Compared with the scheme of automatically configuring according to the general element operation rule, when the user configures the element operation rule in a self-defining way, according to the test requirement, the description information associated with the elements except the element types can be added to further refine the element classification granularity, and/or the description information associated with the operations except the operation types can be added to further refine the operation classification granularity according to the test requirement.
Other description information associated with the element may include, among other things, the ID of the element, the name of the element, the style of the element, the layout position of the element on the page, etc. Other descriptive information associated with the operation may include the number of operations, the manner of clicks (e.g., left mouse click, right mouse click), the magnitude of scrolling, and so forth. Based on the embodiment, the user can further refine the rule of the page test, and can even define the specific operation performed on which element in a one-to-one manner, thereby being beneficial to realizing accurate test.
For example, a user may customize a configuration element operation rule as: performing left-click operation on the elements with the element type of 'button', the name of 'confirmed', the ID of 'button 1' and the background color of 'grey' on the page; performing right-click operation on the element with the element type of 'button', the name of 'cancel', the ID of 'button 2' and the background color of 'white' on the page; and performing left-click operation on the element with the type of the linked text label, the name of directory 1, the ID of label0 and the font of regular script on the label.
Next, the error recognition rule will be exemplarily described with reference to a specific example.
After simulating the operation on an element to be tested, if the element to be tested meets the design requirement or the functional requirement of the application system, the result of the simulation operation on the element to be tested is a correct operation result; otherwise, the result of performing the simulation operation on the operation is an erroneous operation result. And the error identification rule is used for indicating that the simulation operation result of which elements to be tested is identified is an error operation result so as to generate a test result for a user to check.
In some exemplary embodiments, the fault identification rules may be automatically configured according to common fault identification rules in the page testing process. For example, the generic error recognition rules may include: identifying an operation result that is not responsive to the simulation operation, and/or identifying an operation result that is responsive to the simulation operation for a timeout.
For example, the user can configure the error recognition rule as an operation result of identifying that the button is not responsive when clicking the button named ' ok ', an operation result of identifying that the scroll bar is not scrolled when scrolling the scroll bar with the color of ' grey ', and an operation result of identifying that the page pointed by the link L1 is not entered when clicking the text label with the link L1 ', which are not described in detail.
After the pre-configured element matching rules, element operation rules, and error identification rules are obtained, step 202 may be executed: setting element positioning parameters in the test case template according to the element matching rule; setting element action parameters in the test case template according to the element operation rules; and setting the error identification parameters in the test case template according to the error identification rule to obtain the test case corresponding to the application system.
The element positioning parameters are used for positioning the element to be tested in the application system in the process of executing the test case; the element action parameters are used for simulating the target operation of the element to be tested in the process of executing the test case; and the error identification parameters are used for screening out results which do not meet the requirements of users, the design initiatives of the application system or the functional requirements of the application system from the results of simulating the operation on the elements to be detected.
Optionally, one way of configuring the element location parameters in the test case template according to the element matching rule is as follows: taking the element matching rule as the value of the element positioning parameter; for example, if the user passes through the Xpath configuration element, the location path is: page a 0/menu bar1, the positioning path "page a 0/menu bar 1" can be used as the value of the element positioning parameter, so that when the test case is run, the menu bar1 on the page a0 is positioned as the element to be tested.
Optionally, one way of configuring the element action parameters in the test case template according to the element operation rules is as follows: and taking the element operation rule as the value of the element action parameter. For example, if the element operation rule configured by the user is: when the button B1 is clicked, the "correspondence between the button B1 and the clicking operation" may be used as the value of the element action parameter, so that when the test case is run, the button B1 is used as the object to be tested, and the button B1 is clicked.
Optionally, one way of configuring the error recognition parameters in the test case template according to the error recognition rule is as follows: and taking the error identification rule as the value of the error identification parameter. For example, if the user configures the misidentification rule as: identifying an operation result that the button has no response when the button named button1 is clicked; it is possible to use "the operation result identifying no response of the button when the button named button1 is clicked" as the value of the error identification parameter, to judge whether or not the button named button1 is responded when the test case is run, and to record information such as the name, ID, or screen shot of the button when the button is not responded, and output the information as the error operation result.
After the test case corresponding to the application system is generated based on the above steps, step 203 may be executed to run the test case corresponding to the application system. In the process of running the test case, the page test equipment can take the element matched with the element positioning parameter in the test case as the element to be tested, simulate and execute the corresponding operation action according to the element action parameter in the test case, and recognize the error result from the simulation operation result according to the error recognition parameter in the test case.
In this embodiment, a test operation on an application system is responded, a pre-configured test rule is obtained, then a test case corresponding to the application system can be automatically generated based on the test rule and a test case template, the test case is operated to position an element to be tested in the application system, and the operation on the element to be tested is simulated, so that the dependency of a page test process on manual compiling of the test case can be effectively reduced, the time cost spent on testing a page is reduced, and the page test efficiency is improved.
In addition, the mode of configuring the test case template can be quickly copied to various different application systems to execute page detection operation through simple configuration, and is beneficial to reducing the development cost and the maintenance cost of page testing.
In some typical application scenarios, the test requirements of the user are: and testing part of elements contained in the application system. For example, when the application system is a website, the user needs to test elements in certain channels of the website or test elements on certain pages of the website. Under the requirement, the application also provides a page testing method, which can take the page as a testing unit and is used for flexibly completing the testing requirement on partial elements. As will be described in detail below.
Fig. 3a is a schematic flowchart of a page testing method according to another exemplary embodiment of the present application, and as shown in fig. 3a, the method includes:
And step 302, respectively setting element positioning parameters, element action parameters and error identification parameters in the test case template according to the element matching rules, the element operation rules and the error identification rules contained in the test rules to obtain the test case corresponding to the application system.
And 303, acquiring the logic structure description information of the application system according to a preset page detection rule.
For optional implementation of step 301 and step 302, reference may be made to the descriptions of the foregoing embodiments, which are not repeated herein.
In step 303, the logical structure refers to a structure determined by a logical relationship inside the website or the application. In some embodiments, the logical structure may optionally represent a link relationship between pages contained by a website or application.
The following description will be exemplified by taking a video website as an example. Assume that channel page a1 and channel page a2 of a video website are accessible through the home page a0 of the website. Video content page a11 or video content page a12 is accessible through channel page a 1. Video content page a21 or video content page a22 is accessible through channel page a 2. This structure of linking to channel page a1 and channel page a2 by home page a0, video content page a11 and video content page a12 by channel page a1, and video content page a21 and video content page a22 by channel page a2 can be described as a logical structure of a video website.
In this embodiment, the location information of the page includes a name of the page, a UR L (Uniform Resource L locator) of the page, and/or attributes of elements linked to the page, and the like.
In this embodiment, the page test device may detect the logical structure of the application system according to the page detection rule, and generate the logical structure description information according to the detection result. In this embodiment, the logic structure description information may describe all logic structures of the application system, or may describe only a part of logic structures of the application system, depending on contents included in the page detection rule, which is not limited herein.
Optionally, in this embodiment, the page detection rule may be automatically configured by the page testing device according to a general page detection rule in the page testing process. Wherein, the general page detection rule can be expressed as: and scanning all elements linked to the pages in the application system to detect all pages contained in the application system, and recording the link relation between the pages.
Optionally, the page detection rule can also be configured by the user according to the test requirement in a customized manner. Optionally, in such an embodiment, the user may custom configure the attributes of the elements linked to the page as page detection rules. Optionally, the attributes of the elements linked to the page may include: the type, name, ID, style, link pointed to, etc. of the element, including but not limited to this embodiment. Wherein the types of elements may include: text, images, animations, video music, hyperlinks, forms, and miscellaneous controls, and the like. In some scenarios, when the application system is a website, the user may configure the attributes of the elements through the CSS selector, which is not described again.
In some exemplary embodiments, for a website, a user may custom configure the attributes of anchor elements (anchor elements) linked to a page as page detection rules. The anchor element is used to specify a hyperlink reference (href) that is displayed on the web page. Where the hyperlink corresponding to the anchor element begins with an < a > tag and ends with a </a > tag, the text of the clicked hyperlink between the beginning and ending < a > tags is often referred to as the anchor element.
Based on the page detection rule, the page testing equipment can scan the application system according to the page detection rule and screen out the anchor elements which meet the attribute configured by the user from the application system. And then, simulating a click event aiming at the screened anchor elements, and acquiring the logic structure description information of the application system according to the response result of the click event.
The response result of the click event may include: whether the anchor element can respond to the click or not and whether the anchor element enters the next page after the click. If an anchor element enters the next page in response to a click event, it can be determined that a link relationship exists between the page where the anchor element is located and the next page entered after clicking the anchor element. At this time, the positioning information of the page where the anchor element is located and the positioning information of the next page may be obtained, and the logical structure description information of the website may be generated by combining the link relationship.
Alternatively, the logical structure of the application system may be described in JSON (JSON object notation) format to generate logical structure description information. The JSON format is easy to read and write, and is easy to analyze and generate by a machine, thereby being beneficial to effectively improving the reading and writing efficiency of the logic structure description information.
How to obtain the logical structure description information of the application system will be described below with reference to specific examples.
For example, as shown in FIG. 3 b: in a certain website, three gray a tags (anchor elements) are shown at the top column of the home page, and the names are respectively: "top rail 1", "top rail 2", and "top rail 3". Wherein, the a label named as "top bar 1" is linked to the first channel page, the side bar of the first channel page contains 3 gray a labels that can be linked to different content pages, and the names are respectively: "sidebar1-1", "sidebar1-2" and "sidebar 1-3". The a-tag named "top bar 2" is connected to the second channel page, which contains 1 gray a-tag on the sidebar that can be linked to the content page, the names are: "sidebar 2-1". The a-tag named "top column 3" is connected to a third channel page, and the side column of the third channel page contains 2 gray a-tags that can be linked to different content pages, and the names are: "sidebar3-1" and "sidebar 3-2".
Assume that the page detection rule configured by the user through the CSS selector is: gray a tags linked to the page are detected. Then, the logical structure of the application system that can be detected by the page testing device according to the page detection rule may be:
the home page is linked to the first channel page, the second channel page, and the third channel page. The first channel page is linked to the first content page, the second content page, and the third content page. The second channel page is linked to a fourth content page. The third channel page is linked to the fifth and sixth content pages.
When the above logic structure is described in JSON format, the obtained logic structure description information may be:
[ { "header name1": top bar 1"," sidebars ": {" sidebar1-1": {" name ": side bars 1-1", "href": http:// xx.1.html "} } ], wherein http:// xx.1.html is UR L of the first content page.
[ { "header name1": top bar 1"," sidebars ": {" sidebar1-2": {" name ": side bars 1-2", "href": http:// xx.2.html "} } ], wherein http:// xx.2.html is UR L of the second content page.
[ { "header name1": top bar 1"," sidebars ": {" sidebar1-3": {" name ": side bars 1-3", "href": http:// xx.3.html "} } ], wherein http:// xx.3.html is UR L of the third content page.
[ { "headername2": top bar 2"," sidebars ": {" sidebars 2-1": {" name ": side bars 2-1", "href": http:// xx.4.html "} } ], wherein http:// xx.4.html is UR L of the fourth content page.
[ { "headername3": top bar 3"," sidebars ": {" sidebars 3-1": {" name ": side bars 3-1", "href": http:// xx.5.html "} } ], wherein http:// xx.5.html is UR L of the fifth content page.
[ { "headername3": top bar 3"," sidebars ": {" sidebars 3-2": {" name ": side bars 3-1", "href": http:// xx.6.html "} } ], wherein http:// xx.6.html is UR L of the sixth content page.
After the logical structure description information of the application system is obtained, step 304 may be executed to determine the positioning information of at least one page included in the application system from the logical structure description information.
For example, in the above example, the positioning information of the first channel page may be the name of the a-tag linked to the first channel page, i.e. the top bar1, and the positioning information of the first content page may be the name of the a-tag linked to the first content page, i.e. the side bar1-1, or may also be the UR L corresponding to the first content page.
After the positioning information of at least one page included in the application system is determined, step 305 may be executed to configure the page positioning parameters in the test case corresponding to the application system according to the positioning information of the at least one page, so as to divide the test case corresponding to the application system into at least one test case corresponding to the at least one page.
When the at least one page comprises a plurality of pages, the page positioning parameters in the test cases can be configured according to the positioning information of the pages respectively, so as to generate the test cases corresponding to the pages.
For example, bearing the above example, the name of the a-tag linked to the first channel page may be used as the value of the page positioning parameter in the test case, so as to obtain the first test case corresponding to the first channel page.
In step 306, optionally, one or more test cases generated in the above steps may be run concurrently to locate the elements to be tested on one or more pages and simulate operations on the elements to be tested on the one or more pages.
For example, in connection with the above example, the page testing device may run the first test case corresponding to the first channel page, and in the running process, locate the first channel page from the application system according to the value of the page location parameter in the first test case, locate the element to be tested on the first channel page according to the element location parameter in the first test case, and simulate the operation on the element to be tested on the first channel page according to the element action parameter in the first test case.
Meanwhile, the page testing equipment can also operate a second test case corresponding to the first content page, position the first content page from the application system according to the value of the page positioning parameter in the second test case in the operation process, position the element to be tested on the first content page according to the element positioning parameter in the second test case, and simulate the operation on the element to be tested on the first content page according to the element action parameter in the second test case.
In this embodiment, in addition to automatically generating the test case corresponding to the application system according to the configured test rule, the logic structure of the application system may be further obtained, and according to the logic structure, the test case corresponding to the page included in the application system may be automatically generated, and further, in the test process, the page may be used as a test unit, the test granularity is refined, the test operation on the elements on the page surface is flexibly completed, and the page test efficiency is improved.
Fig. 4 is a schematic flowchart of a page testing method according to another exemplary embodiment of the present application, and as shown in fig. 4, the method includes:
And 403, acquiring the logic structure description information of the application system according to the preset page detection rule.
And 406, grouping the at least one page according to the page hierarchy relationship contained in the logical structure description information to obtain at least one group of pages.
And 408, grouping and outputting the test results obtained by running the test cases corresponding to the at least one group of pages according to the grouping condition of the at least one group of pages.
For alternative implementation of steps 401 to 405, reference may be made to the descriptions of the foregoing embodiments, which are not repeated herein.
In step 406, the description of the logic structure description information may refer to the description of the foregoing embodiments, which are not repeated herein. The page hierarchy relationship can be expressed as a classification directory under the classification hierarchy to which the page belongs.
When the application system includes an N-level classification level, pages may be grouped according to the classification categories under the level one, level two …, and the N-level classification level to which the pages belong. The value of N depends on actual requirements, and N is a positive integer.
For example, when the first-level classification level of an application system includes three classification directories, if pages are classified according to the first-level classification level to which the pages belong, the pages under the three classification directories may be divided into three page groups, respectively. When the secondary classification level of the application system includes six classification directories, if the pages are classified according to the secondary classification level to which the pages belong, the pages under the six classification directories can be respectively divided into six page groups.
Next, a description will be given taking a website as an example.
In a common website design, the logical structure of the website is divided into three classification levels, a first page, a column page and a content page, and each classification level may include a plurality of classification directories. The first page is a first classification level and can contain a classification catalogue of a plurality of column pages; column pages are a second classification level, and each column page can contain a plurality of classification catalogues of content pages; the content detail page is a third classification level. Of course, in other web site design manners, the logic structure of the web site may be designed into four levels, five levels or even more levels according to the application requirement, which is not limited in this embodiment. Based on the classification, the pages can be grouped according to the first classification level, the second classification level or the third classification level of the pages in the website.
Taking the website shown in fig. 3b as an example, the "top bar" is a classification directory included in the first level of the website, and when the pages are classified by the first classification level to which the pages belong, the pages can be divided into the same number of page groups as the "top bar", that is: dividing a first channel page and a first content page, a second content page and a third content page which have a link relation with the first channel page into a first group of pages; dividing the second channel page and a fourth content page which has a link relation with the second channel page into a second group of pages; and dividing the third channel page and the fifth content page and the sixth content page which have link relation with the third channel page into a third group of pages.
Continuing with fig. 3b as an example, the "sidebar" is a classification directory included in the second level of the website, and if the pages are classified according to the second classification level to which the pages belong, the pages can be divided into page groups with the same number as the sidebar, that is: the first content page, the second content page, the third content page, the fourth content page, the fifth content page and the sixth content page are divided into different groups respectively, and six groups of pages are obtained.
After obtaining the at least one group of pages, step 407 is executed to run the test cases corresponding to the at least one group of pages in a concurrent manner, so as to simulate the operation on the elements to be tested on the at least one group of pages. For example, the test cases corresponding to the first group of pages, the second group of pages, and the third group of pages may be run concurrently in accordance with the above example. Furthermore, the efficiency of page testing can be effectively improved and the time cost required by page testing can be reduced by the concurrent testing mode.
It should be noted that, in step 408, after the test results obtained by concurrently running the test cases corresponding to the at least one group of pages are obtained, the obtained test results may be grouped and output according to the grouping condition of the at least one group of pages. For example, a test result obtained by running a test case corresponding to the first group of pages is taken as a first group of test results and output; taking a test result obtained by running the test case corresponding to the second group of pages as a second group of test results and outputting the second group of test results; and taking the test result obtained by running the test case corresponding to the third group of pages as the third group of test result and outputting the third group of test result. The mode of outputting the test results in a grouping manner is beneficial for a user to quickly determine the page corresponding to the test results according to the logic structure of the application system, and the efficiency of analyzing the test results by the user is improved.
In this embodiment, after the logic structure of the application system is obtained, at least one test case corresponding to at least one page included in the application system is grouped according to the logic structure, and then, in the test process, multiple groups of test cases can be concurrently executed according to the logic structure of the application system, thereby further improving the page test efficiency.
It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subjects of step 201 to step 204 may be device a; for another example, the execution subject of steps 201 and 202 may be device a, and the execution subject of step 203 may be device B; and so on.
In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 201, 202, etc., are merely used for distinguishing different operations, and the sequence numbers do not represent any execution order per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.
In the above, the optional implementation of the page testing method is described, and in practice, the page testing method may be implemented by a page testing apparatus, as shown in fig. 5, the page testing apparatus includes:
a use case generating module 501, configured to generate a test use case corresponding to an application system in response to a test operation on the application system; the test module 502 is configured to run the test case to locate the element to be tested in the application system and simulate an operation on the element to be tested.
Further optionally, when the use case generating module 501 generates a test case corresponding to the application system, it is specifically configured to: and setting parameters of the test case template based on a pre-configured test rule to obtain a test case corresponding to the application system.
Further optionally, the use case generating module 501 is specifically configured to, when setting parameters of the test case template based on the preconfigured test rule to obtain the test case corresponding to the application system: and respectively setting element positioning parameters, element action parameters and error identification parameters in the test case template according to an element matching rule, an element operation rule and an error identification rule contained in the test rule so as to obtain the test case corresponding to the application system.
Further optionally, when the test module 502 runs the test case to locate the element to be tested in the application system and simulate the operation on the element to be tested, the test case is specifically configured to: running the test case to match the element to be tested from the application system according to the element positioning parameters in the test case; simulating the operation of the element to be tested according to the element action parameter in the test case; and identifying an error result from a result of simulating the operation on the element to be tested according to the error identification parameter in the test case, wherein the error result is used as a test result.
Further optionally, the use case generation module 501 is further configured to: dividing the test case corresponding to the application system into at least one test case; the at least one test case corresponds to at least one page contained in the application system respectively; the test module 502 is further configured to: and running the at least one test case in a concurrent mode to position the element to be tested on the at least one page and simulate the operation on the element to be tested on the at least one page.
Further optionally, when the use case generation module 501 divides the test case corresponding to the application system into at least one test case, it is specifically configured to: acquiring logic structure description information of the application system according to a preset page detection rule; determining the positioning information of at least one page contained in the application system from the logic structure description information; and setting page positioning parameters in the test case corresponding to the application system according to the positioning information of the at least one page, so as to divide the test case corresponding to the application system into at least one test case.
Further optionally, the use case generation module 501 is further configured to: grouping the at least one page according to the page hierarchy relation contained in the logic structure description information to obtain at least one group of pages; the test module 502 is further configured to: and running the test cases corresponding to the at least one group of pages in a concurrent mode to simulate the operation on the elements to be tested on the at least one group of pages.
Further optionally, the testing module 502 is further configured to: and according to the grouping condition of the at least one group of pages, grouping and outputting the test results obtained by running the test cases corresponding to the at least one group of pages.
Further optionally, when the use case generating module 501 obtains the logical structure description information of the application system according to the pre-configured page detection rule, the use case generating module is specifically configured to: acquiring attribute information of an anchor element set by a user; scanning the anchor elements in the application system according to the attribute information of the anchor elements, and simulating click events aiming at the anchor elements; and acquiring the hierarchical relationship among the pages contained in the application system according to the response result of the click event so as to acquire the logic structure description information.
In this embodiment, the page testing apparatus can respond to the test operation of the application system, automatically generate the test case, then locate the element to be tested in the application system based on the test rule, and simulate the operation on the element to be tested, thereby effectively reducing the dependency of the page testing process on manually compiling the test case, reducing the time cost spent on testing the page, and improving the efficiency of the page testing.
The above embodiments describe the module structure and functions of each module of the page testing apparatus, and in some embodiments, the page testing apparatus may be implemented as a page testing device, as shown in fig. 6, the page testing device includes: a memory 601 and a processor 602.
The memory 601 is used for storing computer programs and can be configured to store other various data to support operations on the page test device. Examples of such data include instructions for any application or method operating on the page testing device, contact data, phonebook data, messages, pictures, videos, and the like.
The memory 601 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
A processor 602, coupled to the memory 601, for executing the computer programs in the memory 601 to: responding to the test operation of the application system, and generating a test case corresponding to the application system; and running the test case to position the element to be tested in the application system and simulate the operation on the element to be tested.
Further optionally, when the processor 602 generates a test case corresponding to the application system, it is specifically configured to: and setting parameters of the test case template based on a pre-configured test rule to obtain a test case corresponding to the application system.
Further optionally, when the processor 602 sets parameters of the test case template based on the preconfigured test rule to obtain the test case corresponding to the application system, specifically, the processor is configured to: and respectively setting element positioning parameters, element action parameters and error identification parameters in the test case template according to an element matching rule, an element operation rule and an error identification rule contained in the test rule so as to obtain the test case corresponding to the application system.
Further optionally, when the processor 602 runs the test case to locate the element to be tested in the application system and simulate an operation on the element to be tested, the method specifically includes: running the test case to match the element to be tested from the application system according to the element positioning parameters in the test case; simulating the operation of the element to be tested according to the element action parameter in the test case; and identifying an error result from a result of simulating the operation on the element to be tested according to the error identification parameter in the test case, wherein the error result is used as a test result.
Further optionally, the processor 602 is further configured to: dividing the test case corresponding to the application system into at least one test case; the at least one test case corresponds to at least one page contained in the application system respectively; and running the at least one test case in a concurrent mode to position the element to be tested on the at least one page and simulate the operation on the element to be tested on the at least one page.
Further optionally, when the processor 602 divides the test case corresponding to the application system into at least one test case, the following steps are specifically performed: acquiring logic structure description information of the application system according to a preset page detection rule; determining the positioning information of at least one page contained in the application system from the logic structure description information; and setting page positioning parameters in the test case corresponding to the application system according to the positioning information of the at least one page, so as to divide the test case corresponding to the application system into at least one test case.
Further optionally, the processor 602 is further configured to: grouping the at least one page according to the hierarchical level relation contained in the logic structure description information to obtain at least one group of pages; and running the test cases corresponding to the at least one group of pages in a concurrent mode to simulate the operation on the elements to be tested on the at least one group of pages.
Further optionally, the processor 602 is further configured to: and according to the grouping condition of the at least one group of pages, grouping and outputting the test results obtained by running the test cases corresponding to the at least one group of pages.
Further optionally, when the processor 602 acquires the logical structure description information of the application system according to the preconfigured page detection rule, specifically configured to: acquiring attribute information of an anchor element set by a user; scanning the anchor elements in the application system according to the attribute information of the anchor elements, and simulating click events aiming at the anchor elements; and acquiring the hierarchical relationship among the pages contained in the application system according to the response result of the click event so as to acquire the logic structure description information.
Further, as shown in fig. 6, the page test apparatus may further include: communication components 603, display 604, power components 605, and the like. Only some of the components are schematically shown in fig. 6, and it is not meant that the page test apparatus includes only the components shown in fig. 6.
Wherein the communication component 603 is configured to facilitate communication between the device in which the communication component is located and other devices in a wired or wireless manner. The device in which the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G, 3G, 4G, 5G, and the like, or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component may be implemented based on Near Field Communication (NFC) technology, Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
The display 604 includes a screen, which may include a liquid crystal display (L CD) and a Touch Panel (TP). if the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user.
The power supply 605 is used to provide power to various components of the device in which the power supply is located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.
In this embodiment, the page testing apparatus can respond to the test operation of the application system, automatically generate the test case, then locate the element to be tested in the application system based on the test rule, and simulate the operation on the element to be tested, thereby effectively reducing the dependency of the page testing process on manually compiling the test case, reducing the time cost spent on testing the page, and improving the efficiency of the page testing.
Accordingly, the present application further provides a computer-readable storage medium storing a computer program, where the computer program can implement the steps in the page testing method that can be executed by the page testing device in the above method embodiments when executed.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, 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, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (12)
1. A page testing method is characterized by comprising the following steps:
responding to the test operation of the application system, and generating a test case corresponding to the application system;
and running the test case to position the element to be tested in the application system and simulate the operation on the element to be tested.
2. The method of claim 1, wherein generating the test case corresponding to the application system comprises:
and setting parameters of the test case template based on a pre-configured test rule to obtain a test case corresponding to the application system.
3. The method of claim 2, wherein setting parameters of a test case template based on a pre-configured test rule to obtain a test case corresponding to the application system comprises:
and respectively setting element positioning parameters, element action parameters and error identification parameters in the test case template according to an element matching rule, an element operation rule and an error identification rule contained in the test rule so as to obtain the test case corresponding to the application system.
4. The method of claim 3, wherein running the test case to locate an element under test in the application system and simulate an operation on the element under test comprises:
running the test case to match the element to be tested from the application system according to the element positioning parameters in the test case;
simulating the operation of the element to be tested according to the element action parameters in the test case; and the number of the first and second groups,
and identifying an error result from a result of simulating the operation on the element to be tested according to the error identification parameter in the test case, and taking the error result as a test result.
5. The method according to any one of claims 1-4, further comprising:
dividing the test case corresponding to the application system into at least one test case; the at least one test case corresponds to at least one page contained in the application system respectively;
and running the at least one test case in a concurrent mode to position the elements to be tested on the at least one page and simulate the operation on the elements to be tested on the at least one page.
6. The method according to claim 5, wherein dividing the test case corresponding to the application system into at least one test case comprises:
acquiring logic structure description information of the application system according to a preset page detection rule;
determining positioning information of at least one page contained in the application system from the logic structure description information;
and setting page positioning parameters in the test cases corresponding to the application system according to the positioning information of the at least one page, so as to divide the test cases corresponding to the application system into at least one test case.
7. The method of claim 5, further comprising:
grouping the at least one page according to a page hierarchy relation contained in the logic structure description information to obtain at least one group of pages;
and running the test cases corresponding to the at least one group of pages in a concurrent mode to simulate the operation on the elements to be tested on the at least one group of pages.
8. The method of claim 7, further comprising:
and grouping and outputting the test results obtained by running the test cases corresponding to the at least one group of pages according to the grouping condition of the at least one group of pages.
9. The method of claim 5, wherein obtaining the logical structure description information of the application system according to the pre-configured page detection rule comprises:
acquiring attribute information of an anchor element set by a user;
according to the attribute information of the anchor elements, scanning the anchor elements in the application system, and simulating click events aiming at the anchor elements;
and acquiring the hierarchical relationship among the pages included in the application system according to the response result of the click event so as to acquire the logic structure description information.
10. A page testing apparatus, comprising:
the case generating module is used for responding to the test operation of the application system and generating a test case corresponding to the application system;
and the test module is used for operating the test case to position the element to be tested in the application system and simulate the operation on the element to be tested.
11. A page testing apparatus, comprising: a memory and a processor;
the memory is to store one or more computer instructions;
the processor is to execute the one or more computer instructions to: responding to the test operation of the application system, and generating a test case corresponding to the application system; and running the test case to position the element to be tested in the application system and simulate the operation on the element to be tested.
12. A computer-readable storage medium storing a computer program, wherein the computer program is capable of implementing the page testing method of any one of claims 1 to 9 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910019677.2A CN111427760A (en) | 2019-01-09 | 2019-01-09 | Page testing method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910019677.2A CN111427760A (en) | 2019-01-09 | 2019-01-09 | Page testing method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111427760A true CN111427760A (en) | 2020-07-17 |
Family
ID=71545658
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910019677.2A Pending CN111427760A (en) | 2019-01-09 | 2019-01-09 | Page testing method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111427760A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930629A (en) * | 2020-08-14 | 2020-11-13 | 工银科技有限公司 | Page testing method and device, electronic equipment and storage medium |
| CN113485880A (en) * | 2021-07-12 | 2021-10-08 | 浙江网商银行股份有限公司 | Test method and device |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102609352A (en) * | 2011-01-19 | 2012-07-25 | 阿里巴巴集团控股有限公司 | Parallel testing method and parallel testing server |
| US20130117611A1 (en) * | 2011-11-09 | 2013-05-09 | Tata Consultancy Services Limited | Automated test execution plan derivation system and method |
| CN104133765A (en) * | 2013-12-23 | 2014-11-05 | 腾讯科技（深圳）有限公司 | Test case sending method and test case server of network activities |
| CN104679658A (en) * | 2015-03-17 | 2015-06-03 | 百度在线网络技术（北京）有限公司 | Test method and test system for WEB pages |
| US9304893B1 (en) * | 2013-03-08 | 2016-04-05 | Emc Corporation | Integrated software development and test case management system |
| US20160196021A1 (en) * | 2015-01-05 | 2016-07-07 | International Business Machines Corporation | Automated Modularization of Graphical User Interface Test Cases |
| CN106155877A (en) * | 2015-03-23 | 2016-11-23 | Tcl集团股份有限公司 | A kind of fuzz testing method and system of Android application |
| CN106294107A (en) * | 2015-05-27 | 2017-01-04 | 富士通株式会社 | The method and apparatus generating the test case of Webpage |
| CN106547689A (en) * | 2016-10-20 | 2017-03-29 | 金航数码科技有限责任公司 | A kind of automatic test cases development system and method based on web |
| CN106991045A (en) * | 2017-03-24 | 2017-07-28 | 广州酷狗计算机科技有限公司 | Page method of calibration and device |
| CN107122301A (en) * | 2017-04-27 | 2017-09-01 | 武汉斗鱼网络科技有限公司 | Interface detection method and device |
| CN107704392A (en) * | 2017-09-30 | 2018-02-16 | 华为技术有限公司 | The processing method and server of a kind of test case |
| CN108197026A (en) * | 2017-12-30 | 2018-06-22 | 北京金风科创风电设备有限公司 | Method, device and equipment for testing simulation software of wind generating set and storage medium |
| CN109032943A (en) * | 2018-07-26 | 2018-12-18 | 威创软件南京有限公司 | A method of it is concurrently executed based on robot framework test case |
| CN109144863A (en) * | 2018-08-10 | 2019-01-04 | 广东电网有限责任公司信息中心 | A kind of automated testing method based on network system |
-
2019
- 2019-01-09 CN CN201910019677.2A patent/CN111427760A/en active Pending
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102609352A (en) * | 2011-01-19 | 2012-07-25 | 阿里巴巴集团控股有限公司 | Parallel testing method and parallel testing server |
| US20130117611A1 (en) * | 2011-11-09 | 2013-05-09 | Tata Consultancy Services Limited | Automated test execution plan derivation system and method |
| US9304893B1 (en) * | 2013-03-08 | 2016-04-05 | Emc Corporation | Integrated software development and test case management system |
| CN104133765A (en) * | 2013-12-23 | 2014-11-05 | 腾讯科技（深圳）有限公司 | Test case sending method and test case server of network activities |
| US20160196021A1 (en) * | 2015-01-05 | 2016-07-07 | International Business Machines Corporation | Automated Modularization of Graphical User Interface Test Cases |
| CN104679658A (en) * | 2015-03-17 | 2015-06-03 | 百度在线网络技术（北京）有限公司 | Test method and test system for WEB pages |
| CN106155877A (en) * | 2015-03-23 | 2016-11-23 | Tcl集团股份有限公司 | A kind of fuzz testing method and system of Android application |
| CN106294107A (en) * | 2015-05-27 | 2017-01-04 | 富士通株式会社 | The method and apparatus generating the test case of Webpage |
| CN106547689A (en) * | 2016-10-20 | 2017-03-29 | 金航数码科技有限责任公司 | A kind of automatic test cases development system and method based on web |
| CN106991045A (en) * | 2017-03-24 | 2017-07-28 | 广州酷狗计算机科技有限公司 | Page method of calibration and device |
| CN107122301A (en) * | 2017-04-27 | 2017-09-01 | 武汉斗鱼网络科技有限公司 | Interface detection method and device |
| CN107704392A (en) * | 2017-09-30 | 2018-02-16 | 华为技术有限公司 | The processing method and server of a kind of test case |
| CN108197026A (en) * | 2017-12-30 | 2018-06-22 | 北京金风科创风电设备有限公司 | Method, device and equipment for testing simulation software of wind generating set and storage medium |
| CN109032943A (en) * | 2018-07-26 | 2018-12-18 | 威创软件南京有限公司 | A method of it is concurrently executed based on robot framework test case |
| CN109144863A (en) * | 2018-08-10 | 2019-01-04 | 广东电网有限责任公司信息中心 | A kind of automated testing method based on network system |
Non-Patent Citations (2)
| Title |
|---|
| 刘晓强;解筱梦;杜明;常姗;蔡立志;刘振宇;: "面向云测试的并行测试用例自动生成方法", 计算机应用, no. 04, 10 April 2015 (2015-04-10) * |
| 李伟华，周兴社: "实时并发软件的测试软件开发", 西北工业大学学报, no. 03, 30 August 1995 (1995-08-30) * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930629A (en) * | 2020-08-14 | 2020-11-13 | 工银科技有限公司 | Page testing method and device, electronic equipment and storage medium |
| CN113485880A (en) * | 2021-07-12 | 2021-10-08 | 浙江网商银行股份有限公司 | Test method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11409640B2 (en) | Machine learning based test case prediction and automation leveraging the HTML document object model | |
| US7917755B1 (en) | Identification of localized web page element | |
| CN107729475B (en) | Webpage element acquisition method, device, terminal and computer-readable storage medium | |
| US10073766B2 (en) | Building signatures of application flows | |
| US20200019418A1 (en) | Machine learning analysis of user interface design | |
| CN109739855B (en) | Method and system for realizing data sheet splicing and automatically training machine learning model | |
| CN104699602A (en) | Method for detecting influence and computer | |
| EP2504748A1 (en) | System and method for object relationship identification in a user interface | |
| US20160380915A1 (en) | Rules-Based Workflow Messaging | |
| CN110928763A (en) | Test method, test device, storage medium and computer equipment | |
| CN108319687B (en) | SQL rule generator based on JS dragging technology | |
| CN106933887B (en) | Data visualization method and device | |
| US20150089415A1 (en) | Method of processing big data, apparatus performing the same and storage media storing the same | |
| Walsh et al. | Automatically identifying potential regressions in the layout of responsive web pages | |
| CN110618941B (en) | Interface element processing method and device | |
| US9678856B2 (en) | Annotated test interfaces | |
| US10460019B2 (en) | Computer implemented system and method for transforming web content for display on multiple form factors | |
| CN111427760A (en) | Page testing method, device, equipment and storage medium | |
| US9104573B1 (en) | Providing relevant diagnostic information using ontology rules | |
| CN105739717B (en) | Data inputting method and device | |
| US20230195825A1 (en) | Browser extension with automation testing support | |
| JP6830701B1 (en) | Test support device, test support program, and test support method | |
| US10007493B1 (en) | Event based validation | |
| CN110147477B (en) | Data resource modeling extraction method, device and equipment of Web system | |
| US9471569B1 (en) | Integrating information sources to create context-specific documents |
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 |