Less10 2 e_testermodule_9
•
0 j'aime•1,937 vues
The document introduces cookies and how they are handled in Oracle Application Testing Suite: e-Tester. It discusses the two types of cookies - persistent and session cookies. It also describes how the cookie handling options can be configured on a per-script basis and the implications of these settings for stand-alone versus linked scripts.
![Cookies ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Less10 2 e_testermodule_9
Similaire à Less10 2 e_testermodule_9 (20)
Plus de Suresh Mishra
Plus de Suresh Mishra (13)
Dernier
Dernier (20)
Less10 2 e_testermodule_9
- 1. Cookie Handling Introduction to Oracle Application Testing Suite: e-Tester
- 14. Job Scheduler Introduction to Oracle Application Testing Suite
- 22. Miscellaneous Options Introduction to Oracle Application Testing Suite: e-Tester
- 37. Settings Manager Introduction to Oracle Application Testing Suite: e-Tester
- 40. Java Applets Introduction to Oracle Application Testing Suite: e-Tester
Notes de l'éditeur
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 - Stand-Alone Scripts *Reset To Original State:* clears any left-over, persistent settings from a previous recording and playback. Selecting this option resets e-Tester to a clean start-up state. The default browser window name is reset to none, persistent cookies are cleared, user authentication is cleared, and any external browser windows that may have been opened are closed.
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 - Comparison Exclusion Options Content Content Comparison Filters - specifies regular expressions used to exclude specific text strings from the e-Tester playback comparison. Specify any regular expression and click Add. The following expressions are predefined: BV_SessionID=[0-9]*.[0-9]*& BV_EngineID=[a-z]*.[0-9]*& VALUE="[0-9]*" Automatic Contents Comparison Filters - specifies if specific types of machine-generated web page components should be included or excluded from the playback comparison. These settings are used in cases where HTML source appears to be machine-generated, but is necessary for page navigation or other testing, e-Tester must override the defaults heuristic comparison program for accurate playback comparison. URLs - when selected, parts of URLs that appear to be machine-generated are ignored during the playback comparison. Elements - when selected, parts of form elements that appear to be machine-generated are ignored during the playback comparison.
- Oracle Application Testing Suite: Introduction 10 - Comparison Exclusion Options (continued) Scripts - when selected, parts of script literals that appear to be machine-generated are ignored during the playback comparison. HTML - when selected, parts of HTML that appears to be machine-generated is ignored during the playback comparison. The “Automatic Contents Comparison” filters settings apply globally to the Web page component types. Use the “Content Comparison” filters expressions with these settings to specify the exclusions for comparison filters.
- Oracle Application Testing Suite: Introduction 10 - Comparison Exclusion Options (continued) URL Parameter Specifies components of a URL to exclude from the playback comparison. The settings can use pattern matching to specify components of the URL to exclude. The pattern matches are performed using the Visual Basic Like operator. Use the Add, Modify and Remove options to change the default parameters and parameter values. URL Parameters - specifies URL parameters to exclude from Visual Script playback comparison using the following format: LikePattern - the pattern to match for the value of the URL parameter. For example: param1=* param2=* param3=* paramN=* The following expressions are predefined: BV_EngineID=* BV_Operation=*
- Oracle Application Testing Suite: Introduction 10 - Comparison Exclusion Options (continued) The following expressions are predefined (continued): BV_SessionID=* BV_ServiceName=* The following examples show how specific settings affect the playback comparison. For the following URL: http://www.foo.com/engine123/submit.pl?name1=value1&name2=value2 name*=value* excludes the URL parameters name1=value1 and name2=value2 from the playback comparison. For the following URL: <A HREF=/frameset/news.jsp?BV_SessionID=@@@@0166988701.0932590606@@@@&BV_EngineID=calfdfllemjbfdicfmjcfkkdhhm.0&selected=news.htm> BV_EngineID=* BV_SessionID=* BV_SourceName=* excludes the URL parameters BV_SessionID=@@@@0166988701.0932590606@@@@&BV_EngineID=calfdfllemjbfdicfmjcfkkdhhm.0 URL Parameter Values - specifies URL parameter values to exclude from Visual Script playback comparison using the following format: LikePattern - the pattern to match for the value of the URL parameter value. Each exclusion string must be separated from the other exclusion strings by commas, as follows: val1* val2* val3* valN* The following example shows how specific settings affect the playback comparison. For the following URL: http://www.foo.com/engine123/submit.pl?name1=value1&name2=value2 value* excludes the URL parameters value1 and value2 from the playback comparison.
- Oracle Application Testing Suite: Introduction 10 - Comparison Exclusion Options (continued) URL Subpath - specifies URL path values to exclude from visual script playback comparison using the following format: LikePattern is the pattern to match for the path of the URL. Each exclusion string must be separated from the other exclusion strings by commas, as follows: path1* path2* path3* pathN* The following example shows how specific settings affect the playback comparison. For the following URL: http://www.oracle.com/engine123/submit.pl?name1=value1&name2=value2 www*.oracle.com,engine* excludes the URL path parameters www.oracle.com, engine123 and submit.pl from the playback comparison.
- Oracle Application Testing Suite: Introduction 10 - Siebel Support Oracle Application Testing Suite supports Siebel versions 7.0.5 and above as leverages the Siebel Correlation library with Siebel 7.7 and above
- Oracle Application Testing Suite: Introduction 10 - Settings Manager To change settings across multiple Visual Scripts in a Workspace: 1. Open the Settings Manager at the level where you want to change a setting (global, workspace, script, or page). 2. Expand the category. 3. Select the setting to change. 4. Click Replace. Settings Manager opens a dialog box for specifying which visual scripts to change. 5. Select the Visual Script(s) to change and click Add. 6. Double-click the setting name below the visual script list. 7. Change the setting value as needed. 8. Click OK.
- Oracle Application Testing Suite: Introduction 10 - Settings Manager (continued) To use the Settings Manager 1. Open the setting manager at the level where you want to change a setting (global, workspace, script, or page). 2. Expand the appropriate category. 3. Double-click the setting name. The setting value changes to either a selector list or a text field. 4. Change the setting value (either by selecting from the list or by entering a string value into a text field). 5. Click OK.
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 -
- Oracle Application Testing Suite: Introduction 10 - Windows Event Recorder e-Tester also includes a Windows Event recording mode that you can use to record actions on Flash/ActiveX objects. The Window Event Recorder records events on Windows objects rather than DHTML events. To Record Window Events: 1. Start e-Tester recording. 2. While recording a Visual Script, select Run > Record > Start Windows Event Recorder, or click the toolbar button, to enable the Window Event Recorder mode. 3. Navigate the Web site. 4. Select Run > Record > Stop Windows Event Recorder, or click the toolbar button, to disable the Window Event Recorder mode. 5. Stop e-Tester recording. The Start and Stop Event Recorder options are only available while e-Tester is in record mode. The Windows Events are recorded to the Address node properties.