| Oracle® Application Testing Suite OpenScript User's Guide Version 9.10 for Microsoft Windows (32-Bit) Part Number E15488-03 |
|
|
View PDF |
| Oracle® Application Testing Suite OpenScript User's Guide Version 9.10 for Microsoft Windows (32-Bit) Part Number E15488-03 |
|
|
View PDF |
The OpenScript Preferences let you specify default values and settings to use for OpenScript options. This chapter explains the available options in the OpenScript Preferences categories. The OpenScript preferences are under the OpenScript node. The available preferences may vary depending upon installed modules.
To set OpenScript preferences:
Start OpenScript.
Select OpenScript Preferences from the View menu.
Expand the OpenScript node and select the preference category.
Specify the preferences as necessary for the selected category.
The following sections explain the available options for each category.
The OpenScript Correlation interface allows users to create correlation libraries to automatically parameterize dynamic requests during playback. Correlation libraries contain rules for automatically handling dynamic request parameters such as urls, query strings and post data for the specific modules.
This category lets you specify libraries and rules for transforming dynamic data in recorded script URLs and related parameters (headers, post data, etc.) to variable names that will be recognized by the script playback engine (OpenScript or Oracle Load Testing). Correlation rules must be defined within OpenScript modules and are not available with the basic platform.
Selected Module: Shows the names of the defined correlation libraries. Use the Add button to define libraries. After you define a library you can use the Add Rule button to specify the rules to include in the library.
Add Library: Opens a dialog box for adding a correlation library name.
Add Rule: Opens a dialog box for adding a correlation rule to the selected library.
Edit: Opens a dialog box for editing the selected correlation library name.
Delete: Deletes the selected correlation library from the Preferences list. The defined rules for the library are also removed from the preferences. The correlation library .XML file is not deleted from disk.
Up: Moves the correlation rule up in the priority list.
Down: Moves the correlation rule down in the priority list.
Import: Opens a dialog box for selecting the correlation library file to import.
Export: Opens a dialog box for selecting the location where you want to export the selected correlation library .XML file.
Revert: Reverts the library to the default values.
Tab view: Shows the library or rule details for the selected correlation library or rule. The tab view information changes depending upon whether a library or rule node is selected and which type of correlation rule is selected. See the module chapters for details about specific correlation libraries.
This dialog box lets you specify a new correlation library for transforming dynamic data in recorded script URLs and related parameters (headers, post data, etc.) to variable names that will be recognized by the script playback engine (OpenScript or Oracle Load Testing).
Name: Specifies the name of the correlation library. After you define a library you can use the Add Rule button to specify the rules to include in the library. The name is required. You can also select Copy rules to copy correlation rules from an existing library.
Copy rules from existing library: Lets you copy correlation rules from an existing library to a new library.Specifies the name of the correlation library. After you define a library you can use the Add Rule button to specify the rules to include in the library. The name is required. You can also select Copy rules to copy correlation rules from an existing library.
Copy Rules: When selected, a list of existing correlation rule libraries will be enabled for copying.
Library: Lists the correlation rule libraries available for copying.
This dialog box lets you specify or edit a correlation rule for transforming dynamic data in recorded script URLs and related parameters (headers, post data, etc.) to variable names that will be recognized by the script playback engine (OpenScript or Oracle Load Testing).
Type: Specifies the type of correlation rule. The available Source and Target options change depending upon the rule type.
Name: Specifies the name of the correlation rule. The name is required.
Source: Specifies which object(s) to substitute as dynamic data.
Target: Specifies which object(s) to use as the target location of the transform.
This category lets you specify general preferences.
These preferences set the default general preferences. The resulting dialog presents the following fields:
Confirm exit when closing last window: When selected, a confirmation message appears when closing the OpenScript workbench.
Remove script from workbench on close: When selected, any opens scripts will be removed from the workbench when OpenScript is closed.
Maximum Number of Results to Save: Specifies the maximum number of script playback session results to save. The script playback session results appear in the Results view and are saved to the results subdirectory under the script directory. When the maximum number has been reached, subsequent playback sessions delete the oldest playback results.
Results: Specifies the number of results to save.
Record and Playback Port Range: Specifies the range of ports to use to avoid port conflicts when multiple users run OpenScript from a single installation using multiple concurrent interactive desktop sessions (for example, Terminal Server or Remote Desktop sessions).
Minimum: Specifies the port number to use as the minimum.
Maximum: Specifies the port number to use as the maximum.
The Browser preferences specify the browser and any additional arguments. The resulting dialog presents the following fields:
Browser Type: Select which browser to use.
Internet Explorer: When selected, OpenScript uses the Internet Explorer browser.
Path Override: Specifies the path and file name to use to override the default Internet Explorer browser location.
Additional Arguments: Specifies any additional command arguments to include when starting the browser.
Firefox: When selected, OpenScript uses the Firefox browser.
Path Override: Specifies the path and file name to use to override the default Firefox browser location.
Additional Arguments: Specifies any additional command arguments to include when starting the browser.
Start Up: Specifies the browser start up settings.
Startup Timeout: Specifies the amount of time, in seconds, to use for the browser startup timeout.
These preferences set the default encryption preferences. The resulting dialog presents the following fields:
Do not encrypt script data: When selected, passwords are stored and displayed as plain text in the script.
Obfuscate script data: When selected, passwords are obfuscated before storing and displaying in the script. Obfuscated passwords are hidden but not securely encrypted.
Encrypt script data: When selected, passwords are encrypted in the script. Specify an encryption password to use.
Password: Specifies the password to use when encrypting and decrypting data strings using the encrypt() and decrypt() functions. Only users who use the same encryption password in their copy of OpenScript will be able to decrypt script passwords. This same encryption password must be used for authentication on all agent machines that will run or open the script in Oracle Load Testing Authentication Manager or Oracle Test Manager.
Caution:
HTTP scripts do not automatically obfuscate/encrypt sensitive script passwords.These preferences lets you specify the name and location of the repository to use to store script files. The resulting dialog presents the following fields:
Name: Shows the names of the defined repositories. Use the Add button to define repositories and locations.
Location: Shows the location of defined repositories.
Add: Opens a dialog box for specifying a repository and location.
Edit: Opens a dialog box for editing the selected repository and location. The Default repository location can be changed but it cannot be renamed.
Delete: Deletes the selected repository and location from the Preferences list. The script files and directory are not deleted. The Default repository cannot be deleted.
This category lets you specify script playback preferences.
This category lets you specify general playback preferences. The resulting dialog box displays the following sections and fields:
This section lets you specify general playback preferences and displays the following fields:
VU Pacing (Think Time): Specifies the script playback delay between pages for each virtual user. This is the amount of time the user looks at a page before making the next request and is commonly referred to as "think time." There are four options:
Recorded: Uses the delay times that were recorded in the Script. You can set minimum and maximum delay times (in seconds) that override the script delay times in the Minimum and Maximum edit boxes.
Recorded/Random: Uses random delay times based upon the recorded user delay. The low end of the random range as the actual recorded user delay minus the Lower percentage setting. The high end of the random range as the actual recorded user delay plus the Upper percentage setting. For example, if the actual recorded delay time was 100 seconds and the Lower and Upper settings are 10% and 25% respectively, Oracle Load Testing uses random delay times between 90 and 125 seconds.
Random: Uses random times for Virtual User pacing. You can set minimum and maximum delay times for random delay in the Minimum and Maximum edit boxes.
No Delay: Plays back the Visual Scripts at the fastest possible speed with no time between page requests.
Preserve variables between iterations: Used to preserve or automatically clear variables defined in the Run section between successive iterations of the Run section.
Variables defined in the Initialize section will be preserved forever, unless explicitly removed in script code.
Variables set in the Run section will always be preserved between the final iteration of the Run section and the Finish section.
Variables include all items that are added into the script variables collection (see: getVariables() script method). This includes variables for elements such as HTTP form fields defined using http.solve(...) and http.solveXPath(...).
Additional Arguments: Used to specify custom OpenScript script.java code arguments. You can create your own settings in OpenScript scripts. For example, you can create custom settings in OpenScript script.java code, as follows.
if (getSettings().get("MyCustomSetting").equals("abc")) {
info("We're running in ABC mode.");
}
You can then set the additional arguments in the Additional Arguments field as follows:
-MyCustomSetting abc
This section specifies the default playback error handling settings.
On iteration failure, do not run more iterations: When selected, virtual user playback is stopped if an error occurs between playback iterations.
Use recorded value if variable is not found: When selected, the recorded data value will be used if a variable is not found. Databank variables will always use the recorded value if the databank attached to the script cannot be found. If the databank cannot be found and Use recorded value if variable is not found is not selected, the recorded data value will still be used.
This section specifies the default playback system settings.
Maximum JVM Heap Size: Specifies the maximum size of the JVM heap. This value cannot be more than 90% of the total memory size.
JVM Arguments: Used to specify additional Java Virtual Machine (JVM) or program arguments to pass to a script upon playback. It can accept all standard JVM arguments. For example, if you specify a custom argument -Dmyvariable=myvalue in the Additional Arguments, the argument will be passed to the script upon playback. Within the script code you can use System.getProperty("myvariable") to get "myvalue".
If the specified argument conflicts with existing OpenScript playback setting, (for example the "Maximum Heap Size" playback setting) the playback setting replaces the setting being specified in the JVM Arguments.
Debug logging: When selected, debug logging is enabled and DEBUG messages appear in the Console view during script playback. When cleared, debug logging is disabled and DEBUG messages do not appear in the console view during script playback.
This category lets you specify the default playback debug settings. The resulting dialog presents the following options:
Enable Tree View Debugger: When selected, the tree view debugger is enabled. During script playback, tree view nodes in the script are highlighted as they are executed. Script execution stops at any Breakpoints set. Use the Resume toolbar button to continue script execution or use the Step options to step into or over script functions. When cleared, the tree view debugger is disabled. If Breakpoints are set in the script, the script execution stops and the Java code view opens.
Pause on exceptions: When selected, script playback is paused if an AbstractScriptException occurs during playback. You can use the Execute debug option to run actions after an error occurs. You may also be able to modify the script and save it to reposition execution pointer at start of the function where the exception occurred.
Activate the workbench when a breakpoint is hit: When selected, the OpenScript workbench becomes the active window when a breakpoint is reached during script execution. When cleared, The OpenScript workbench does not become the active window.
Activate the debug view when a breakpoint is hit: When selected, the Debug view becomes the active view when a breakpoint is reached during script execution. When cleared, the Debug view remains in its current state.
This category lets you specify error recovery actions for exceptions that occur during playback. You can set the error recovery action for individual playback exceptions. Expand specific sections and set the error recovery action. You can set the action as Fail, Warn, or Ignore, as follows:
Fail: Report the error as failure and stop script execution.
Warn: Report the error as a warning and continue script execution.
Ignore: Ignore the error and continue script execution.
ReportErrorAndContinue: Report the error to the results log and continue script execution. .
Error Recovery playback preferences specified in the OpenScript Preferences are stored on the local machine and only apply when the script is played back from inside OpenScript on that machine. If you upload your script to Oracle Load Testing on another server and your script depends on an error recovery setting being a certain way in order for it to work, then you can set the error recovery setting in the OpenScript script Java code.
In OpenScript scripts, error settings can be turned on and off at any time, overriding the default Oracle Load testing and OpenScript Preferences using script Java code. For example:
getSettings().setErrorRecovery("http.zeroLengthDownloads", "IGNORE");
// user code executed in script, such as http.get(), http.post(), ...
getSettings().setErrorRecovery("http.zeroLengthDownloads", "FAIL");
This section lets you specify the default General error recovery actions, as follows:
Variable Not Found - specifies the error recovery action if a variable cannot be found when parsing transformed strings.
Create Variable Failed - specifies the error recovery action if a script fails to create a variable.
File Not Found - specifies the error recovery action if a file is not found.
Segment Parser Failed - specifies the error recovery action if the XPath Segment Parser cannot verify the correctness of an XPath.
Binary Decode Failed - specifies the error recovery action if a binary post data parameter error occurs.
Encryption Service Not Initialized - specifies the error recovery action when the password encryption service was not initialized.
Unexpected Script Error - specifies the error recovery action if any unexpected script error occurs.
Child Script Failed - specifies the error recovery action if a child (a script called from another script) script fails during playback.
Function Failed - specifies the error recovery action if a called function fails during playback.
This section lets you specify the default Functional Test error recovery actions, as follows:
Text Matching Failed - specifies the error recovery action if a text matching test fails.
Object Test Failed - specifies the error recovery action if an object test fails.
Table Test Failed - specifies the error recovery action if a table test fails.
This section lets you specify the default HTTP error recovery actions, as follows:
Zero Length Downloads - specifies the error recovery action if a server response indicates zero bytes length.
Text Matching Failed - specifies the error recovery action if a text matching test fails.
Response Time Error - specifies the error recovery action if a Server Response Time test fails.
Solve Variable Failed - specifies the error recovery action if a table test fails.
HTML Parsing Error - specifies the error recovery action if an HTML parsing error occurs.
Invalid URL - specifies the error recovery action if the server returns an Invalid URL response code.
Invalid HTTP Response Code - specifies the error recovery action if the sever returns an invalid HTTP response code.
Client Certificate Keystore Error - specifies the error recovery action if the Client Certificate Keystore indicates and error.
This section lets you specify the default Oracle Forms Functional test error recovery actions, as follows:
Oracle Forms Error - specifies the error recovery action if any Oracle Forms Functional test error occurs.
This section lets you specify the default Oracle Forms Load test error recovery actions, as follows:
Form Connect Error - specifies the error recovery action if a server connection error occurs.
Forms Input/Output Communication Error - specifies the error recovery action if a read or write error occurs with an Oracle Forms message.
Forms Content Match Failed - specifies the error recovery action if the content of a form does not match on playback.
Forms Playback Error - specifies the error recovery action if there is an error playing back a form.
Forms Component Not Found - specifies the error recovery action if a component of a form is not found.
This section lets you specify the default Utilities error recovery actions, as follows:
SQL Execute Error - specifies the error recovery action if an SQL execute error occurs.
XML Parsing Error - specifies the error recovery action if any XML parsing error occurs.
CSV Loading Error - specifies the error recovery action if an error occurs while loading a CSV file.
This section lets you specify the default Web Functional Test error recovery actions, as follows:
Response Time Error - specifies the error recovery action if a Server Response Time test fails.
Solve Variable Failed - specifies the error recovery action if the value of any variable cannot be solved.
Wait for Page Timeout - specifies the error recovery action if a page timeout error occurs.
Object Not Found - specifies the error recovery action if a web page object is not found.
Playback Failed - specifies the error recovery action if script playback fails.
This category lets you specify playback preferences that apply to all Functional Test scripts. The resulting dialog box displays the following sections and fields:
This section lets you specify the default Match Format and Object Enumeration setting.
Match Format: Specifies which format to use to match attributes in an object path. The match format can be a wildcard-formatted or a regular-expression-formatted expression. format is one of the following settings:
wildcard: (default) Attributes in the given path may contain wildcards for unknown characters. For example, title="Welcome, user *". An asterisk "*" matches any number of characters. A question mark "?" matches any single character.
wildcardThenRegex: Attributes in the given path may contain a wildcard-formatted expression, or a regular-expression-formatted expression. During playback, an attempt is first made to find the object assuming a wildcard format, then an attempt is made to find the object assuming a regular-expression format.
regex: Attributes in the given path may contain a regular expression.
Object Identification: specifies which Object Identification method to use. Select one of the following options:
Use XPath: When selected, the OpenScript object identification uses the standard XPath query language to find an object within a page by searching for it in the HTML based on its tag + attributes.
Use XPath with Smart Match: When selected, the OpenScript uses an XPath with OpenScript Smart Match, which provides additional functionality to rank the choices in cases where XPath alone returns multiple matches. The following example explains how the Smart Match ranking feature enhances object identification in an XPath. With the following XPath,
/web:a[@text='Search' OR @href='search.jsp' OR @index='0']
it is possible for multiple links on a page to match the XPath criteria. For example:
link A: text='Logout', href='logout.jsp', index=0
link B: text='Search', href='search.jsp', index=3
link C: text='Search', href='doNotSearch.jsp', index=15
link D: text='Find', href='search.jsp', index=22
When Smart Match is not enabled, OpenScript returns the first result found on the page (Link A in the above example).
When Smart Match is enabled, OpenScript ranks all the results based on how well they match the specified attributes in the XPath. OpenScript evaluates the XPath from left-to-right and produce a list of attribute name=value pairs. For example:
Attribute 1: text=Search
Attribute 2: href=search.jsp
Attribute 3: index=0
OpenScript then builds a table and assigns a score to each attribute for each result. OpenScript assigns a 0 or a 1 based on whether or not each result matches a particular attribute name=value pair. The result with the highest numerical ranking will be used during playback. For example:
| Link | Attr 1 text=Search | Attr 2 href=search.jsp | Attr 3 index=0 | Smart Mode Score |
|---|---|---|---|---|
| A | 0 | 0 | 1 | 001 |
| B | 1 | 1 | 0 | 110 (Best Match) |
| C | 1 | 0 | 0 | 100 |
| D | 0 | 1 | 0 | 010 |
Logical operators (AND, OR) in the XPath are ignored when Smart Match is enabled during playback. In Smart Match mode, all attributes are matched as one group in left-highest priority.
You can specify required attributes by using the Logical AND operator. All attributes joined together using the Logical OR operator are optional. The AND operator has a higher priority than the OR operator when both operators are used in a single XPath. Parenthetical groups of attributes are also permitted. For example:
/web:a[@text='Search' AND (@alt='Find' OR @title='Find')]
In this XPath, the text attribute is required, and the alt and title attributes are ranked using the Smart Match ranking system.
You can turn on/off Smart Mode for an individual action(s) by using the getSettings().set() API.
This section lets you specify the browser settings for functional tests.
Hide browser during playback: Specifies if the browser appears or is hidden during script playback. However, the browser will be changed to be visible automatically when focus is set to an element inside of that browser by a mouse click or key press event.
Close browser after playback: Specifies if the browser automatically closes after playback.
This category lets you specify HTTP playback preferences. The resulting dialog box displays the following sections and fields:
This section lets you specify HTTP playback preferences and displays the following fields:
Proxy Host: Specifies the host name of the proxy server.
Proxy Port: Specifies the port to use on the proxy server.
Username: Specify the user name to use for authentication.
Password: Specify the password to use for authentication.
Non-Proxy Hosts: Specifies the host name of the non-proxy servers.
This section lets you specify specifies the default HTTP compression playback settings.
Enable GZIP: When selected, the GZIP compression format is enabled.
Enable Deflate: When selected, deflate is enabled.
This section specifies the default HTTP header playback settings.
Browser Emulation: Specifies which browser to emulate for script playback. The Default is the recorded browser.
Language: Specifies which language to use for script playback. The default is English.
HTTP Version: Specifies which HTTP version to use for script playback.
Accept String: Specifies the Accept string to use in the Request header for script playback.
Global Headers: Specifies any custom "Global Headers: string to use in the Request header for script playback. The format is in the form: name1:value1;name2:value2;name3:value3. For example: x-oracle-slm-message-id: bcn=<beacon_name>; svc=<service_name>.
This section specifies the default HTTP playback connections settings.
Enable Keep Alive: When selected, keep alive is enabled.
Max Number of Keep Alive Requests: Specifies the maximum number of requests to make on a keep alive connection before closing it or select Unlimited for an unlimited number.
Max HTTP Connections Per User: Specifies the maximum number of server connections per process per server. Each VU makes multiple connections to request additional resources for images and additional frames for example. Setting this option specifies a limit on the total number of connections that the VUs can make to the server. The default setting is 'Default', which means use the default connection limits as configured on the agent machine. (See Microsoft KBase article Q183110 for more information.)
This section specifies the default HTTP playback Secure Sockets Layer (SSL) settings.
SSL Version: Specifies the SSL version to use.
This section specifies the default miscellaneous HTTP playback settings.
Do not request URLs ending in: Specifies the URLs that will not be requested when the URL ends with one of the specified patterns or file types. Specify the ending pattern or file type separated by commas.
Ignore URLs that Match Regex: Specifies the Regular Expression(s) string to use to ignore specific resources. For example, the expression Login_Banner(.+?) would not download resources such as Login_Banner1.gif and Login_Banner2.gif. Multiple Regular Expressions can be separated using a comma (,).
Cache Emulation: Specifies the type of user to simulate. This is useful for simulating different profiles of virtual users. A first time user places more of a load on the Web server because pages and image are not yet cached. A repeat user places less of a load on the server as only newer pages are requested and brought down from the Web server. There are three options:
Do Not Cache: cache is not used. When using WinInet, selecting Do Not Cache has the same effect as selecting 1st Time as the Cache Emulation method. In this case, document cache is not created and not cleared.
1st Time User: The virtual users are considered to be using the Web site or application for the first time for each iteration so no cache is used. The cache is used during the iteration.
Repeat User: The virtual users are considered to have visited or used the Web site or application previously. Pages and images are retrieved from the cache.
Enable Cookies: When selected, the virtual user profiles will use cookies. Use this setting if your Web application uses cookies to manage session and other context information.
Download Local Files: When selected, the Java Agent retrieves the requested local file contents.
Preserve Cookies between iterations: Used to preserve or automatically clear cookies added to the browser in the Run section between successive iterations of the Run section.
Cookies added to the browser in the Initialize section will be preserved forever, unless explicitly removed in script code.
Cookies added to the browser in the Run section will always be preserved between the final iteration of the Run section and the Finish section.
Preserve Connections Between Iterations: Used to preserve connections between OpenScript and the browser between successive iterations of the script.
Max Content Size (KB): Specifies the maximum number of KB to download from a server for a given request. The default value of this option is "Unlimited". However, the maximum Virtual User Display Size is set to 1024KB, which may cause content in the Details view to be truncated if the content size exceeds the Virtual User Display Size. You can configure the Maximum Virtual User Display Size by adding the following setting in the Additional Arguments field of the General Playback Preferences:
-MAX_VUDATA_BYTES xxxxxxxx
Where xxxxxxxx is the size in KB to set as the Maximum Virtual User Display Size. For example:
-MAX_VUDATA_BYTES 10000000
See Section 2.4.1, "General Playback Preferences" for additional information about specifying Additional Arguments.
Socket Timeout: Specifies the maximum number of seconds to wait for a socket connection before timing out.
This section lets you specify the default settings for which resources (embeded objects, images, css, js, jars, etc.) to download for a page during playback of a script.
The Download Manager does the following:
Parses resource URLs embeded in an html page during playback.
Simplifies scripts by filtering out resource URLs from scripts.
Provides user control over which resource URLs are downloaded or executed during playback.
Note:
Certain resource URLs that do not appear directly in the HTML page contents are not parsed by the Download Manager. For example, an HTML page that imports a '.css' file. When the browser loads the HTML page, it automatically loads the '.css' file and downloads any '.gif' resources.Certain resource URLs that are not inside an HTML tag are not parsed by the Download Manager. For example, a resource URL that is dynamically composed by Javascript cannot be parsed by Download Manager.
The resource downloads will be included in the playback results in the Results view and the HTML Results report. Each downloaded resource counts as a hit in the Hits per Second and Total Hits reports. The size in kilobytes for each resource is included in the Kilobytes per Second and Total Kilobytes reports.
The Download Manager section has the following options:
Use Download Manager: When selected, the Download Manager is enabled during playback. When cleared, the Download Manager is not enabled during playback.
Ignored Resources (Use RegEx): Specifies the Regular Expression(s) string to use to ignore specific resources. For example, the expression Login_Banner(.+?) would not download resources such as Login_Banner1.gif and Login_Banner2.gif. Multiple Regular Expressions can be separated using a comma (,).
CSS Resource: When selected, css resources in <Link> tags are downloaded during playback. When cleared, css resources are not downloaded during playback.
Image Resource: When selected, image resources in <Img> tags, in the "background" attribute of a tag, or in <style> tags with "background:url" patterns are downloaded during playback. When cleared, image resources are not downloaded during playback.
Embeded Object Resource: When selected, object resources in <Embed> tags or in <Object> tags are downloaded during playback. When cleared, object resources are not downloaded during playback.
Script Resource: When selected, script resources in <Script> tags are downloaded during playback. When cleared, script resources are not downloaded during playback.
Applet Resources: When selected, applet resources in <Applet> tags are downloaded during playback. When cleared, applet resources are not downloaded during playback.
This category lets you specify playback preferences for Oracle EBS/Forms Functional Tests. The resulting dialog box displays the following sections and fields:
This section lets you specify the default forms event timeout setting.
Forms Startup Timeout: Specifies the maximum number of seconds OpenScript should wait for a form to appear before considering the form not found. This is the default timeout when waiting for a form to appear before invoking an action against it. This is also the default timeout when waiting for a form to appear before continuing the script.
Forms Action Timeout: Specifies the maximum number of seconds OpenScript should wait for forms action playback until success.
Forms Response Timeout: Specifies the maximum number of seconds OpenScript should wait for forms response before timing out.
This category lets you specify playback preferences for Oracle EBS/Forms Load Tests. The resulting dialog box displays the following sections and fields:
This section lets you specify playback log preferences.
Capture Message Details: Specifies if forms message details are captured during playback. When selected, OpenScript captures and stores Forms message requests, responses, and information about all loaded Forms components during playback. This information is useful to have when debugging the script.
OpenScript displays captured details in the "Messages" and "Object Details" tabs of the Details view. Oracle Load Testing displays this information in the Virtual User Display based on the "Virtual User Display" settings.
Capturing message details is a memory-intensive operation. During heavy load testing, it is recommended to clear this setting to reduce the amount of heap space required by the agent.
Show Message Log In the Console: Specifies if forms message log details are shown it the Console tab. When selected, the message log details are shown in the console. When cleared, the message log details are not shown in the console.
This category lets you specify playback preferences for the agent Shared Data Service. The resulting dialog box displays the following fields:
OATS Credential: Specifies the authentication credentials to use to establish the communication between the shared queue and the Virtual User.
Enable global shared data access credentials: When selected, when selected, the shard data access credentials are enabled. Specify the Address, User Name, and Password.
Address: Specifies the address of the Oracle Load Testing for Web Application server to use for the shared data service.
User name: Specifies the user name to use for authentication. The default name is oats unless changed in the Oracle Application Testing Suite configuration.
Password: Specifies the password to use for authentication. This should be the same password specified in the Encryption setting of the General preferences if the Encrypt script data setting is selected.
Actions on Shared Data: Specifies actions on shared data.
Timeout: Specifies the maximum number of seconds to wait for actions on shared data to occur before timing out.
This category lets you specify the default preferences for Web Functional Test script playback. The resulting dialog box displays the following sections and fields:
This section lets you specify the default object playback timeout setting.
Timeout: Specifies the maximum number of seconds OpenScript should wait for an object to appear before considering the object not found. This is the default timeout when waiting for an object to appear before invoking an action against it. This is also the default timeout when waiting for an object to appear before continuing the script.
You can override individual object wait timeouts in waitForPage() or object.waitFor() by editing their "timeout" properties. Action timeouts cannot be overridden.
This section lets you specify the default playback settings for Web functional test-type scripts.
Capture HTML: When selected, the page HTML will be captured.
Capture screenshots: When selected, a screen image of the page will be captured.
Capture URLs: When selected, the page URL will be captured.
Capture frames: When selected, the HTML frames on the page will be captured.
Clear session cookies between iterations: When selected, session cookies are cleared from cache between playback iterations.
Clear persistent cookies between iterations: When selected, persistent cookies are cleared from cache between playback iterations.
Clear cache between iterations: When selected, pages are cleared from cache between playback iterations.
Clear session cookies before playing back: When selected, session cookies are cleared from cache before playback.
Clear persistent cookies before playing back: When selected, persistent cookies are cleared from cache before playback.
Clear cache before playing back: When selected, pages are cleared from cache before playback.
This section lets you specify the default screen capture delay setting.
Delay time for capture screenshot: Specifies the amount of time to wait before capturing a screenshot of the page.
This section lets you specify the default date format.
Date Format: Specifies the month, day, year, and time format. The Date Pattern follows standard Java SimpleDateFormat string conventions. The default value is MMM d, yyyy h:mm:ss a (month, day, year, hour, minutes, seconds, am/pm).
This category lets you specify recording preferences.
Selecting the Record preferences node let you specify the following general recording preference:
Show external toolbar while recording: When selected, the floating recording toolbar will be shown while recording. When cleared the floating toolbar is not shown.
This dialog box lets you specify recording preferences for the HTTP module. The resulting dialog box displays the following sections and fields:
This tab lets you specify the general browser recorder settings.
Setup: Specifies the network settings for proxy recording.
Network Interface: Enter or select the network IP address of the proxy server.
Port: Specify the port to use on the proxy server.
Additional Arguments: Specify any additional command line arguments to use when starting the proxy server.
Maximum Download Size (MB): Specify the file size for file downloads.
Only record requests originating from the local machine: When selected, only requests originating from the local machine are recorded by the HTTP proxy recorder.
Client-Side Digital Certificate File: Enter the name of a .PFX-formatted digital certificate file or use the Browse button to select a file.
File: Specifies the name of the setup file. Enter the name or use the Browse to select the file from a drive and directory location.
Choose above pfx file to store: Specifies the private-key password defined for the client certificate PFX file when the certificate was exported from Internet Explorer. Click Store and enter the private-key password for the client certificate.
SSL Version: Specifies the SSL version to use.
SSL Version: Select SSL version to use for the proxy server.
Close browser when stopping recorder: Specify the browser options that will be used during HTTP recording.
Close browser: When selected, the browser closes automatically when recording is stopped.
Always Launch a new browser when starting recorder: Specify the browser options that will be used during HTTP recording.
Launch browser: When selected, the browser launches automatically when recording is started.
Error Handling: Specify the error handling options that will be used during HTTP recording.
Record navigations that return error code 404: When selected, the HTTP recorder records navigations that return a Server Status Code 404: Not Found.
This tab lets you specify the default Proxy recorder settings.
Chain Proxy: Specifies if the OpenScript proxy is chained to another proxy.
Use browser's proxy: When selected, the HTTP recorder uses the proxy configuration specified by the browser.
Use specified proxy: When selected, OpenScript uses the specified proxy.
Use proxy configuration script: When selected, the specified configuration scripts will be used.
Address: Specify the URL to the JavaScript file containing the FindProxyForURL JavaScript function supplied by the system administrator for the intranet environment.
Use proxy server: When selected, the specified proxy server will be used.
Address: specify the network IP address of the proxy server to which to chain the OpenScript proxy.
Port: Specify the port to use on the chained proxy server.
Proxy Authentication: Specifies the log in credentials for authentication.
Username: Specify the user name to use for authentication.
Password: Specify the password to use for authentication.
This tab lets you specify the URL type(s) to filter during recording.
Name: Shows the name(s) of the defined filters. Select the checkbox to enable the filter. Clear the checkbox to disable the filter.
Pattern: Shows the pattern(s) specified for the defined filters.
Match by: Shows the match setting(s) (Content Type or URL) specified for the defined filters.
Add: Opens a dialog box for specifying a URL filter.
Edit: Opens a dialog box for editing the selected URL filter.
Delete: Deletes the selected URL filter.
Automatically filter download manager resources: When selected, the proxy recorder automatically filters the URL resources based upon the settings specified in the Download Manager section of the HTTP Playback preferences. When cleared, the Download Manager settings are not used during recording.
This dialog box lets you specify recording preferences for the Oracle Forms Functional Test module. The resulting dialog box displays the following sections and fields:
This tab lets you specify the general browser recorder settings.
Miscellaneous: Specifies if screenshots are captured.
Capture screenshots: When selected, screenshots are captured during recording.
This tab lets you specify the Oracle Forms object identification attributes.
Name: Shows the name(s) of the defined Oracle Forms object identifiers.
Attributes: Shows the pattern(s) specified for the defined Oracle Forms object identifiers.
Add: Opens a dialog box for specifying a new Oracle Forms object identifier.
Edit: Opens a dialog box for editing the selected Oracle Forms object identifier.
Delete: Deletes the selected Oracle Forms object identifier.
This dialog box lets you specify recording preferences for the Oracle Forms Load Test module. The resulting dialog box displays the following section and fields:
Applet Parameters: Specifies the Forms Applet Class property to use to record Forms applications.
EBS Forms: When selected, the OpenScript Applet Class property oracle.forms.engine.main is used to record EBS/Forms applications.
Custom Forms: When selected, the specified Applet Class property is used to record custom non-Web deployed Forms applications.
Miscellaneous: Specifies the miscellaneous record preferences.
Force HTTP Recording: When selected, recording communicates over HTTP disregarding the connection parameter values of the Applet page. This setting may be necessary if the site has an Applet loading page that is set to communicate over a socket instead of using HTTP. If the contents of the Applet loading page are set to Socket, OpenScript cannot record the socket traffic.
This dialog box lets you specify recording preferences for the Siebel Functional Test module. The resulting dialog box displays the following sections:
This tab lets you specify the Siebel general preferences.
SI Elements Paths: Specifies if the Siebel script recorder uses Siebel specific object identifier paths for the webdom elements that are marked in the Siebel application as Standard Interactivity (SI) controls instead of normally recorded attributes such as text, href, and index.
Use special paths for SI elements: When selected, the Siebel script recorder records only the Siebel tag attributes when normal html elements (A, TD, INPUT, DIV, etc.) are used as SI controls in a Siebel application.
Path: Specifies the object identifier path to use for Siebel SI controls. The Siebel attributes are RN (repository name), OT (object type) and UN (unique name).
Edit: Opens a dialog box for editing the object identifier path.
Sitemap Links: Specifies if the Siebel script recorder uses Siebel site map page specific object identifier paths when recording actions on links within the Siebel site map page instead of normally recorded object identifier paths that use the standard path. The standard path includes a particular document index or frame name, which may change dynamically on playback of the script.
Use global paths for Sitemap link: When selected, the Siebel script recorder records only a site map page specific path for the object identifier path.
Path: Specifies the object identifier path to use for Siebel site map page links. The Siebel attributes are RN (repository name), OT (object type) and UN (unique name).
Edit: Opens a dialog box for editing the object identifier path.
Miscellaneous: Specifies the miscellaneous Siebel record preferences.
Record "waitForPage actions: When selected, the script recorder generates "wait for page" actions for test steps that generate a page transition in the browser. When cleared, the script recorder generates a "capture page" action for test steps in Siebel applications. Some Siebel actions may not generate the page transition needed to reliably play back "wait for page" actions. Clearing this setting for Siebel Functional test scripts allows scripts to record the "capture page" action instead of the "wait for page" action for more accurate script playback.
This tab lets you specify the Siebel object identification attributes.
Name: Shows the name(s) of the defined Siebel object identifiers.
Attributes: Shows the pattern(s) specified for the defined Siebel object identifiers.
Add: Opens a dialog box for specifying a new Siebel object identifier.
Edit: Opens a dialog box for editing the selected Siebel object identifier.
Delete: Deletes the selected Siebel object identifier.
This dialog box lets you specify recording preferences for the Web Functional Test module. The resulting dialog box displays the following sections and fields:
This tab lets you specify the general Web Functional test recorder settings.
Browser: Specify the browser options that will be used during Web Functional test recording.
Always launch a new browser when recording a different script: When selected, a new instance of the Internet Explorer browser is launched for each new script recording. When cleared, a new browser is launched only for the first script recording of the OpenScript session. The general case is to launch a new browser instance for each specific script. However, when chaining scripts using a shell script where each script needs to use the same instance of the browser, clearing this setting will cause subsequent scripts recordings to use the same browser instance as the first recording.
Miscellaneous: Specifies the miscellaneous record settings.
Capture screenshots: When selected, screen images are captured during recording.
Capture HTML: When selected, page source HTML is captured during recording.
Capture URLs: When selected, the page URL will be captured.
Capture Frames: When selected, the HTML frames on the page will be captured.
Ignore Auto Page: When selected, server-side auto pages are ignored during recording.
Action Cache Interval(s): Specifies how often to cache page actions during recording. The following cases are determined by this setting:
If while recording, the text on the same Web page element is changed within the Action Cache Interval time setting, the previously recorded value will be replaced by the changed value. In the Java code, the setText action will be replaced with the changed value.
If while recording, a browser window closes within the Action Cache Interval after a user performs an action on a web page (for example, a button click) the window close event will not be recorded, as the window close event is considered to be caused by the previously performed action.
Record "waitForPage actions: When selected, the script recorder generates "wait for page" actions for test steps that generate a page transition in the browser. When cleared, the script recorder generates a "capture page" action for test steps that generate a page transition in the browser. For Web functional test scripts, the "wait for page" action is the normal record option. See the Siebel Functional test record preferences for additional information.
This tab lets you specify recording preferences for the Web Functional Test module.
Name: Shows the name(s) of the defined Web object identifiers.
Attributes: Shows the pattern(s) specified for the defined Web object identifiers.
Add: Opens a dialog box for specifying a new Web object identifier.
Edit: Opens a dialog box for editing the selected Web object identifier.
Delete: Deletes the selected Web object identifier.
This tab lets you specify recording preferences for the Web Services module. The resulting dialog box displays the following sections and fields:
This tab lets you specify the general browser recorder settings.
Request Timeout: Specifies the amount of time in seconds to wait for a response to a request before timing out.
Generate default values for requests: When selected, the OpenScript XML parser generates the specified values for the primitive data types by default. The values may be empty. (For other Axis or Oracle parsers the parameters of the methods must be specified.)
xsd:string: Specifies the default value for String data type parameters.
xsd:int: Specifies the default value for Integer data type parameters.
xsd:long: Specifies the default value for Long data type parameters.
xsd:float: Specifies the default value for Float data type parameters.
xsd:double: Specifies the default value for Double data type parameters.
xsd:boolean: Specifies the default value for Boolean data type parameters.
This tab lets you specify additional Apache AXIS parsers to use with the Web Services module.
Apache AXIS 1.X: Specifies the root folder of the Apache AXIS 1.X implementation of the SOAP ("Simple Object Access Protocol") parser. Download "AXIS 1.4 Final" binary ZIP file (axis-bin-1_4.zip) from http://ws.apache.org/axis/, unpack the zip file, and then specify the AXIS 1.X root folder using the Browse button.
Apache AXIS 2: Specifies the root folder of the Apache AXIS 2 implementation of the SOAP ("Simple Object Access Protocol") parser. Download the AXIS 2 Standard Binary Distribution ZIP file (axis2-1.3-bin.zip) from http://ws.apache.org/axis2/, unpack the zip file, and specify the AXIS 2 root folder using the Browse button.
This category lets you specify script step group creation, naming, and numbering preferences. Step groups allow you to optionally organize your OpenScript script commands into logical groupings based on the type of script you are creating. If step groups are enabled during recording, your script commands will be listed within a step group node (or sections) in the tree view (or code view) of the script. Step groups can also be added or modified manually or completely disabled if you prefer not to use them.
This dialog box lets you specify how step groups are created for ADF Functional Tests. See the Basic module Step Group preferences on for additional information. The resulting dialog box displays the following options:
Step Creation: Specifies if step groups are created or not by default during script recording.
Based on time threshold: When selected, step groups are created based upon the specified recording time threshold. Specify the Threshold time value in seconds.
ADF Functional: When selected, step groups will be created based on the ADF component. Groups are created whenever an ADF component is changed.
Do not create steps: When selected, step groups will not be created automatically during script recording.
Step Naming: Specifies if step groups are named or not by default during script recording.
By page title: When selected, step groups are named based upon the title of the Web page as defined in the HTML <Title> tag for the main page and the page URL will also be shown in parentheses in the step group name. If a title is not specified then the step group will be named "No Title" but URL will still be displayed.
ADF Component: When selected, step groups are named based upon the component title specified by the ADF JavaScript. If no title is found in the ADF Javascript, step groups are named based upon the title of the Web page as defined in the HTML <Title> tag. If no is title found, step groups are named based upon the subsequent child elements.
Do not name steps: When selected, step groups will not be named automatically during script recording.
Step Numbering: Specifies if step groups are numbered or not by default during script recording.
Auto number: When selected, step groups are numbered sequentially starting with step 1.
Do not number steps: When selected, step groups will not be numbered automatically during script recording.
This dialog box lets you specify how step groups are created. The resulting dialog box displays the following options:
Step Creation: Specifies if step groups are created or not by default during script recording.
Based on time threshold: When selected, step groups are created based upon the specified recording time interval threshold. Specify the Threshold time value in seconds. Script commands that occur within the specified time interval relative to each other, will be organized into the same step group. For example, if a user performs multiple actions on a page within the specified time interval would result in those action commands being grouped into the same step group. This may be useful for grouping commands into step groups for AJAX applications where full Web page transitions may not occur which would allow you to group commands by page.
Do not create steps: When selected, step groups will not be created automatically during script recording.
Step Naming: Specifies if step groups are named or not by default during script recording. Step names will be displayed in the step nodes of the tree view and also shown in the code view. Step names can also be edited manually in either view.
Do not name steps: When selected, step groups will not be named automatically during script recording.
Step Numbering: Specifies if step groups are numbered or not by default during script recording.
Auto number: When selected, step groups are numbered sequentially starting with step 1.
Do not number steps: When selected, step groups will not be numbered automatically during script recording.
This dialog box lets you specify how step groups are created, named, and numbered for HTTP scripts. See the Basic module Step Group preferences on for additional information. The resulting dialog box displays the following options:
Step Creation: Specifies if step groups are created or not by default during script recording.
Based on time threshold: When selected, step groups are created based upon the specified recording time threshold. Specify the Threshold time value in seconds.
Do not create steps: When selected, step groups will not be created automatically during script recording.
Step Naming: Specifies if step groups are named or not by default during script recording.
By page title: When selected, step groups include the title of the web page.
Do not name steps: When selected, step groups will not be named automatically during script recording.
Step Numbering: Specifies if step groups are numbered or not by default during script recording.
Auto number: When selected, step groups are numbered sequentially starting with step 1.
Do not number step: When selected, step groups will not be numbered automatically during script recording.
This dialog box lets you specify how step groups are created for EBS Forms Functional Tests. See the Basic module Step Group preferences on for additional information. The resulting dialog box displays the following options:
Step Creation: Specifies if step groups are created or not by default during script recording.
Based on time threshold: When selected, step groups are created based upon the specified recording time threshold. Specify the Threshold time value in seconds.
Forms Functional Test: When selected, step groups will be created based on the windows in which the actions occur. Groups are created whenever a Window Activate action is recorded.
Web Functional: When selected, step groups are created based upon the loading of a new Web page being loaded in the browser. When a new page is finished loading, the page and subsequent user actions performed on that page prior to the next page load will be grouped into the same step group.
Do not create steps: When selected, step groups will not be created automatically during script recording.
Step Naming: Specifies if step groups are named or not by default during script recording.
Forms Functional Test: When selected, step groups will be named the same as the window titles. Groups will be named the same as the window that is active.
Web Functional: When selected, step groups are named based upon the title of the Web page as defined in the HTML <Title> tag for the main page and the page URL will also be shown in parentheses in the step group name, If a title is not specified then the step group will be named "No Title" but the URL will still be displayed.
Do not name steps: When selected, step groups will not be named automatically during script recording.
Step Numbering: Specifies if step groups are numbered or not by default during script recording.
Auto number: When selected, step groups are numbered sequentially starting with step 1.
Do not number steps: When selected, step groups will not be numbered automatically during script recording.
This dialog box lets you specify how step groups are created for EBS Forms Load Tests. See the Basic module Step Group preferences on for additional information. The resulting dialog box displays the following options:
Step Creation: Specifies if step groups are created or not by default during script recording.
Based on time threshold: When selected, step groups are created based upon the specified recording time threshold. Specify the Threshold time value in seconds.
Oracle EBS/Forms Load: When selected, step groups will be created based on the windows in which the actions occur. Groups are created whenever a Window Activate action is recorded.
Do not create steps: When selected, step groups will not be created automatically during script recording.
Step Naming: Specifies if step groups are named or not by default during script recording.
By page title: When selected, step groups are named based upon the title of the Web page as defined in the HTML <Title> tag for the main page and the page URL will also be shown in parentheses in the step group name. If a title is not specified then the step group will be named "No Title" but URL will still be displayed.
Oracle EBS/Forms Load: When selected, step groups will be named the same as the window titles. Groups will be named the same as the window that is active.
Do not name steps: When selected, step groups will not be named automatically during script recording.
Step Numbering: Specifies if step groups are numbered or not by default during script recording.
Auto number: When selected, step groups are numbered sequentially starting with step 1.
Do not number steps: When selected, step groups will not be numbered automatically during script recording.
This dialog box lets you specify how step groups are created for Siebel Functional Tests. See the Basic module Step Group preferences on for additional information. The resulting dialog box displays the following options:
Step Creation: Specifies if step groups are created or not by default during script recording.
Based on time threshold: When selected, step groups are created based upon the specified recording time threshold. Specify the Threshold time value in seconds.
Web Functional: When selected, step groups are created based upon the loading of a new Web page being loaded in the browser. When a new page is finished loading, the page and subsequent user actions performed on that page prior to the next page load will be grouped into the same step group.
Do not create steps: When selected, step groups will not be created automatically during script recording.
Step Naming: Specifies if step groups are named or not by default during script recording.
Siebel Functional: When selected, step groups will be named based upon the Siebel URL pattern. OpenScript uses a heuristic to evaluate the recorded URL of pages to determine a meaningful title.
Web Functional: When selected, step groups are named based upon the title of the Web page as defined in the HTML <Title> tag for the main page and the page URL will also be shown in parentheses in the step group name, If a title is not specified then the step group will be named "No Title" but the URL will still be displayed.
Do not name steps: When selected, step groups will not be named automatically during script recording.
Step Numbering: Specifies if step groups are numbered or not by default during script recording.
Auto number: When selected, step groups are numbered sequentially starting with step 1.
Do not number steps: When selected, step groups will not be numbered automatically during script recording.
This dialog box lets you specify how step groups are created, named, and numbered for Siebel scripts. See the Basic module Step Group preferences on for additional information. The resulting dialog box displays the following options:
Step Creation: if step groups are created or not by default during script recording.
Based on time threshold: When selected, step groups are created based upon the specified recording time threshold. Specify the Threshold time value in seconds.
Do not create steps: When selected, step groups will not be created automatically during script recording.
Step Naming: Specifies if step groups are named or not by default during script recording.
By Siebel URL Pattern: When selected, step groups will be named based upon the Siebel URL pattern. OpenScript uses a heuristic to evaluate the recorded URL of pages to determine a meaningful title.
By page title: When selected, step groups include the title of the web page.
Do not name steps: When selected, step groups will not be named automatically during script recording.
Step Numbering: Specifies if step groups are numbered or not by default during script recording.
Auto number: When selected, step groups are numbered sequentially starting with step 1.
Do not number step: When selected, step groups will not be numbered automatically during script recording.
This dialog box lets you specify how step groups are created for Web Functional Tests. See the Basic module Step Group preferences on for additional information. The resulting dialog box displays the following options:
Step Creation: Specifies if step groups are created or not by default during script recording.
Based on time threshold: When selected, step groups are created based upon the specified recording time threshold. Specify the Threshold time value in seconds.
Web Functional: When selected, step groups are created based upon the loading of a new Web page being loaded in the browser. When a new page is finished loading, the page and subsequent user actions performed on that page prior to the next page load will be grouped into the same step group.
Do not create steps: When selected, step groups will not be created automatically during script recording.
Step Naming: Specifies if step groups are named or not by default during script recording.
Web Functional: When selected, step groups are named based upon the title of the Web page as defined in the HTML <Title> tag for the main page and the page URL will also be shown in parentheses in the step group name, If a title is not specified then the step group will be named "No Title" but the URL will still be displayed.
Do not name steps: When selected, step groups will not be named automatically during script recording.
Step Numbering: Specifies if step groups are numbered or not by default during script recording.
Auto number: When selected, step groups are numbered sequentially starting with step 1.
Do not number steps: When selected, step groups will not be numbered automatically during script recording.
|
 Copyright © 2009, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|