Automatic testing method for page objects

Abstract

The invention discloses an automatic testing method for page objects, and belongs to the technical field of page testing. The method comprises the steps of designing each page as a Class; acquiring page elements by calling a page class in a Selenium testing page; reading a testing instruction from the page elements; calling a page code file of a page to be tested, searching for an operated Class and creating a page object instance; calling a page operation related Class specified by the testing instruction; calling the page elements in the page operation related Class to find the correspondingpage elements; performing a page operation on the found page elements and obtaining a testing result. According to the method, each page is designed as a Class, the page elements are obtained by calling the page class in the Selenium testing page, and the situation that testing page codes need to be changed when the page element id or position is changed is avoided.

Description

technical field [0001] The invention relates to a page object automatic testing method, which belongs to the technical field of page testing. Background technique [0002] At present, when using webdriver for testing, there will be a time to locate the elements of a certain page, and the program lines are filled with id, name, xpath and other methods, which will cause poor readability of the test program and is not convenient for the later stage maintenance and modification. [0003] Although it is possible to make the program easier to understand by adding annotations, it cannot fundamentally solve the problem. At present, more methods are used to avoid direct calls to these methods each time by encapsulating these methods. Although reuse can be achieved, the logical processing of page elements and the independence of test data cannot be achieved through encapsulation. [0004] Constantly adding new tests, but rarely refactoring and using the original tests, Selenium's ex...

AI Technical Summary

Problems solved by technology

[0002] At present, when using webdriver for testing, there will be a time to locate the elements of a certain page, and the program lines are filled with id, name, xpath and other methods, which will cause poor readability of the test program and is not convenient for the later stage maintenance and modification

[0003] Although it is possible to make the program easier to understand by adding annotations, it cannot fundamentally solve the problem. At present, more methods are used to avoid direct calls to these methods each time by encapsulating these methods. Although reuse can be achieved, the logical processing of page elements and the independence of test data cannot be achieved through encapsulation

[0004] Constantly adding new tests, while rarely refactoring and using the original tests, Selenium's execution is relatively slow compared to unit tests. As the number of tests gradually increases, the running time will gradually increase to an unbearable level