When you launch QTP, you will notice that the Process Guidance pane shows you a path to achieve what QTP has popularized in the Testing community as “Keyword-Driven Testing”.
[Keyword Driven Testing is a technique that separates much of the programming work from the actual test steps so that the test steps can be developed earlier and can often be maintained with only minor updates, even when the application or testing needs change significantly]
[The keyword-driven methodology is especially useful for organizations that have both technical and less technical users because it offers a clear division of automation tasks. This enables a few experts to maintain the resource framework while less technical users design and maintain automated test steps. Additionally, after the basic infrastructure is in place, both types of users can often do their jobs simultaneously. ]
[Writing your scenarios at the right level of abstraction is critical to building an effective test suite. Here are a few guidelines that can help you get there.
- Tests should be independent of the user interface of the application.
- Tests should strive to be at the highest level of abstraction possible, without sacrificing readability.
- Don’t repeat yourself: Repeating a series of steps at any level — at a scenario, or in the implementation can increase the maintenance overhead.
- Use Extract Concept and Push to Implementation to achieve granularity that reflects your domain and also promotes reuse
- Your test should ideally be an illustration of the functionality as opposed to some UI mechanics. For instance, if a test reads:
- enter “5” in units and “10.0” in price and select “air shipping” in shipping dropdown
Description of the UI clutters the intent here. Instead the test:
- create order for “5” units at price “10.0” for “air shipping”
helps clarify the intent.]