CN111221610B

CN111221610B - Page element acquisition method and device

Info

Publication number: CN111221610B
Application number: CN202010005089.6A
Authority: CN
Inventors: 高媛媛; 刘水泉; 刘庆文; 孙启舜
Original assignee: CCB Finetech Co Ltd
Current assignee: CCB Finetech Co Ltd
Priority date: 2020-01-03
Filing date: 2020-01-03
Publication date: 2023-07-04
Anticipated expiration: 2040-01-03
Also published as: CN111221610A

Abstract

The invention discloses a method and a device for acquiring page elements, and relates to the technical field of computers. One embodiment of the method comprises the following steps: receiving acquisition requirements of pages, and acquiring codes corresponding to the acquisition requirements from source codes of the pages; starting from the position of the code, acquiring offspring similar to the grammar structure of the code and the first offspring of the offspring; and generating an acquisition template based on the codes, the offspring and the first offspring, and acquiring the elements of the page by utilizing the acquisition template to obtain the page elements. According to the embodiment, the code extraction is performed based on the acquisition requirement to generate the acquisition template, so that the page elements are acquired in batches, and the mode of manually recording and acquiring the page elements one by one is different from the mode of manually recording and acquiring the page elements one by one, so that the acquisition speed of the page elements is increased, and the acquisition efficiency is improved.

Description

Page element acquisition method and device

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for collecting page elements.

Background

UI (User Interface) testing in the field of software development has high repeatability, such as multiple tests of new functions and changed functions, regression tests of unchanged functions, and the like. If the manpower is released from the repeated labor, not only the manpower resource can be effectively saved and the cost can be reduced, but also the problem of unstable quality caused by the implementation of different personnel can be avoided.

Currently, the main UI automation test products, tools or frameworks in the market mainly collect page elements one by recording scripts or manually clicking pages, and generate step scripts, such as QTP (Quick Test Professional, automation test tools) or Selenium IDE (open source Web automation test tools).

In carrying out the present invention, the inventors have found that at least the following problems exist in the prior art:

1) The locking condition is required to be defined directly according to the attribute of the target element (i.e. the locked page element) or the outer layer element (i.e. the father element, the grandfather element, etc.), and the more stable locking condition cannot be used by defining the anchor point element (i.e. the upper level element of the target element for locking the target element);

2) Only one by one definition of the page elements (i.e. the path and condition for locating the page elements) can be generated, and batch generation is not supported;

3) Based on the manual page element collection mode, when more page elements are collected one by one, time is consumed.

Disclosure of Invention

In view of the above, the embodiments of the present invention provide a method and an apparatus for collecting page elements, which at least can solve the problems of the prior art that the definition level of the page element features is too single and the efficiency of element recording and collection is low.

To achieve the above object, according to an aspect of the embodiments of the present invention, there is provided a page element collection method, including:

receiving acquisition requirements of pages, and acquiring codes corresponding to the acquisition requirements from source codes of the pages;

obtaining offspring similar to the grammar structure of the code and a first offspring of the offspring from the position where the code is located;

and generating an acquisition template based on the codes, the offspring and the first offspring, and acquiring the elements of the page by utilizing the acquisition template to obtain the page elements.

Optionally, starting from the location where the code is located, obtaining the offspring similar to the syntax structure of the code and the first offspring of the offspring includes:

obtaining offspring which have parent-child relations with the code and have structures similar to the grammar structure from the position where the code is located;

and starting from the position where the offspring is located, acquiring a first offspring which has a parent-child relationship with the offspring and has a structure similar to the grammar structure.

Optionally, the step of obtaining, from the location where the offspring is located, a first offspring having a parent-child relationship with the offspring and having a structure similar to the grammar structure includes:

Determining a subsequent sibling in sibling relation with the offspring and having parent-child relation with the code from the position of the offspring;

and starting from the position of the subsequent brothers, acquiring a second offspring which has a parent-child relationship with the subsequent brothers and has a structure similar to the grammar structure.

Optionally, after the obtaining the page element, the method further includes;

acquiring left and right values of the offspring; wherein the left value and the right value represent two values located on both sides of the assignment operator;

taking the left value as a left value of a page element definition of the page element, and taking the right value as an attribute value of the left value in the page element definition; wherein the page element definition represents a path and conditions for locating the page element.

