Your SlideShare is downloading. ×
Less03 2 e_testermodule_2
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Less03 2 e_testermodule_2

387
views

Published on


0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
387
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 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 -
  • Oracle Application Testing Suite: Introduction 3 -
  • 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[0], Link[1], 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="nextpage.html">Link Text</A>). The default setting is cleared.
  • Oracle Application Testing Suite: Introduction 3 -
  • 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 -
  • 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.
  • Oracle Application Testing Suite: Introduction 3 -
  • Oracle Application Testing Suite: Introduction 3 -
  • 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.
  • Oracle Application Testing Suite: Introduction 3 -
  • Oracle Application Testing Suite: Introduction 3 -
  • Oracle Application Testing Suite: Introduction 3 -
  • Oracle Application Testing Suite: Introduction 3 - Instructor Note Use the Object Model Element Selector to select any page object Select the Property of the object that you want to test
  • Oracle Application Testing Suite: Introduction 3 -
  • Oracle Application Testing Suite: Introduction 3 - Be sure the action is in the right spot. If the actions is not correctly ordered, it may not fire or the script could timeout during playback.
  • Oracle Application Testing Suite: Introduction 3 -
  • Oracle Application Testing Suite: Introduction 3 -
  • Transcript

    • 1. Features of The Visual Script Introduction to Oracle Application Testing Suite: e-Tester
    • 2. Script Views
      • Scripts are viewed in a “tree” style hierarchy
      • Click the “+” sign to expand a node or click the “-” to close a node
      • Right -click a page node and select
        • Expand Page to view the entire contents of the page
        • Collapse page to close all nodes
    • 3. Page Properties
      • Page Properties: allows you to view additional information about the selected visual script node.
      • View the properties by:
        • Right-clicking a node and selecting “Properties”
        • Select “Edit”/“Properties”
    • 4. Page Components (Nodes)
      • Each page is divided into two major sections or “nodes”:
        • Address Node: contains recorded actions, navigations, URL, page timers, and parameters.
        • Frame Node: contains the content of the page
    • 5. The Address Node Introduction to Oracle Application Testing Suite: e-Tester
    • 6. Address Node
      • Cookies: names and values for cookie information transferred between the browser and web server.
      • Parameters: user input from data submitted to the current page from a form on the previous page.
      • Headers: information passed to the server in the HTTP header.
      • Duration Master/Tested: length of time taken to download the page during script record/playback. The tested time updates each time script is played.
      • Delay: length of time the user spent on the previous page before navigating to the current page.
    • 7. Address Node Properties
      • 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.
    • 8. Address Properties Page No. and Title User Actions (DHMTL) Page Load Times Fully Qualified URL User Think Time
    • 9. Understanding Actions
      • e-Tester is optimized for maximum performance. Two events that are automatically recorded are:
        • OnClick
        • OnChange
      • Additional events can be captured when necessary
        • onMouseOver
        • onMouseUp
        • onKeyPress
        • And others
      • Performance may be severely impacted if there are many events to execute.
    • 10. Understanding Actions
      • 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.
      • Action Sample:
      Event: click Object: link with text “account summary” Index: fourth link on the page
    • 11. Understanding Actions
      • Example 2:
      Event: click Frame: named “main” Index: 2 nd element in the form “login” Object: form element with name “login button” (within form named “login”)
    • 12. Pages Without Actions
      • The first page of a script (unless the actions are carried over from another script).
      • Auto-Page/Auto-Split: page or frame that was returned without any action taken by user (client-side redirection).
        • Unexpected Auto-Pages/Auto-Splits may be due to the user not allowing the page to fully download before performing the next navigation or incorrect settings for Java applets.
    • 13. Dynamic Addresses
      • Dynamic URLs can contain one or more variable parameters (example, session id).
      • e-Tester handles dynamic URLs by performing the recorded actions rather than requesting the recorded URL’s.
      http://www.foo.com/home.jsp?SessionID=18a81b0&EngineID=32a1
    • 14. Capturing Events - Advanced Introduction to Oracle Application Testing Suite: e-Tester
    • 15. Events Capturing
      • The Visual Script Events Capture interface allows users to specify additional custom DHTML events for e-Tester to record and playback.
      • Capture and fire events to record/playback that may be required for script execution.
    • 16. Events Capturing
      • Select Options/Current Script/Recording/Event Recording
      • Choose the Element Tag and Event Name to record, and click Add Event.
    • 17. Events Capturing
      • The events specified in the event recording options will appear in the address properties. This example shows a blur event on input elements that was added in the event recording interface.
    • 18. Events Capturing
      • Be careful when adding events and know what you are adding and why.
      • Unnecessary events can have serious impact on the speed and performance of script recording and playback.
      • Unnecessary events make the script more difficult to debug.
    • 19. Events Capturing
      • The following is an example of an unnecessary mouseOver and mouseOut event on links.
    • 20. Events Capturing
      • All the user did was mouse over some links before picking the one needed
    • 21. Events Capturing
      • e-Tester can look at every object on page and automatically record certain common events handlers if it detects that an event handler was fired on the object
        • Event handlers include: onblur, onchange, onfocus, onmouseover, and more
        • Useful for highly dynamic applications that make extensive use of JavaScript event handlers on objects that affect navigation
      • Controlled by setting SmartEventRecording=True through the Settings Manager
    • 22. “ Advanced” Actions In the Address Node Introduction to Oracle Application Testing Suite: e-Tester
    • 23. Advanced Actions
      • Users can manually modify a script without re-recording by adding actions.
      • DHTML objects that were recorded can can be replaced.
      • DHTML objects that were not recorded can be added.
      • Select the Advanced tab
    • 24. Advanced Actions
      • Create a New Event by selecting the “Create New Event” icon from the advanced tab
    • 25. Advanced Actions
      • Click the object for which to add the new action on the web page.
      • The Object Selector places the path of the selected object in the “Selected Path” field after it is clicked.
      • Hit ok to capture the new object path
    • 26. Advanced Actions
      • Once the object is selected, e-Tester has a new path (object) it will perform a DHTML action on.
      • Select the event type to cause e-Tester to perform the DHTML Action
        • Example: Click, Mouse Over, and so on.
    • 27. Advanced Actions
      • The new action has been added to the Actions portion of the Address properties.
      • Actions can be dragged and dropped into the correct sequential location.
    • 28. Advanced Actions
      • Actions can be cut, copied, pasted, or deleted by right clicking as shown.
    • 29. Advanced Actions
      • The entire group of actions can be played back in the page by using the “Play All Events” button on the Advanced tab.
      • Click to select an action of interest and play it individually with the “Play Selected Events” button from the advanced tab.
    • 30. Review 2
      • Explain the components of the following action:
      • click + window(index=0).link(text="browse products" href= http://jersey/fmstocks/browse.asp
      • | index=10)
      • 2 . Why does e-Tester only record onClick and onChange without adjustments? Why not add all events for all objects?
      • 3. True/False e-Tester navigates the pages by the URL.
      • 4. How can actions be added to a page in a script?
      • 5. In the address properties of page 4 of a given script there is a list of actions. What page were the actions actually performed on?
      • 6. Sally has a script that fails to playback because a keyPress event is required for a text box on one page. What is the better solution?
      • A. Use the event capture interface and add the onKeyPress event for text boxes.
      • B. Use the advanced action to add a single onKeyPress for the
      • specific text box
      • C. Manually test the transaction

    ×