less02 2 e_testermodule_1
TRANSCRIPT
Copyright © 2008, Oracle. All rights reserved.
e-Tester
Introduction to Oracle Application Testing Suite
Copyright © 2008, Oracle. All rights reserved.2 - 2
Topics Covered
The topics to be covered in the e-Tester module:
• Script Basics
• Features of the Visual Script
• Playback and Results Analysis
• Test Cases
• Data Banks
• Dialog Manager
• Cookie Handling
• Other Features
• Java Applet Support
• Flash/ActiveX Support
Copyright © 2008, Oracle. All rights reserved.2 - 3
Uses of e-Tester
• Build a suite of tests which serve as your baseline for functional and regression testing
• Re-use these scripts for load and scalability testing of the application under test
Copyright © 2008, Oracle. All rights reserved.2 - 4
User Interface
Visual Script Pane
Results Pane
Browser Pane
Copyright © 2008, Oracle. All rights reserved.
E-Tester Basics
Introduction to Oracle Application Testing Suite: e-Tester
Copyright © 2008, Oracle. All rights reserved.2 - 6
How Scripts Are Created
Scripts are visual not code-based.
Scripts are recorded automatically as you interact with your web application through the integrated browser.
Scripts can test individual or multiple application functionalities.
Scripting is the process of creating tests which serve as your baseline for functional and regression testing.
Scripts should focus on actual user transactions.
Copyright © 2008, Oracle. All rights reserved.2 - 7
Organize Script
Workspace: a directory created on your hard drive that stores all Oracle Application Testing Suite related files
Workspaces are used for:
• Organizing the test files for different web application projects.
• Dividing the test for different functions of a web application.
• Separating scripts that will run on the test environment and the production environment.
• Separate scalability and functional tests scripts.
Copyright © 2008, Oracle. All rights reserved.2 - 8
The Workspace Manager
Workspace Manager: interface used to add, remove, and open a workspace.
Copyright © 2008, Oracle. All rights reserved.2 - 10
The Workspace Folder
Workspaces are located in the install path of the Oracle Application Testing Suite (<Installpath>\ets\eTEST”)
Copyright © 2008, Oracle. All rights reserved.2 - 11
What Is Kept In The Workspace…
The different files/extensions that the workspace comprises:
• .mom - e-Tester recorded scripts (Microsoft Object Model)
• .wg – Contains additional information for use in e-Load
• .log – Contains the results of the script
• .mom.lck – the script is currently open in e-Tester and has been locked out
• .scn – e-Load scenario file (saved scenarios)
• .mjb – Job Scheduler job file (saved jobs)
• .ini – Workspace Settings file
Copyright © 2008, Oracle. All rights reserved.2 - 12
How to Open A Workspace…
• e-Tester automatically opens the last workspace used
• To open a workspace, select File/Open Workspace
Copyright © 2008, Oracle. All rights reserved.2 - 13
Things to Think About When Creating Scripts…
What sort of transactions will your users perform?
Refer to your Test Plan for the steps to execute, as well as the verification points to check for.
Try a “Dry Run” of your script before you record it, so that nothing unexpected occurs during recording.
Watch for “Scope Creep”
Copyright © 2008, Oracle. All rights reserved.2 - 14
Lets Start Scripting….
Enter the starting URL of your application into the Address bar.
Previously entered addresses may be re-selected through the address drop down.
Copyright © 2008, Oracle. All rights reserved.2 - 15
Start a New Script
If a new script is not already open,select “File”/”New Script”
or click the button as shown
Or
Copyright © 2008, Oracle. All rights reserved.2 - 16
Start Recording
Start Recording by:
• Clicking on the Record Script toolbar icon
• Or Selecting Run/Record/Start
Copyright © 2008, Oracle. All rights reserved.2 - 17
Record Your Script
As you interact with the web application, e-Tester “snaps” the pages that the application navigates to.
Copyright © 2008, Oracle. All rights reserved.2 - 18
Recording Tips
The page download timer (bottom right corner) increments as the page is downloading.
A page will be appended to the script page when download is complete.
Note: Wait until the page has completely downloaded (“snapped”) before navigating to the next page.
If download has not completed, e-Tester may not be able to reproduce the actions that generate the page on playback.
Copyright © 2008, Oracle. All rights reserved.2 - 19
Record a transaction
Enter http://localhost/fmstocks into the address field
Login: ta1 password: ta
Click the “Login” button.
Click the “Research a company” link on the left.
Enter ticker symbol “orcl”
Click “Search”
Stop recording.
Copyright © 2008, Oracle. All rights reserved.2 - 20
Stop The Recording
Stop Recording by:
• Clicking on the stop toolbar icon
• Or select “Run/Record/Stop”
Copyright © 2008, Oracle. All rights reserved.2 - 21
Save Your Script
Save the script by: • Clicking on the Save toolbar icon
• Or select “File”/ “Save Script”
Copyright © 2008, Oracle. All rights reserved.2 - 22
Save Your Script
The script will be saved in the open workspace folder.
You can click “save as” and select any workspace folder to save your script in.
Saving a script will create the following files.
• .mom
• .mom.vba
• .wg
Copyright © 2008, Oracle. All rights reserved.2 - 23
Playback Your Script
Playback the script by:
• Clicking on the “Playback Script” toolbar icon
• Or selecting “Run”/“Playback”/“Start”
Copyright © 2008, Oracle. All rights reserved.2 - 24
Exercise
1. Record a script that tests the view balance and portfolio– Go to http://localhost/fmstocks– User Name: ta1– Password: ta– Click the login button– Click “View your balance”– Click View your portfolio– Logout
Playback the script and answer the following review questions
Copyright © 2008, Oracle. All rights reserved.2 - 25
Review 1
1. Is this a transaction that a typical user would perform? Why would this matter?
2. Is the transaction that was recorded repeatable? Why is this important?
3. Can multiple occurrences of the transaction execute simultaneously? Why is this important?
4. Why is it necessary to wait for each page to completely download before continuing?
5. What is a workspace?
6. Name two files types generated and their purpose when saving an e-Tester script.