There are times when major changes need to be applied to a repository. Such an example is when a deployed application is moved from a local test server to a server in a pre-production environment. Nothing should change except for the URL, which unfortunately is hard-coded into every single object in your repository.
- Open Object Repository Manager [Resources > Object Repository Manager]
- Open your project repository [File > Open] Export to XML [File > Export to XML]
- Enter a filename [exported.xml]
- [ok]
- Open you’re favourite XML editor (i.e. Notepad++)
- Find and Replace on the current path to the new path
- Do any other maintenance work
- [Save xml-doc]
- ensure document is well-formed
- [Close xml-doc]
- Meanwhile… Back in Object Repository Manager
- Import from XML [File > Import from XML]
- Save your Imported repository [imported.tsr]
- In the file system, delete repository.tsr and exported.xml
- Rename: imported.tsr to repository.tsr
Note: You will need to open a different QuickTest project and then reopen your current project for the results of the merge to be visible in the Object Repository. It’s a pain, but that’s the way of things.
|
Ryan Boucher is a Software Inquisitor and is passionate about it. You can find a whole raft of articles and anecdotes about software testing and other topics he gets excited about. |
| Tags |
2 Responses to “QuickTest : Applying major changes to a repository”
Nice tip.
Remember though that object properties can be defined using regular expressions.
So, instead of doing this each time for an environment shift, do it once with regular expressions defining the variety of environment urls or even better do it when your creating the objects.
eg:
http://URL1|http://URL2|http://URL3
Cheers, I hadn’t thought of that. I love regex.