Oracle Application Testing Suite: Introduction 3 - Script Views Look and feel is similar to Windows Explorer. Scripts are stored in a tree form. You can use either the “+” sign to expand the tree or use the “Expand Page” selection and view all the components of the tree node. Use the “Expand Page” option on Page 3 and observe the various components of the tree.
Oracle Application Testing Suite: Introduction 3 - Page Properties Page Properties: This dialog box shows the properties of the selected page node of the visual script. The properties are as follows: Page - the page number and title from the visual script. Type - the visual script node type: Page. Name - the page name assigned to this node. Execute Default Comparison Test - when selected, the default test that checks for page differences is executed on playback. Any HTML content that has changed on the application since the script was recorded will be flagged with a warning notification. Result - the result of the comparison test: passed or failed.
Oracle Application Testing Suite: Introduction 3 - Page Components (Nodes) Each page is divided into 2 major sections: Address Node: Contains the recorded navigations, URL and timers for the page. Frame Node: Contains the content of the page.
Oracle Application Testing Suite: Introduction 3 - Instructor Note Address Node Properties: Shows the properties and options of the selected address node of the visual script. The properties are as follows: Page - the page number (also referred to as the step number). Type - the visual script node type selected: (in this case its “Address.”) Title - the title of the page from the web application HTML source (<TITLE> </TITLE> tag set) The title attribute shown in the visual script is editable in the page properties dialog. URL - the Uniform Resource Locator (URL) web address of the page. Actions - lists the Dynamic HTML and/or Java events to be played back. The associated check box lets you include or exclude specific events in the Visual Script playback. When selected, the event is included in playback. When cleared, the event is not included. Attributes - the time attributes for the page, as follows: Recorded Duration - the amount of time in seconds it took for the page. Tested Duration - the amount of time in seconds required to test the page. Delay Before Playback - the amount of time in seconds e-Tester delayed before playback of the page. Base Final Event on Index - when selected, e-Tester navigates pages using the zero-based index of the “event” that occurred on the page (for example, a click on Link, Link, and so on.) and ignores any text related to the event. When cleared, e-Tester navigates pages using the text for the click events from the HTML source (for example, the text “Link Text” within the HTML: <A HREF=&quot;nextpage.html&quot;>Link Text</A>). The default setting is cleared.
Oracle Application Testing Suite: Introduction 3 - Anytime a user clicks an object on a webpage, an action is generated. Actions performed on a given step eventually cause navigation to a subsequent page which is where the action information is stored. Take the following example of a user is recording a new script: The first step (page 1) is navigation to http://localhost/fmstocks. The second step (page 2), the user logs in to the application. On page 2 the user clicks “Account Summary” which gives step (page 3). The action was performed on page 2 but it will be listed in the address properties of page 3. Address properties show how a user got to the page.
Oracle Application Testing Suite: Introduction 3 - Pages Without Actions Auto Pages: result when there is a new page recorded, with no user interaction. For example, certain applications will have the user wait for the completion of a long server-side transaction and display automatically one or more “Please wait…” pages to let the user know that the transaction is in progress and has not completed. If this page was displayed 3 times, this page is recorded 3 times in the visual script as an auto page.
Oracle Application Testing Suite: Introduction 3 - As discussed above, e-Tester looks for objects that the user interacted with during the recording process and reproduces the events performed with actions on playback. Script execution is the same as an actual user experience and therefore session ID’s an other dynamic parameters are automatically accounted for. Pages with actions show URL’s for informational purposes only.
Oracle Application Testing Suite: Introduction 3 - Some applications require execution of events in addition to onClick and OnChange for successful playback. If there is a mouseOver that is needed for links on a repeated basis, the event can be set up for automatic capture. Any of the common DHTML events can be added with this interface.
e-Test has to now execute 102 mouseOver and mouseOut events before it gets to click event that navigates. The mouseOver and mouseOut events are unnecessary and will greatly slow the playback of the script.
Right-click the Address node and select “Address Properties” to get more information on the navigations that were recorded.
Navigations show how you got from the previous page to the current page you are looking at.
e-Tester records the DHTML path and event type for each object you interacted with. e-Tester uses the path to find the object then fires the recorded event during playback. The listing of path to objects and their events are known as actions.
Address Properties Page No. and Title User Actions (DHMTL) Page Load Times Fully Qualified URL User Think Time