Introducing Test Objects and Object Repositories
Before you create a test, you need to set up the resources
that will be used by that test. One of the most important resources for any test
is the object repository. An object repository is a storehouse for the test
objects (and other object types) used in your test.
Test objects are stored
representations of the actual objects (or controls) in your application.
QuickTest creates test objects by learning a select set of the properties and
values of the objects in your application. QuickTest uses the information it
learns to uniquely identify the run-time objects in your application.
Each test object is part of a test object hierarchy. For
example, a Link object may be part of a Browser/Page/Link hierarchy. Top-level
objects, such as Browser objects, are known as container objects, as they can
contain lower-level objects, such as Frame or Page objects.
Note: Object repositories can also include checkpoint objects.
These object types are covered in Creating
Checkpoints and Using Functions.
Run-time objects are created
and maintained during a QuickTest run session by the object creator (for
example, Microsoft for Microsoft Internet Explorer objects, Mozilla for Mozilla
Firefox objects, the product developer for ActiveX objects, and so on). During a
run session, QuickTest performs the specified test object method on the run-time
object. Run-time objects are not stored in an object repository, as they are
available only during the run session.
No comments:
Post a Comment