Your SlideShare is downloading. ×
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
Less07 2 e_testermodule_6
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

Less07 2 e_testermodule_6

219

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
219
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
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 7 -
  • Oracle Application Testing Suite: Introduction 7 - Auto Map Click the Auto Map button to generate Variables for every Parameter and automatically Map each of these Variables to the Corresponding Parameter
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 - Auto Bind Click the Auto Bind button to generate Data Bank Fields for each Variable and Bind them respectively
  • It is important to understand when to databank an input parameter. You may have a registration form with 15 fields that you think all need to get values from a databank, however the application may require that only the email field is unique. Even though the registration data will not be unique for each iteration (except the email), the load and results from the back end will be the same as if the data had been varied, since the same resources are required to do a database write regardless of the actual data submitted in this case.
  • Oracle Application Testing Suite: Introduction 7 - Synthesize To generate synthesized data: 1. Select “Edit > Data Bank Wizard” or click the toolbar button. 2. Click the “Data Binding” tab. 3. Click “Synthesize.” 4. Enter a field name in the “Name” field. 5. Specify a data pattern in the “Pattern” field. 6. Specify the “Algorithm”, “Direction”, “Fill”, and “Case” options 7. Specify the Min, Max, and Step values. 8. Click Insert to add another column to the data bank. The column number increments and the name and pattern values will clear out. 9. Repeat steps 4-7 to define data generation for the next column of Data Bank data. 10. Repeat steps 8-9 for each column of data to add to the Data Bank file. 11. Specify a file name in which to save the data. 12. Click “Sample” to generate a representative sample of the synthesized data. The sample data bank file opens in Windows Notepad. 13. Use the “Column Number” arrow buttons to switch between and edit column pattern definition settings. 14. Specify the number of data rows to generate in the “Rows” field. 15. Click OK to generate the data bank file.
  • Oracle Application Testing Suite: Introduction 7 - Synthesize Algorithm: Specifies the algorithm to use to generate the data. The following options are available: Random - generates random data values. Sequential - generates sequential data values. Direction: Specifies the data direction. The following options are available: Forward - generates data in ascending order. Reverse - generates data in descending order. Fill: Specifies if leading zeros are used to fill all positions in multi-digit numbers. The following options are available: True - insert leading zeros to maintain digit length. False - do not insert leading zeros. Column Number: Changes the data bank column. Use the “Insert”, and “Remove” buttons to add and remove columns in the data bank file. Case: Specifies the case of generated text characters. The following options are available: Lower - generates lower case letters. Upper - generates upper case letters Both - generates mixed case letters.
  • Oracle Application Testing Suite: Introduction 7 - Synthesize (continued) Min: Specifies the minimum value for generated values. Max: Specifies the maximum value for generated values. Step: Specifies the increment amount to use between generated data values. Insert: Inserts a new column into the data bank file. Remove: Remove the current column from the data bank file. Clear: Clears the current pattern definition values.
  • Oracle Application Testing Suite: Introduction 7 - Synthesize General Properties: Specifies the number of data rows and the name of the Data Bank file. Rows: Specifies the number of data value rows to generate. File Name: Specifies the name of the Data Bank file in which to save the generated data. Sample: Generates a sample set of data based upon the current pattern definition settings and values.
  • Oracle Application Testing Suite: Introduction 7 - Review BONUS: If your script continues past the page which follows a form submission, how could attaching a databank file cause the following navigations to break?
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 - Identify The Failure The changes are HTML Differences, Link Differences, Failed Navigations Analyze the differences to locate exactly what changed
  • Oracle Application Testing Suite: Introduction 7 - View The Actions The changes are HTML Differences, Link Differences, Failed Navigations Analyze the differences to locate exactly what changed
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 - Modify The Action Modifying the action is only a viable solution if the change to the navigation is permanent. If you are using a data bank with multiple values, this solution will not work.
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 -
  • Oracle Application Testing Suite: Introduction 7 - Modify Location Criteria Note: This solution only works if the following are true: The object attribute is changing The object position never changes The subsequent navigations remain intact
  • Transcript

    • 1. Advanced Data banking Introduction to Oracle Application Testing Suite
    • 2. Advanced Data banking
      • In order to save time, e-Tester provides the ability to automatically create variables, add mappings, create a data file, and add bindings.
        • Auto Map: Data bank feature that creates variables for each parameter in the Visual Script and maps each variable to its respective parameter.
        • Auto Bind: Data bank feature that creates a data file (containing headers for each variable and the recorded data for each mapped variable) and binds each data bank field to its respective variable.
    • 3.
      • Open the Data Bank Wizard.
      • Click on the Auto Map button.
      • A variable will be created for each unique parameter listed. Each parameter will be mapped to a variable.
      Auto Map
    • 4. Auto Map
      • Auto Map will generate a variable and mapping for every parameter in the visual script.
      • Some data is not necessary for navigations. The unnecessary variables and mappings should be eliminated
      • Eliminating unnecessary variables/mappings will:
        • Reduce the size and complexity the Data Bank file and the Data Bank associations
        • Make the script easier to debug for future test runs
    • 5. Auto Bind
      • Add variables and mappings.
      • Click on the Auto Bind button.
      • A Data Bank file will be created, and saved in the DataBank directory. The file is named with the script name.
      • The Data Bank fields will be bound to the variables.
    • 6. Databank Recommendations
      • Auto mapping and auto binding should only be used when there are several fields that are to be databanked
      • Think about what is happening on the backend when setting up databank.
      • You may only have to databank a handful of fields in a given situation.
    • 7. Synthesize
      • Synthesize enables you to add/edit data in a databank file to fit a defined pattern.
    • 8. Synthesize
      • Enter name for “header” of data file
      • Define a pattern
        • # for number
        • % for letter
        • ? For letter or number
      • Define algorithm and other fields
      • Click “Insert” to add another field
    • 9. Synthesize
      • Enter name for “header” of data file
      • Define a pattern
        • # for number
        • % for letter
        • ? For letter or number
      • Define algorithm and other fields
      • Click Insert to add another field
    • 10. Synthesize
      • Define the number of rows of data to generate in the data file
      • Specify the file name to save the data to
      • Sample generates a set of data based on the current settings and values.
      • Cannot edit synthesized data (through wizard) once wizard is closed. Data must be manually manipulated
    • 11. Exercise
      • Open the Registration script
      • Create a data file using the Synthesize feature with all the fields
      • Databank all the fields
    • 12. Review 6
      • How many databank files can you attach to a script?
      • How many parameters can you databank within a script?
      • Why wouldn’t you want to run the default content comparison tests on a page, following a Data Banked form submission?
      • Can you map multiple parameters of the same name to the same variable? If so, when would this be useful?
    • 13. Data Bank “Issues” Introduction to Oracle Application Testing Suite: e-Tester
    • 14. Potential Data Bank Problems
      • Navigations may break when using a data bank
        • Failed navigations are due to dynamically changing HTML
        • EXAMPLE:
          • During record, the user searched for “dogs” and clicked on the search result link “I-love-dogs.com”
          • During playback, e-Tester searched for the Data Bank value “cats” and the link “I-love-dogs.com” was not contained in the search results.
    • 15. Identify The Failure
      • Look in the Summary column of the Results Log to identify the failure.
      • The example above Failed to Navigate on page 5, due to the link not being found.
    • 16. View The Actions
      • Look at the Address/Properties, for the page that failed, to determine what actions were needed to navigate.
      • The action recorded, in the example above, clicked on the link with the text “Oracle”
    • 17. View The Differences
      • View the textual differences, on the page prior to the one that failed, to determine what content changed on the web page.
    • 18. Match The Failures And Differences
      • Compare the failure to the content differences found to see if they match.
      • In the example above, the recorded html (blue) contained the link “TER” and the tested html (red) contained the link “MSFT.” The summary column shows that the navigation failed because the “TER” link was not found.
    • 19. Understand What Happened
      • After concluding that the navigation failed due to a change in the page content, it is important to understand what happened.
        • The HTML changed due to a data banked form submission.
        • The result links changed due to a data banked form submission.
        • The link that e-Tester used to navigate during record did not exist upon playback.
    • 20. Solutions To Data Bank Problems
      • Potential solutions to problems caused by using a data bank include:
        • Re-record the navigation
        • Modify the navigation
    • 21. Resolution Considerations
      • When deciding which solution to use there are a few things to consider:
        • Re-record the navigation: This resolution will only correct the problem for the current data record, not for all records in the Data Bank file.
        • Modify the navigation: This the easiest and fastest resolution.
    • 22. Modifying Navigations
      • There are two ways to modify navigations:
        • Modify the action
        • Modify the object’s location criteria
    • 23. Modify The Action
      • To modify the Action:
        • Open the Address Properties
        • Double-click on the action to be modified (this will open the “Event Properties”)
        • Edit the Object Path
    • 24. Location Criteria
      • e-Tester locates objects, used for navigation, based on the following criteria (in this order):
        • The type of object selected
        • An obtainable attribute of the object
        • The object’s position in relation to other objects in the same collection.
    • 25. Location Criteria
      • Below is an example of an object path:
        • Object Type = link
        • Obtainable Attribute = text (“TER”)
        • Object Position = index 15 (16th link in collection)
    • 26. Think About Location Criteria
      • In some cases, the second location criteria, object attribute, is dynamic. In these cases, navigation will fail if an object with the specified attribute can not be found.
      • If the object attribute is dynamic, and the object position is static, it makes sense to switch the order of the location criteria.
    • 27. Modify Location Criteria
      • To modify the location criteria:
        • Open Address/Properties…
        • Check the Base Final Event on Index checkbox.
        • Note: This is usually not necessary if eTester is allowed to use the index as a secondary attribute
    • 28.  

    ×