Optionally, after the obtaining the page element, the method further includes: analyzing the characteristics of the page elements, and constructing a first acquisition template based on the characteristics so as to acquire the page elements of the page by using the first acquisition template to obtain all the page elements in the page.

Optionally, after the obtaining the page element, the method further includes: in response to a selection operation of at least one page element, the at least one page element is highlighted in the page based on a predetermined color.

Optionally, after the obtaining the page element, the method further includes: and determining a tree node corresponding to the page in an object library, and adding the page element into a child node of the tree node to construct a tree structure consisting of the page and the page element.

Optionally, after constructing the tree structure formed by the page and the page element, the method further includes:

receiving a programming language definition or an extensible markup language definition for a single page element;

sub-nodes corresponding to the single page element in the tree structure are colored based on a first color corresponding to the programming language or a second color corresponding to the extensible markup language.

determining the type of the extracted page element in response to the selection operation of the page element in the object library, and acquiring the operation step of the type; the operation steps are page operation behaviors;

the operation steps are ordered and combined according to the selection sequence of the page elements so as to generate operation actions;

and receiving test data input of each operation step in the operation action, and executing the test to obtain a test result.

Optionally, after generating the operation action, further comprising:

in response to a change operation to at least one operation step in the operation actions, the operation actions are updated based on change information in the change operation.

To achieve the above object, according to another aspect of the embodiments of the present invention, there is provided a page element collecting apparatus, including:

the demand receiving module is used for receiving the acquisition demand of the page and acquiring codes corresponding to the acquisition demand from the source codes of the page;

the code acquisition module is used for acquiring offspring similar to the grammar structure of the code and a first offspring of the offspring from the position where the code is located;

and the element acquisition module is used for generating an acquisition template based on the codes, the offspring and the first offspring, and acquiring the elements of the page by utilizing the acquisition template to obtain the page elements.

Optionally, the code obtaining module is configured to:

Optionally, the system further comprises an element definition module for;

Optionally, the device further comprises a first element acquisition module, configured to: analyzing the characteristics of the page elements, and constructing a first acquisition template based on the characteristics so as to acquire the page elements of the page by using the first acquisition template to obtain all the page elements in the page.

Optionally, the method further comprises an element highlighting module for: in response to a selection operation of at least one page element, the at least one page element is highlighted in the page based on a predetermined color.

Optionally, the method further comprises an object library module for: and determining a tree node corresponding to the page in an object library, and adding the page element into a child node of the tree node to construct a tree structure consisting of the page and the page element.

Optionally, the method further comprises an element coloring module for:

Optionally, the device further comprises a test module for:

Optionally, the method further comprises a step changing module for:

To achieve the above object, according to still another aspect of the embodiments of the present invention, there is provided a page element collecting electronic device.

The electronic equipment of the embodiment of the invention comprises: one or more processors; and the storage device is used for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are enabled to realize the page element acquisition method.

To achieve the above object, according to still another aspect of the embodiments of the present invention, there is provided a computer readable medium having stored thereon a computer program, which when executed by a processor, implements the page element collecting method described in any one of the above.

According to the solution provided by the present invention, one embodiment of the above invention has the following advantages or beneficial effects: rapidly and batchly collecting page elements on a current page according to the collection requirement; based on the page elements and the types thereof selected in the object library, the operation steps are generated in batches and saved as scripts and tested, the automatic test of the UI at the Web end is realized, the writing time of the test scripts is shortened, and the applicability of the automatic test is improved.

Further effects of the above-described non-conventional alternatives are described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

FIG. 1 is a schematic flow diagram of a method for collecting page elements according to an embodiment of the present invention;

FIG. 2 is a schematic diagram of an example reporting information template;

FIGS. 3 (a) and 3 (b) are schematic diagrams of two similar pages;

FIG. 4 is a schematic diagram of a human-machine interaction interface defining an acquisition template;

FIG. 5 is a flow chart of an alternative method of page element acquisition according to an embodiment of the invention;

FIG. 6 is a flow chart of another alternative page element gathering method according to an embodiment of the invention;

FIG. 7 is an exemplary diagram of a java defined page element;

FIG. 8 is an exemplary diagram of a page element of an xml definition;

FIG. 9 is an exemplary schematic diagram showing different colors for page elements of different Java definitions and xml definitions;

FIG. 10 is a flow chart of yet another alternative page element gathering method in accordance with an embodiment of the present invention;

