Anybody used QARun and TestPartner? We are looking at a Compuware solution and they will give us either tool at the same price. They say TestPartner is a better tool but does not have as good a shared repository system as QARun. Anyone else have practical experience with both?
Thanks for the replies guys. Compuware told me about the repository problem only supporting a single user in TestPartner and say that should be fixed in January. Unfortunately they will not give us evaluation software but promise to give us our money back withing 30 days if it can't do what they claim it will.
Looks like TestPartner it is.
The language it uses is VBA rather than VB. This is the best way to go (by licensing an established language) it is more advanced than creating your own and you have skills that can be used outside the tool.
We have recently purchased TestPartner and found out that the multi-user support (which is rather significant) will not be ready until at least mid-next year. We were originally told that it would be ready by late 2001 (December).
You mention that you are a complete convert to TestPartner. How are you dealing with the lack of multi-user support, and for that matter the lack of SQL Server support.
The combination of these two issues has caused us to have to write a slew of work-arounds.
Speaking of single-user we now have to maintain a separate database for each tester. It's a bit of a nightmare to have to synchronize multiple databases.
We currently maintain a master database that we try to keep current and have a check out procedure for the individual assets.
Any hints, tips or tricks would be greatly appreciated.
In fairness to Compuware they presented both QARun and TestPartner to us but then pushed QARun. When we asked them why, they were upfront about the multi-user problem with TestPartner but were adamant that apart from this it was a better product than QARun.
If you have multiple users writing scripts could you not just use a SCM tool like PVCS or Perforce (or whatever the developers in your company use) and check files in and out as needed instead of each user having their own database of scripts? Just a suggestion.