Shared OR的一些缺点

1. QTP store OR in binary format which makes it impossible for others to create tools that can help make OR creation easier

2. Shared OR can be shared across Tests. But it can't be edited by multiple users at the same time. Shared OR are not like shared excel files where multiple users can update the file at the same time

3. This is a huge bottleneck when the team's size is big

4. Any wrong change in Shared OR can impact all the Test cases and there is no trace of the changes done. It becomes difficult to track if that object was changed by some other user by mistake or intentionally

5. There is nothing like patial load. As the OR size grows huge and QC integration is also used, the file download delay has significant impact on script initiation time

6. In case we create multiple Shared OR per user and want to merge them into one, then QTP only allows merging 2 files at once. Also the merged OR has to be shared to a new file. This makes the merging process very cumbersome and practically unrealistic to implement

7. Shared ORs cannot be associated with Library files. We always need to utilize an Action for associating Shared ORs. If I have some code which needs to be executed when associated Libraries are loaded, then I can't use Shared ORs as there is no Action loaded yet. This means the Shared OR is unavailable as the Shared OR only maps to Actions