FIG. 11 is a schematic diagram of main modules of a page element acquisition device according to an embodiment of the present invention;

FIG. 12 is an exemplary system architecture diagram in which embodiments of the present invention may be applied;

fig. 13 is a schematic diagram of a computer system suitable for use in implementing an embodiment of the present invention.

Detailed Description

Exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, in which various details of the embodiments of the present invention are included to facilitate understanding, and are to be considered merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

The invention relates to the field of automatic testing application of a Web end UI. Although QTP can also realize UI automatic test, the used vb is not an object-oriented language and has slower running speed, so the invention mainly builds the UI automatic test object library tool based on the Selenium.

The words related to the present invention are explained as follows:

page element: the Web page is widely referred to as a component of a Web page, and can be a control, a relatively independent string of characters or pictures, and the like.

Document object model (Document Object Model, DOM): to handle standard programming interfaces of extensible markup languages. On a web page, the objects that organize the page (or document) are organized in a tree structure, and the standard model used to represent the objects in the document is called the DOM.

XML (Extensible Markup Language ): a subset of the standard generic markup language is a markup language used to mark electronic files to be structured.

div element: to provide structural and background elements for the content within html (hypertext markup language ) documents (block-level).

Referring to fig. 1, a main flowchart of a method for collecting page elements provided by an embodiment of the present invention is shown, including the following steps:

s101: receiving acquisition requirements of pages, and acquiring codes corresponding to the acquisition requirements from source codes of the pages;

s102: obtaining offspring similar to the grammar structure of the code and a first offspring of the offspring from the position where the code is located;

s103: and generating an acquisition template based on the codes, the offspring and the first offspring, and acquiring the elements of the page by utilizing the acquisition template to obtain the page elements.

In the above-described embodiment, the tests are largely classified into the unit test, the interface test, and the UI function test for steps S101 and S102. In the projects, UI function test is the test type with the largest task amount in each project, and is also the last version quality detection link before version delivery.

One acquisition template may correspond to multiple acquisition requirements, for example, the "fill information template" includes two acquisition requirements of "fill information item" and "button", and based on the two acquisition requirements, corresponding codes are extracted from the page source code, as shown in fig. 2.

For single acquisition requirements, the corresponding codes of the single acquisition requirements are firstly checked from the source codes of the pages based on manual work, and the codes comprise relation definitions such as offspring, follow-up brothers and the like, tag labels, attributes and attribute values of tags and the like.

Taking code as an example, the implementation process (only examples are provided herein) is specifically illustrated:

1) Locking codes meeting the following conditions, wherein tag is div, id is pane-base, and the codes comprise tag is label and class is el-form-item-label;

2) Searching a corresponding code from the html source code of the page according to the acquisition requirement, and obtaining < div role= "tabpanel" id= "lane-base" aria-labe1 ledby= "tab-base" class= "e 1-tab-lane-wrap" >;

3) Then searching the offspring with the same (or similar) grammar structure as the initial element in the offspring of the initial element, and defining the offspring as anchor point elements to obtain <1Abel for= "personName" class= "el-form-item __ label" style= "width: srem; "> …;

it should be noted that, the anchor element in the present invention is an element having a unique feature and a fixed relationship with the target element. The function is as follows: because it has unique features, it can be accurately locked; because it has a fixed relationship with the target element, it can be locked to the target element by locking the anchor element.

4) Searching a subsequent brother which is in a brother relation with the anchor point element and has a father-son relation with the initial element (namely, a same-level subsequent code with tag being div), and defining the subsequent brother as an intermediate element (namely, an intermediate transition element) to obtain < div class= "el-form-item __ content" >;

5) In the offspring of the intermediate element, the offspring (i.e. the second offspring, tag is input) with the same syntax structure as the initial element is searched, and is defined as the target element, so that < input type= "text" auto complete= "off" class= "el-input __ inner unit" >.

It should be noted that the anchor element must be an intermediate element to be used for the seek transition from the initial element to the target element, but the intermediate element is not necessarily an anchor element, such as a subsequent sibling.

The characteristics of multiple target elements in the same page may be the same, e.g., class attribute el_input_inner, as in multiple input box elements of the page.

In the case where the feature defined for the target element is not unique, the unique feature may be transferred to other elements as anchor elements. For example, the target element does not have a unique feature, but the intermediate element 2 has a unique feature for=personname, from which the intermediate element 2 can be locked, and then the target element is locked according to a "offspring" or "parent-child" relationship between the target element and the intermediate element 2.

