views:

880

answers:

10
+4  Q: 

UI Testing Tool?

Looking for a tool to UI testing of a Windows (.NET WinForms) application. The idea is that the analysts will record the tests via some UI and it will be able to be played back over and over again.

Commercial tools are fine but bonus points for free ones.

+1  A: 

Checkout Ranorex, commercial, quite expensive but powerful (not affiliated).

zzandy
+2  A: 

So far I have found:

Comments please if you have used any of these.

Robert MacLean
White is a wrapper around the UI Automation Framework. It adds a neat hook that waits for the process's input thread to go idle before proceeding to the next command, which ultimately means it runs as the speed of your machine and doesn't need Thread.Sleep calls.
bryanbcook
+2  A: 

Some others:

I believe they're both free, and Quail looks really nice!

Razzie
A: 

There are a bunch of similar questions on SO:

In my experience, there are a lot of good open source tools for the web, but not so much selection for open source thick client test automation tools. If you want good support with robust functionality, especially recording, you will need to look at the commercial tools (QTP, RFT, TestPartner, etc...)

Tom E
+3  A: 

TestComplete.

You can definitely use capture-replay to capture and run the test script. But I would suggest that you must at least manually edit your scripts to make them

  1. more readable
  2. easier to maintain.

The good thing about TestComplete is that it is able to look into your form's properties, capture those properties so that you can refer to those properties by their name, not by just screen coordinates.

Ngu Soon Hui
A: 

You should have a look at http://opensourcetesting.org/functional.php A lot of tools are listed here and you should find something that meet your needs.

luc
+6  A: 

(I was going to just comment on an answer above, but ran out of room.) We bought Ranorex, and I wouldn't do it again. Their licensing for 1.5 (what we're using) was unclear. Their written license was per user, their marketing said per machine. Still, enforcement was key-based, and not a big deal when a machine got wiped or a replacement tester came in.

For the 2.0 product, their licensing is now tied to the machine. Reimage a machine and you get to relicense it. I'm just not going to support that kind of hassle with my company's thousands of dollars, and we didn't upgrade.

For what they want for the product, a lot of the functionality could be easily written using the UI Automation Framework. Ranorex is a decent product, but I question its value for the money. We're moving a lot of our new tests to just coding to the UI Automation Framework, as we often end up modifying Ranorex-generated code anyway.

mikestew
+1  A: 

Visual Studio Team Test 2010 is coming with a tool for recording and playing back UI tests. You'll find some pointers at:

Introduction to Record and Playback Engine in VSTT 2010

Alfred Myers
A: 

We were using Mercury TestDirector a few years ago and quite happy with it. (All the caveats as mentioned by others apply.)

Mercury was aquired by HP and the tools have been rebranded as HP QuickTest. Not sure how much has changed, but certainly worth a look.

I tried to include a link to the HP website, but the URL doesn't look too "stable". Not exactly a confidence builder ....

IronGoofy
The actual GUI test was called "Winrunner" and was very splendid last time I used it some years ago.I agree with the caveat about HP. "Your software has entered an endless swamp, where everything is rebranded and renamed , but nothing ever really changes -- an annoying hardware salesman trys to sell you an itanium based workstation"
James Anderson
A: 

Like Tom E stated, do take caution while considering going down the record/playback path for test automation.

See Uncle Bob's article on Ruining your Test Automation Strategy.

The main problem is that the record/playback tools couple the tests to the GUI which makes them very fragile.

Uncle Bob's article does point out that some testing needs to occur on the GUI...but that he recommends stubbing out the business rule code.

Sorry I can't provide you with a specific UI test automation tool...but hopefully this caveat will help you make the best decision on how to employ the tool that you eventually use.

mezoid