i myself have plenty of experience with winrunner. the problem is the other branch of my company is building their automation framework on silk.
we are trying to consolidate and integrate our test effort by using only test tool.
Put together a few testcases that you want to see automated with these tools and have them show you how this is done. Keep in mind that they might be faster at it than you, but this can be learned. Main thing to see is whether it can do the job. Look for:
1 - Amount of code required to do the task. Few code means less to maintain.
2 - Ease of modifying a test (data, logic, ect.)
3 - Readability of code. Does the finished script make sense to you to follow?
4 - Compare the features that you are going to need in the future. (Double-byte language support?, SAP interfaces?)
5 - How easy is it to follow the results from a test. This is where you will be spending a lot of time. It there information to let you know exactly what happened in a test?
I've been using both products with different type of applications. My opinion that Winrunner learning curve is much shorter though for experienced user Silk test has much more abilities. Winrunner was almost useless for our java based application, at the same time Silk was terrific in object recognition. Some other concern is the companies stability. It is clear that Mercury is much more stable company than Segue. The same support level ratio sometimes makes the choice. I would recommend you to use both products because in my practice there is no universal product.
The tool which suits best on the company environment. We need to see the future focus of the company. If we shift the technology then the tools is having comportable etc., Basing all these criteria one should go about taking the decison.
One other factor to consider is whether or not anyone on the QA Team has any programming experience. The only tool out there that will allow you to take advantage of Object Oriented programming techniques is SilkTest.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by RagerXS: One other factor to consider is whether or not anyone on the QA Team has any programming experience. The only tool out there that will allow you to take advantage of Object Oriented programming techniques is SilkTest.
This can have a huge impact on the sucess of your implementation of a tool. If you have non technical users on your team I'd take a look at Certify from Worksoft or Unified Test Pro from sdt corp. These are 3rd generation automation tools that non-technical users can use for automation and I must say we are right in the middle of doing POC's on both and having used all the major tools over the last 8 years I'm very impressed with the Action/Keyword approach these tools are taking. It's not a new concept, but these guys have taken it to the next level.
Life should NOT be a trip to the grave with the intention of arriving safely in an cool and well preserved body, but rather to skid in, chocolate in one hand, beer in the other, body wrecked, totally worn out and screaming WOO HOO what a ride!