After playing with the WinRunner eval copy, I notice that the test scripts and data generated by WinRunner are rather loosely organized (in file directories). We need to version-control the test scripts & data, and put them in configuration management tools (e.g. Continuus). If you have experience version-controlling WinRuner test scripts/data, what do you think? Is it relatively easy and painless?
Any suggestion, idea, insight will be greatly appreciated!
But it will be better if WR itself provides the Version Control System, meaning from single menu item ( Check In/Commit) should check in the necessary files to the repository, instead of manually check in the necessary files.
Here is the assignment description of a work that I've to do:
<font color="blue"> Improve coupling CMSynergy version control system.
As components and documentation change over time, a coupling with the version control system 'CM Synergy' has been made to retrieve the latest versions. However, only one client is used to query the database, which causes problems on reaction times and availability.
Increase the number of clients to speedup reaction times. Make sure enough clients are running and also allow clients from other databases. </font>
Does anybody has an idea on how I can solve the problem?