About Recording Tests
You record your tests while navigating through your application. As you navigate, QTP graphically displays each step you perform as a row in the Keyword View and a line in the Expert View. A step is anything a user does that changes the content of a page or object in your application, for example, clicking a link or typing data in an edit box. Your test steps represent the operations you perform on your application. During a run session, QTP uses the recorded steps to replicate the operations you performed while recording.
While you record your test steps, QTP creates test objects representing the objects in your application on which you perform operations. This enables QTP to identify the objects in your application both while creating a test and during a run session.
Recording can be useful in the following circumstances:
You are new to QTP and want to learn how QTP interprets the operations you perform on your application and how it converts them to QTP objects and built-in operations.
You need to quickly create a test that tests the basic functionality of an application or feature, and the test does not require long-term maintenance.
You are working with a new application or with major new features of an existing application, and you want to learn how QTP interacts with the application.
You are developing functions that incorporate built-in QTP keywords.
After creating your initial test, you can further enhance it by adding and modifying steps in the Keyword View or Expert View.
Guidelines for Recording QTP Test Scripts
Consider the following when recording tests:
- If you are recording steps on a Web-based application, evaluate the types of events you need to record. If you need to record more or fewer events than QTP generally records by default, you can configure the events you want to record.
- Consider increasing the power and flexibility of your test by replacing fixed values with parameters. When you parameterize your test, you can check how it performs the same operations with multiple sets of data, or from data stored or generated by an external source.
- Consider using actions to streamline the testing process.
- If you have useful WinRunner assets, you can link to WinRunner tests and call WinRunner TSL functions from your QTP test.
- When you record tests, you may not notice that new objects are being added to the local object repository. This may result in many testers maintaining local object repositories with copies of the same objects. When using a keyword-driven methodology, you select the objects for your steps from the existing object repository. When you need a new object, you can add it to your local object repository temporarily, but you are also aware that you need to add it to the shared object repository for future use.
- When you record a test, QTP enters the correct objects, methods, and argument values for you. Therefore, it is possible to create a test with little preparation or planning.
Part –2: Step by Step method of QTP Recording Process.
Go Back to –> QTP Tutorial Learn QTP – Design QTP Scripts