Based on the element definition mode between the target element and the anchor element, under the condition that the attribute of the target element is not unique, the anchor element can be determined based on the unique characteristic of the intermediate element, no sequence number locking element is needed, and the condition that when information items in a page change, sequence numbers are needed to be readjusted for all page element definitions is avoided.

From the above, the acquisition requirement needs to start from the initial element in the page source code, lock the anchor element according to the parent-child relationship between the anchor element and the intermediate element, and determine the subsequent sibling element and the target element according to the anchor element, thereby obtaining the final acquisition result.

Taking the "filled information item" in fig. 2 as an example, the obtained anchor point element is the 2 nd intermediate element, the "offspring" of the "initial element" meeting the conditions (parent-child relationship and grammar structure) in the current page is locked, and the "offspring" of the "subsequent brothers" of the "offspring" is finally extracted.

It should be further noted that the examples of fig. 2 and 3 are only one case, i.e., looking up the offspring based on the initial element, and then looking up the offspring based on the subsequent siblings of the offspring. In actual operation, the code forms are various, so that the mode of constructing the acquisition template is various:

1) Because the codes are in a tree structure generally, when the initial element does not have a offspring, the parent code of the initial element can be searched based on the initial element, the parent code can be searched again based on the father and brother codes of the parent code, and then the acquisition template is constructed;

2) But if the parent code and the offspring do not exist, the acquisition template construction can be performed based on the brother codes.

Still further, the current collection only obtains the page elements corresponding to the collection requirements. In actual operation, all page elements of the page can be collected based on the page elements, specifically:

1) Firstly, selecting one or more page elements meeting acquisition requirements from pages based on manual work;

2) Checking source codes corresponding to the page elements to induce unique features of the page elements, determining the relationship between the unique features and the page elements, and creating an acquisition template (namely a first acquisition template) according to the relationship;

3) Through the acquisition template, all page elements meeting the requirements in the page are locked, and the locking process is as follows:

(1) all anchor elements on the page are locked from the initial element through the intermediate element (i.e., all elements that meet the definition of the anchor element in the template);

(2) and for each anchor point element, continuing to pass through the intermediate element, and locking the target element.

For a system or platform, most of front-end controls are unified, so that html structures of more pages have certain similarity, and the similar pages can adopt the same acquisition template to acquire page elements, such as a query function page and an information reporting function page.

Referring to fig. 3 (a) and 3 (b), both pages contain many information filler items, and except for the difference of the information item titles, the CSS (Cascading Style Sheets, cascading style sheet) layer presents style, DOM structure, and the like, which are similar.

For step S103, an acquisition template generation interface is preset, as shown in fig. 4, to generate an acquisition template according to the initial element, the anchor element, the intermediate element and the target element, and then the acquisition template is used to acquire the element of the current page, so as to obtain an acquisition result.

The processing manner of the "button" collection requirement is the same as that of the "filled information item", and the implementation process is not described here again. Finally, based on the collection template corresponding to the 'filled information item' and the collection template corresponding to the 'button', the collection template corresponding to the whole requirement is generated.

It should be noted that, collecting page elements is usually collecting all page elements in a page, for example, the page includes 10 input boxes, the page elements of the 10 input boxes are collected, and the obtained collection template also corresponds to codes of the 10 input boxes.

In actual operation, only a part of the input boxes can be selected as the acquisition requirement, but in order to reduce the generation times of the acquisition template, all the page elements meeting the conditions, such as the page elements of the 10 input boxes, are generally acquired by using the acquisition template, and then manual deletion is supported on the basis.

When a worker views a page element, it may be highlighted (e.g., yellow-green, yellow) to facilitate viewing where the page element is located in the page. For example, clicking the "highlight button" highlights the element "name" on the current page, and if multiple page elements are selected, the highlighting is performed one by one according to the selection order.

According to the method provided by the embodiment, the code extraction is performed based on the acquisition requirement to generate the acquisition template, so that the page elements are acquired in batches, and the acquisition speed of the page elements is accelerated and the acquisition efficiency is improved unlike a mode of manually recording and acquiring the page elements one by one.

Referring to fig. 5, a flowchart of an optional page element acquisition method according to an embodiment of the present invention is shown, including the following steps:

