Browse Prior Art Database

Change driven automated test management system

IP.com Disclosure Number: IPCOM000245845D
Publication Date: 2016-Apr-13
Document File: 6 page(s) / 41K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is system wherein the automated test cases changed automatically when there is a change in the corresponding source code for the application or the system under test.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 33% of the total text.

Page 01 of 6

Change driven automated test management system

Disclosed is system wherein the automated test cases changed automatically when there is a change in the corresponding source code for the application or the system under test.

Test Automation and selenium was introduced to automate manual testing. Selenium is very useful for testing web based product. In selenium, automation test developer, search the html element of interest and perform action on them to check if the required behavior is achieved. The html element search is happened based on the properties of the html element - like id, name, x-path etc. When you update the web page; i.e. the corresponding java script and html, the property of the html element may change. If the element search was based on that property, Selenium will not be able to find that element and the automation test will start failing.

This proposed system address this issue. If there is a change in the html, css or java script file, proposed algorithm will find that change and will updated the corresponding selenium test so that Automation can still find that element and the test will work as expected. This algorithm will allow to maintain the selenium page objects automatically if there is changes in the source html, css and java script file.

Maintaining automation is a time consuming job and is also associated with cost. Here we are proposing a new framework to write and maintain html elements.

Algorithm -
1. Scan all HTML files and extract HTML element from it and store it in the DB.

2. Scan all JavaScript files and extract HTML element from it. Store the HTML element in the DB.

3. Create page objects for all the user accessible HTML elements in the automation framework.

4. Add an event listener for delivery of the change sets from source control client.

5. Scan all the changed HTML and JavaScript files and compare them with the DB entries.

6. Update the page objects in the automation framework, if any user accessible HTML element is changed.

Step 1:-

The proposed framework start with a parser. The parser will scan all the html and java script files to extract html element from them. This information will be stored in a database table. Table will contain the html elements, its parents (div, span, page) and its properties. There will be a user interface to show this information to the user so that they can write the page objects easily by seeing those html elements and their properties.

Table - HTMLELEMENTS
ElementId (unique ID assigned), ElementType, SourceCodeFileName LISTOFPROPERTIES, PARENT ID

Parents are also HTML Elements. So, they will also be part of this table only.

The algo to populate this table is -

Algo 1:-

From the list of html element, insert them into the table with parent information in the table along with the element type and the properties. If parent is not already present in the table, 1st insert the parent and then the original element.

1


Page 02 of 6

Step 2:

Once user writes the page...