Web Element Handler Classes for Automated Locator Generation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing web application testing methods require significant manual effort and expertise to create accurate locators for test automation, making the process tedious and inefficient.
Innovation Solution
Automated generation and management of locators for web elements by analyzing the Document Object Model (DOM) structure to identify elements, remove duplicates, and create XPaths and CSS Selectors, which are then used to generate handler classes, stored in a central repository, and accessed through a user interface.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If manual methods are used to create locators for web elements, then accuracy can be achieved, but significant manual effort and expertise are required making the process tedious and inefficient
Solution Approach 1:
The system enables self-service by automatically generating locators through DOM analysis without requiring manual intervention. The automated locator generation service analyzes web application pages, identifies elements, and creates accurate locators autonomously, eliminating the need for test automation engineers to manually create locators while maintaining high accuracy
Solution Approach 2:
The patent replaces the mechanical manual process of locator creation with an automated computational system. The DOM analysis service uses automated algorithms to parse web page structures, identify elements, and generate locators, substituting human manual effort with machine-based automation that is both efficient and accurate
2Extent of automation
If automated locator generation is implemented, then manual effort is reduced, but complexity in managing multiple accessibility methods (CSS Selectors, XPath) increases
Solution Approach 1:
The system implements universality by generating multiple types of locators (CSS Selectors, XPath expressions) through a single automated service. The locator generation service is designed to produce heterogeneous locator types that can be used across different test automation tools and frameworks, making the system versatile and reducing the need for separate tools for each locator type
Solution Approach 2:
The patent introduces an intermediary layer (the automated locator generation service) that manages the complexity of creating and maintaining multiple locator types. This service acts as a mediator between the web application structure and the test automation requirements, handling the complexity of DOM analysis and locator creation internally while presenting a simplified interface to users
3Adaptability or versatility
If multiple accessibility methods are created for each element, then versatility and test coverage increase, but the amount of data to be stored and managed in the central repository increases
Solution Approach 1:
The system merges multiple locator types for the same web element into a single centralized repository entry. Each element in the repository contains consolidated information including the element identifier, multiple accessibility methods (CSS Selectors, XPath), and associated metadata, reducing redundancy and simplifying data management while maintaining full versatility
Solution Approach 2:
The patent performs preliminary organization of locator data during the automated generation process. The system pre-structures the repository entries with all necessary accessibility methods and metadata before they are stored, eliminating the need for subsequent data consolidation and reducing the overall data management burden
Data Source
AI summary
An example methodology includes, by a computing device, analyzing an application to identify one or more elements in the application and, for each element of the one or more elements, an attribution of the element. The method also includes, for each element of the one or more elements, by the computing device, determining an attribute of the element which is a non-duplicate attribute, creating a first accessibility to the element by the non-duplicate attribute, creating a second accessibility to the element by XPath, and storing the first accessibility and the second accessibility created for the element within a central repository. The method may also include, by the computing device, generating a handler class for an element of the one or more elements in the application, wherein the handler class contains code for accessing the element, and providing the generated handler class to another computing device.