s501: receiving acquisition requirements of pages, and acquiring codes corresponding to the acquisition requirements from source codes of the pages;

s502: obtaining offspring which have parent-child relations with the code and have similar structures with the grammar structures of the code from the position of the code;

s503: determining a subsequent sibling in sibling relation with the offspring and having parent-child relation with the code from the position of the offspring;

s504: starting from the position of the subsequent brothers, obtaining a second offspring which has a parent-child relationship with the subsequent brothers and has a structure similar to the grammar structure;

s505: generating an acquisition template based on the code, the offspring, the subsequent brothers and the second offspring, and acquiring elements of the page by using the acquisition template to obtain page elements;

S506: acquiring left and right values of the offspring; wherein the left value and the right value represent two values located on both sides of the assignment operator;

s507: taking the left value as a left value of a page element definition of the page element, and taking the right value as an attribute value of the left value in the page element definition; wherein the page element definition represents a path and conditions for locating the page element.

In the above embodiment, for the steps S501 to S504, reference may be made to the descriptions of the steps S101 to S102 shown in fig. 1, and the step S505 may be referred to the descriptions of the step S103 shown in fig. 1, which are not repeated here.

In the above embodiment, for step S506, the condition defined by the intermediate element (i.e., the offspring) includes the left value, the right value, and the relationship thereof. The "initial element" of the "filled information item" collection requirement as in fig. 2 should meet the condition: html tag (tagName) is div and id is pane-base.

The left and right values represent two values on either side of the assignment operator:

1) Left value, meaning that if an expression can reference to an object, and the object is a block of memory space and can be checked and stored, then the expression can be taken as the left value;

2) Right value refers to a reference to "data" stored in a certain memory address.

From the above, the left value refers to an object, which is typically provided with a name or accessed by a name in the program, so the left value may in turn indicate that a specific name reference must be provided in the program. The right value refers to the content in the address, so the right value may in turn represent the value to which no specific name refers in the program.

For step S507, the conditions to be described are defined as:

1) The left value is "object name value": the condition represents the right value as the object name of the acquired page element. For example, rightvalue=text, in the acquisition requirement, the condition indicates that for a plurality of acquired page elements, the text thereof is taken as the object name thereof;

take code as an example:

::before

name of name

</label>

The object name of the left value is taken as the "name".

2) The left-right value relationship is "to equals": the condition indicates that an increasing condition is defined for the acquired page element, the left value of the newly increasing condition is the left value of the current condition, the right value of the newly increasing condition is the attribute value defined by the left value of the page element, and the relationship between the two values is equal.

Taking the anchor element (first descendant) in fig. 3 as an example, the newly added condition is for a page element, which is a locked path and condition in the definition of the page element:

< Condition rightvalue = "label" leftvalue "tagName" left2 rightrel= "equal"/>

< Condition rightvalue = "el-form-item_label" leftvalue= "class" left2right trel= "equal" >

The following code is added to the page element definition as a new condition:

< Condition rightvalue = "" leftvalue= "for" left2 right= "to equals"/>

The left value of the newly added condition is 'for', and the left value of the newly added condition is defined as a page element; the right value is "personName", which is the corresponding attribute value in the html of the page element, and the attribute value have an equivalent corresponding relationship of "to".

Through the operation, the object name assignment can be carried out on the page elements in the acquisition result, and the positioning condition of the for attribute is automatically added for the anchor point elements.

The method provided by the embodiment can define and edit the page element based on the left value, the right value and the relation of the intermediate element, support the expansion of the input condition and define the input condition as the newly added condition.

Referring to fig. 6, a flowchart of another optional page element acquisition method according to an embodiment of the present invention is shown, including the following steps:

s601: receiving acquisition requirements of pages, and acquiring codes corresponding to the acquisition requirements from source codes of the pages;

S602: obtaining offspring similar to the grammar structure of the code and a first offspring of the offspring from the position where the code is located;

s603: generating an acquisition template based on the code, the offspring and the first offspring, and acquiring elements of the page by using the acquisition template to obtain page elements;

s604: and determining a tree node corresponding to the page in an object library, and adding the page element into a child node of the tree node to construct a tree structure consisting of the page and the page element.

In the above embodiment, for the steps S601 to S603, reference may be made to the descriptions of the steps S101 to S103 shown in fig. 1, and the descriptions are omitted here.

