Page testing method and page testing device

Abstract

The embodiment of the invention provides a page testing method and a page testing device, wherein the page testing method is used for testing a page. The method comprises the following steps of: reading a testing statement for indicating a page element and a testing action; searching the position of the page element on the page according to the source code of the page; executing the testing action at the position; and verifying the execution result of the testing action to obtain a testing result. The invention further provides the page testing device. According to the embodiment, an action function is not necessary to be used; an appointed testing action is directly triggered; and therefore, the development complexity and the usage complexity of testing software are both reduced.

Description

technical field [0001] The invention relates to page testing technology, in particular to a page testing method and a page testing device. Background technique [0002] The third-generation software testing technology with Action Word (AW) as its main feature has achieved great success once it was launched because of its ease of use. [0003] In this software testing technique, the test software manufacturer pre-tests each standard action (such as "mouse left button click" Click the button" or "click the drop-down box with the left mouse button", etc.) to define the corresponding action function. This kind of action function is identified by the corresponding action name (such as "click the button with the left mouse button" or "click the drop-down box with the left mouse button", etc.), and its function is not to trigger the corresponding action, but to trigger the action A direct result produced after execution, which may be called an action event. An action list is mai...

AI Technical Summary

Problems solved by technology

It is not difficult to find that testers need to base on the action type (such as "left mouse button click") and the type of the page element to be tested for the action to be tested (for example, the type of "login button" is "button", "gender The type of "drop-down box" is "drop-down box") to select the corresponding action name (for example, "click the button with the left mouse button" or "click the drop-down box with the left mouse button") to determine the corresponding action function, instead of selecting the corresponding action name only based on the action type, because for different types of page elements, even if the action type is the same, the action events triggered after the action is executed are likely to be different (for example, the left mouse button click The "login button" may cause the login result interface to pop up, and clicking the "drop-down box" with the left mouse button may cause the options to be selected), so the corresponding action function needs to be developed according to the type of page element

This difference in action functions due to different types of page elements increases the complexity of the test software

On the one hand, even for the same type of action, test software vendors need to write multiple different action functions according to the type of page element that the action targets, thus increasing the development complexity of the test software

On the other hand, when selecting an action function, the tester needs to further select the desired action function from among multiple similar action functions according to the type of page element the action targets, which increases the complexity of using the test software

Images