Keyword Driven Methodology


It is a Test Creation Methodology which involves selection of keywords. Keywords Indicate Operations to be Performed and Meant for Structured Test Creation. It creates Structured Tests – Easy to Update & Maintain.

It is suitable for companies having technically expert users: For Maintaining Resource Frameworks and companies having less technically proficient users for for design & maintenance of automated test steps. The objective is clear division of automation tasks.

Keywords can be come from
  • Built in keywords from QTP itself
  • Our own user defined keywords
Resources and infrastructure required:
    • Shared object repositories
    • Function libraries
    • Recovery scenarios
    • Persons with thorough knowledge of application
    • Expertise of QTP Software
    Steps to implement keyword driven methodology in QTP:
  • Analyzing the application to find out the testing needs: Find out the Application’s development environment like Web, Java or .NET. Load the desired QTP add-ins and find out the business processes and functionality we want to test.
  • Setting up the object repositories: Decide how to divide our actions, build resources to be used by our tests, the most widely used resource is the shared object repository.
  • Creation of function libraries: Creation of function libraries containing functions which extend QTP functionality and use these keywords to build keyword-driven tests.
  • Configuration of QTP according to the testing needs: Setting up of preferences like global testing preferences, run session preferences, any test specific preferences. Creation of recovery scenarios to instruct QTP how to proceed when a step fails and configuration of QTP window to easily access panes like the test flow pane, the resources pane and the available keywords pane.
  • Building of the tests: Construction of the tests by inserting calls to the relevant actions from the tests. Creation of one or more empty tests and addition of actions to them. Association of the object repositories with the relevant actions. Association of the function libraries and recovery scenarios with the relevant tests, so that steps can be inserted using keywords and configuration of test preferences.
  • Addition of Steps to the Test Actions: Addition of steps which use the keywords created in previous steps, enhancement of tests by inserting checkpoints and output values – to verify that the application is behaving according to expectations and addition of programmatic statements to enhance the tests further.
  • Running, analyzing and troubleshooting the tests: When the tests are ready, run them, view the results and troubleshoot the tests, as needed.

No comments:

Post a Comment