I am using CVS. Assume, you have OR in text format (what XML is), what you gonna do with it? I have ORep 6 MB. I work with XML only if I need mass changes, such as format of all html ids changed from ID:XXX to BO:ID:XXX. So you have multiple environments, what is a difference in the test between them? Do you have a different OR for each environment?
On Aug 18, 11:00 am, jpl171psu <[email protected]> wrote: > hi I appreciate your response.. Are you currently doing any > versioining with QTP? If so what tool are you using? So by branching I > mean having multiple versions for different environments. Then when > the application code is merged into production, and all the other > multiple QA envinronments are updated with the latest production code, > we would have to do the same with our framwork to support the changes > across the multiple environments. To support multiple environments > manually would be a huge task and seems unnessary. I don't know why > they designed this tool to use binary files, in a true development > shop it would make sense to want to do branching which requires > merging at the end.. The library mapping files that are part of the > QTP test it's self are in binary format, not > unicode.http://mercuryquicktestprofessional.blogspot.com/2006/11/some-useful-... > > Switching our framework over to .vbs files instead of the use of > actions eliminates the dependency on most of the binary files within > the QTP test. Those would now just be generic files and get reset > during runtime based on the code we add for the API. We know it is > possible to import/export xml files within the repository manually. > But was hoping that someone may know of a way using the automation > model within the QTP API to do this. I have not seen methods in the > documentation provided with QTP that supports this. We want to cut out > any manual intervention that we can for merging. > > On Aug 17, 2:55 pm, Roman Zilber <[email protected]> wrote: > > > By "branching" do you mean version management? Obj Rep can be > > exported/imported as XML, but there is no reason to do it, you will never > > merge big XML files manually. All normal version management tools support > > binary file format. Library files should be in unicode format. > > > On Mon, Aug 17, 2009 at 1:29 PM, jpl171psu <[email protected]> wrote: > > > > Hi, > > > I was wondering if anyone has had any experience with branching > > > concepts with QTP. The thing that makes it impossible for branching > > > with QTP is the fact that there are multiple binary files associated > > > with the QTP test. We have figured out a way to eliminate our > > > dependency on actions and library resourses by using functions and > > > mapping these at runtime. Thus eliminating our dependency on the > > > binary files. The only thing that we are left figuring out is the > > > Object Repository. Does anyone know if it is possible to load a xml > > > file to the obj rep at runtime? Or if anyone has any experience with > > > attempting the same thing we are with versioning/branching, I would > > > love to exchange some ideas. Thanks- Hide quoted text - > > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google "QTP - HP Quick Test Professional - Automated Software Testing" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MercuryQTP?hl=en -~----------~----~----~----~------~----~------~--~---