In the above embodiment, for step S604, the collection result generally includes all page elements in the page, but some workers may not need to perform the deletion operation through the Delete button provided in the interface.

For pruned page elements, the worker, after confirming the check, may click on the "Add to object library" button to add the page element to the object library.

Because the object library may contain page elements of all pages, in order to avoid element confusion, the page elements collected at this time may be added to the child nodes of the tree node corresponding to the page, for example, the child nodes of the log-in page tree node such as the password, the log-in name, and the like.

It should be noted that, the pages and the page elements in the object library represent a two-layer tree structure, so as to represent the page elements contained in the pages. The page elements added to the object library need to determine which page or new page to add to, typically to the collected page.

Further, the invention also supports java definitions and xml definitions for page elements, wherein:

1) Java definition: referring to fig. 7, mainly facing to java programmers, for some page elements with special positioning or operation, the positioning or operation can be directly realized through java language based on selenium, for example, a lower menu is displayed after clicking an upper menu;

2) xml definition: referring to fig. 8, the method is mainly directed to testers (whether programming capability is available or not is not considered) so as to reduce the learning cost of the UI automation test as much as possible.

And for the operations of codes, offspring, follow-up brothers, first offspring and second offspring in the page element acquisition process, the same mode as the xml definition is used for carrying out acquisition requirement definition.

According to the invention, an xml file strictly conforming to a programming grammar structure does not need to be written, a worker can finish definition input of page elements through a human-computer interaction interface, and the maintenance of a single page element defined by xml is supported.

Further, for page elements of different Java definitions and xml definitions, different colors may be presented in the tree structure of the object library. Referring to fig. 9, java defined page elements appear light, while xml defined page elements appear black.

According to the method provided by the embodiment, the structural relation between the page and the page element is displayed in the tree structure, java definition and xml definition of the page element are supported, and different colors are displayed in the tree structure, so that the page element is distinguished.

Referring to fig. 10, a flowchart of still another optional page element acquisition method according to an embodiment of the present invention is shown, including the following steps:

s1001: receiving acquisition requirements of pages, and acquiring codes corresponding to the acquisition requirements from source codes of the pages;

s1002: obtaining offspring similar to the grammar structure of the code and a first offspring of the offspring from the position where the code is located;

s1003: generating an acquisition template based on the code, the offspring and the first offspring, and acquiring elements of the page by using the acquisition template to obtain page elements;

s1004: determining a tree node corresponding to the page in an object library, and adding the page element into child nodes of the tree node to construct a tree structure composed of the page and the page element;

S1005: determining the type of the extracted page element in response to the selection operation of the page element in the object library, and acquiring the operation step of the type; the operation steps are page operation behaviors;

s1006: the operation steps are ordered and combined according to the selection sequence of the page elements so as to generate operation actions;

s1007: and receiving test data input of each operation step in the operation action, and executing the test to obtain a test result.

In the above embodiment, for the steps S1001 to S1003, reference may be made to the descriptions of the steps S101 to S103 shown in fig. 1, and the step S1004 may be referred to the descriptions of the step S604 shown in fig. 6, which are not repeated here.

In the above embodiment, for step S1005, the steps in the present invention correspond to one page operation behavior, for example:

1) Inputting name text in a name input box;

2) Selecting a gender in a gender selection box;

3) Inputting digital text in an age input box;

4) Inputting an identity card number text in an identity card input box;

5) Selecting a ethnicity in a ethnicity selection box;

6) Clicking the "submit" button

7) Judging whether a prompt appears, if so, indicating that the execution is successful, otherwise, indicating that the execution is failed.

All page elements needed by the Web end UI automation script are contained in the object library, and a worker can select the page elements in the object library. And each page element has predefined types, such as input text, drop down selections, buttons, radio boxes, check boxes, etc., with different types of page elements having different operational steps, such as gender selection.

For step S1006, the actions of the present invention correspond to a series of steps, typically a set of business-significant operational steps in a page, such as the submitted application actions of 1) through 7) above.

The invention configures default operation steps for each page element type in advance. After one or more page elements in the object tree are selected, the operational actions are generated according to a default operational order configured for the type of page element or a selection order for the page elements.

In addition, operations such as deleting, adding, adjusting the order of steps or modifying steps to other steps and modifying corresponding step parameters may be supported for operation step customization or modification operations.

