Automated test tool interface

• US 8,924,934 B2
• Filed: 02/04/2011
• Issued: 12/30/2014
• Est. Priority Date: 02/04/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Sullivan, Blake, Subramaniam, Pavitra, Yvanovich, Mark
• Primary Examiner(s): Hong, Stephen
• Assistant Examiner(s): Nazar, Ahamed I
• Application Number:
  US13/021,668
• Publication Number:
  US 20120204091A1
• Time in Patent Office: 1,425 Days
• Field of Search: 715/226, 715/768, 717/124
• US Class Current: 717/124
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

An automated test tool interface is described. A developer of a reusable web component provides an interface for obtaining an accurate identification of a root element of a component and any sub elements within the root element on a web page. An automated test framework uses this interface when recording automated tests to obtain a stable identification of the element that is independent of the rendering of the component on the web page. When the automated test is played back, the test framework again uses the interface to convert the stable identification of the element to a form that is dependent on the rendering of the component on the web page. Thus, changes in the rendering of a component will no longer cause an automated test tool to fail, as element identification in the testing framework is no longer tied to the specific rendering of the web page.

Claims

1. A non-transitory computer-readable storage medium storing a plurality of instructions for controlling a processor to generate automated test tool interfaces, the plurality of instructions comprising:

instructions that cause the processor to receive information defining one or more functions that convert between a Document Object Model dependent representation of an element of a component and a Document Object Model independent representation of the element of the component;

instructions that cause the processor to generate one or more interfaces of the component based on the information defining the one or more functions;

instructions that cause the processor to provide the Document Object Model independent representation of the element of the component based on accessing at least one of the one or more interfaces, wherein the instructions that cause the processor to provide the Document Object Model independent representation of the element of the component comprise;

instructions that cause the processor to receive, from a testing system, a first identifier that identifies the element of the component that is being tested;

instructions that cause the processor to determine, based on the first identifier, a second identifier associated with the element; and

instructions that cause the processor to send the second identifier to the test system; and

instructions that cause the processor to provide a Document Object Model dependent representation of the element of the component based on accessing at least one of the one or more interfaces.

2. The non-transitory computer-readable storage medium of claim 1 wherein the instructions that cause the processor to provide the Document Object Model dependent representation of the element of the component further comprise:

instructions that cause the processor to receive, from the testing system, the second identifier;

instructions that cause the processor to determine, based on the second identifier, a third identifier associated with the element; and

instructions that cause the processor to send the third identifier to the testing system.

3. The non-transitory computer-readable storage medium of claim 2, wherein the first identifier is a first XPATH locator which identifies the element according to a Document Object Model rendering of the component.

4. The non-transitory computer-readable storage medium of claim 3 wherein the second identifier is a stable locator that is independent of the Document Object Model rendering of the component.

5. The non-transitory computer-readable storage medium of claim 4, wherein the third identifier is a second XPATH locator that identifies the element according to the Document Object Model rendering of the component.

6. The non-transitory computer-readable storage medium of claim 5, wherein the first XPATH locator and the second XPATH locator are the same.

7. The non-transitory computer-readable storage medium of claim 6, wherein the instructions that cause the processor to determine the second identifier includes:

instructions that cause the processor to access a published interface of the component to determine the second identifier.

8. The non-transitory computer-readable storage medium of claim 7, wherein the instructions that cause the processor to determine the third identifier includes:

instructions that cause the processor to access the published interface of the component to determine the third identifier.

9. The non-transitory computer-readable storage medium of claim 8, wherein the testing system stores the second identifier.

10. The non-transitory computer-readable storage medium of claim 9, wherein the component is an HTML component.

11. The non-transitory computer-readable storage medium of claim 9, wherein the component is an ADF Faces component.

12. The non-transitory computer-readable storage medium of claim 9, wherein the published interface of the component is not included when the component is deployed to a production web server.

13. A method comprising:

receiving, with a computer, information defining one or more functions that convert between a Document Object Model dependent representation of an element of a component and a Document Object Model independent representation of the element of the component;

generating, with the computer, one or more interfaces of the component based on the information defining the one or more functions;

providing, with a computer, the Document Object Model independent representation of the element of the component based on accessing at least one of the one or more interfaces, wherein providing the Document Object Model independent representation of the element of the component comprises;

receiving, from a testing system, a first identifier that identifies the element of the component that is being tested;

determining, based on the first identifier, a second identifier associated with the element; and

sending the second identifier to the test system; and

providing, with the computer, a Document Object Model dependent representation of the element of the component based on accessing at least one of the one or more interfaces.

14. The method of claim 13, wherein providing the Document Object Model dependent representation of the element of the component further comprises:

receiving, from the testing system, the second identifier;

determining, based on the second identifier, a third identifier associated with the element; and

sending the third identifier to the testing system.

15. A system comprising:

a processor; and

a memory coupled to the processor, the memory containing a set of instructions which when executed by the processor cause the processor to;

receive information defining one or more functions that convert between a Document Object Model dependent representation of an element of a component and a Document Object Model independent representation of the element of the component;

generate one or more interfaces of the component based on the information defining the one or more functions;

provide the Document Object Model independent representation of the element of the component based on accessing at least one of the one or more interfaces, wherein to provide the Document Object Model independent representation of the element of the component the processor is caused to;

receive, from a testing system, a first identifier that identifies the element of the component that is being tested;

determine, based on the first identifier, a second identifier associated with the element; and

send the second identifier to the test system; and

provide a Document Object Model dependent representation of the element of the component based on accessing at least one of the one or more interfaces.

16. The system of claim 15 wherein the set of instructions that cause the processor to provide the Document Object Model dependent representation of the element of the component further comprises instructions that cause the processor to:

receive, from the testing system, the second identifier;

determine, based on the second identifier, a third identifier associated with the element; and

send the third identifier to the testing system.

17. The system of claim 15 wherein the first and third identifiers are XPATH locators and the second identifier is a stable locator.