In general, the local object repository is easiest to use when you are creating simple tests, especially under the following conditions:
Conversely, the shared object repository is generally the preferred option when:
-
- You are creating tests using keyword-driven methodologies (not by recording).
- You have several tests that test elements of the same application, interface, or set of objects.
- You expect the object properties in your application to change from time to time and/or you regularly need to update or modify object properties.
- You often work with multi-action tests and regularly use the Insert Copy of Action and Insert Call to Action options.
==================the following table doesn't associate with the title and I haven't understood the differences between object repository window and manager=============
The following table lists features and functionality, indicating if they are available in the Object Repository window or the Object Repository Manager:
Functionality | Object Repository window | Object Repository Manager |
---|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
Y
|
| |
Y
| Y
| |
Y |
| |
| Y | |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|