For step S1007, a test operation may be performed after the operation action is generated, and a test report is generated after the test is completed. The staff can obtain the execution process information of operation steps, operation events and the like from the test report, and in addition, if the execution fails, a failure prompt, such as screenshot display errors, can be triggered.

The invention may specify a test data source in which the worker writes the test data, e.g., excel. An excel test file template sheet can also be generated for the selected page elements, namely the page element names are used as column headers, such as test task configuration descriptions, test points and the like, so that test data can be conveniently organized on the excel. Or to provide parameters that facilitate the user in defining directly the test data values that need to be used.

In addition, it should be noted that, the primary operation step in the present invention means to simulate a human-computer interaction. The interaction types are more, and the operation (such as clicking, information filling and the like) on the specified page element can be performed, or the man-machine interaction which does not involve the page element can be performed such as waiting.

The operation steps are actually java interactions on page elements, and different java methods can realize different operation steps, so that step libraries are formed through combination. Such as input text (parameters: test data source, page elements), test data source text is entered in the page elements specified by the parameters.

According to the method provided by the embodiment, the operation steps of the page elements are ordered in batches and rapidly based on the types of the page elements, so that the operation actions are generated, and the method is different from the manual recording of generating steps one by one, so that the script generation speed is increased, and the UI test efficiency is improved.

Referring to fig. 11, a schematic diagram of main modules of a page element collection apparatus 1100 according to an embodiment of the present invention is shown, including:

the demand receiving module 1101 is configured to receive a collection demand for a page, and acquire a code corresponding to the collection demand from a source code of the page;

a code obtaining module 1102, configured to obtain, from a location where the code is located, a descendant similar to a syntax structure of the code and a first descendant of the descendant;

and the element collection module 1103 is configured to generate a collection template based on the code, the offspring and the first offspring, and collect elements on the page by using the collection template to obtain page elements.

In the embodiment of the present invention, the code obtaining module 1102 is configured to:

The implementation device of the present invention further includes an element definition module 1104 (not shown in the figure) for defining elements;

The implementation device of the present invention further includes a first element acquisition module 1105 (not shown) configured to: analyzing the characteristics of the page elements, and constructing a first acquisition template based on the characteristics so as to acquire the page elements of the page by using the first acquisition template to obtain all the page elements in the page.

The implementation device of the present invention further includes an element highlighting module 1106 (not shown in the figure) for:

in response to a selection operation of at least one page element, the at least one page element is highlighted in the page based on a predetermined color.

The implementation device of the present invention further includes an object library module 1107 (not shown in the figure) for:

and determining a tree node corresponding to the page in an object library, and adding the page element into a child node of the tree node to construct a tree structure consisting of the page and the page element.

The implementation of the present invention further includes an element coloring module 1108 (not shown) for:

The inventive device further comprises a testing module 1109 (not shown) for:

The implementation device of the present invention further includes a step change module 1110 (not shown in the figure) for:

In addition, the implementation of the apparatus in the embodiments of the present invention has been described in detail in the above method, so that the description is not repeated here.

Fig. 12 illustrates an exemplary system architecture 1200 to which embodiments of the invention may be applied.

As shown in fig. 12, the system architecture 1200 may include

terminal devices

1201, 1202, 1203, a network 1204, and a server 1205 (by way of example only). The network 1204 serves as a medium for providing communications links between the

terminal devices

1201, 1202, 1203 and the server 1205. The network 1204 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

A user may interact with the server 1205 through the network 1204 using the

terminal devices

1201, 1202, 1203 to receive or transmit messages or the like. The

terminal devices

1201, 1202, 1203 may have various communication client applications installed thereon.

The

terminal devices

1201, 1202, 1203 may be various electronic devices having a display screen and supporting web browsing, including, but not limited to, smartphones, tablets, laptop and desktop computers, and the like.

The server 1205 may be a server providing various services, such as a background management server (by way of example only) that provides support for shopping-type websites browsed by users using

terminal devices

1201, 1202, 1203.

It should be noted that, the method provided by the embodiment of the present invention is generally performed by the server 1205, and accordingly, the apparatus is generally disposed in the server 1205.

It should be understood that the number of terminal devices, networks and servers in fig. 12 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 13, there is illustrated a schematic diagram of a computer system 1300 suitable for use in implementing an embodiment of the present invention. The terminal device shown in fig. 13 is only an example, and should not impose any limitation on the functions and the scope of use of the embodiment of the present invention.

As shown in fig. 13, the computer system 1300 includes a Central Processing Unit (CPU) 1301, which can execute various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1302 or a program loaded from a storage section 1308 into a Random Access Memory (RAM) 1303. In the RAM 1303, various programs and data necessary for the operation of the system 1300 are also stored. The CPU 1301, ROM 1302, and RAM 1303 are connected to each other through a bus 1304. An input/output (I/O) interface 1305 is also connected to bus 1304.

The following components are connected to the I/O interface 1305: an input section 1306 including a keyboard, a mouse, and the like; an output portion 1307 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker, and the like; a storage portion 1308 including a hard disk or the like; and a communication section 1309 including a network interface card such as a LAN card, a modem, or the like. The communication section 1309 performs a communication process via a network such as the internet. The drive 1310 is also connected to the I/O interface 1305 as needed. Removable media 1311, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memory, and the like, is installed as needed on drive 1310 so that a computer program read therefrom is installed as needed into storage portion 1308.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flow chart. In such embodiments, the computer program may be downloaded and installed from a network via the communication portion 1309 and/or installed from the removable medium 1311. The above-described functions defined in the system of the present invention are performed when the computer program is executed by a Central Processing Unit (CPU) 1301.

The computer readable medium shown in the present invention may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules involved in the embodiments of the present invention may be implemented in software or in hardware. The described modules may also be provided in a processor, for example, as: a processor comprises a demand receiving module, a code acquisition module and an element acquisition module. The names of these modules do not in some way constitute a limitation on the module itself, for example, an element acquisition module may also be described as a "module that acquires page elements".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be present alone without being fitted into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to include:

According to the technical scheme of the embodiment of the invention, the page elements are rapidly and batched collected on the current page according to the collection requirement; based on the page elements and the types thereof selected in the object library, the operation steps are generated in batches and saved as scripts and tested, the automatic test of the UI at the Web end is realized, the writing time of the test scripts is shortened, and the applicability of the automatic test is improved.

The above embodiments do not limit the scope of the present invention. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of the present invention.

Claims

1. The page element acquisition method is characterized by comprising the following steps of:

receiving acquisition requirements of a page, and acquiring codes corresponding to the acquisition requirements from source codes of the page as initial elements;

searching offspring with the same grammar structure as the initial element in offspring of the initial element, and defining the offspring as anchor point elements;

searching a subsequent brother which is in a brother relation with the anchor element and has a father-son relation with the initial element, and defining the subsequent brother as an intermediate element;

among the offspring of the intermediate element, the offspring with the same grammar structure as the original element is searched and defined as the target element;

and generating an acquisition template based on the initial element, the anchor point element, the intermediate element and the target element, and acquiring the element of the page by using the acquisition template to obtain the page element.

2. The method of claim 1, further comprising, after the obtaining the page element;

acquiring left and right values of the anchor point element; wherein the left value and the right value represent two values located on both sides of the assignment operator;

3. The method of claim 1, further comprising, after the obtaining the page element:

analyzing the characteristics of the page elements, and constructing a first acquisition template based on the characteristics so as to acquire the page elements of the page by using the first acquisition template to obtain all the page elements in the page.

4. The method of claim 1, further comprising, after the obtaining the page element:

5. The method of claim 1, further comprising, after the obtaining the page element:

6. The method of claim 5, further comprising, after constructing the tree structure of the page and the page elements:

7. The method of claim 5, further comprising, after constructing the tree structure of the page and the page elements:

8. The method of claim 7, further comprising, after generating the operational action:

9. A page element acquisition device, comprising:

the demand receiving module is used for receiving the acquisition demand of the page, and acquiring a code corresponding to the acquisition demand from the source code of the page as an initial element;

the code acquisition module is used for searching the offspring which is the same as the grammar structure of the initial element in the offspring of the initial element and defining the offspring as anchor point elements;

the element acquisition module is used for generating an acquisition template based on the initial element, the anchor point element, the intermediate element and the target element, and acquiring the element of the page by utilizing the acquisition template to obtain the page element.

10. An electronic device, comprising:

one or more processors;

storage means for storing one or more programs,

when executed by the one or more processors, causes the one or more processors to implement the method of any of claims 1-8.

11. A computer readable medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements the method according to any of claims 1-8.