views:

475

answers:

5
+3  A: 

To be blunt, this sounds like you're looking for reasons not to do it. Just get NUnit and get going. Start with the smallest piece to get your feet wet.

Steven A. Lowe
On the contrary, I want to use unit testing very badly. However, this is something that would need to be rolled out to 100 or so people, and I want to make sure that we invest our time and energy into the proper tools.
Tim
@Tim: this is the kind of information that belongs in your question! "Company-wide" could mean "you and the other programmer" ;-)
Steven A. Lowe
+1, NUnit is great. @Tim, there are many alternatives, some of them good, but the differences are minimal. Just take it and go.
orip
A: 

TestComplete was decent and easy to use when I used it (a couple of years ago). At least then, you'd need to learn some VBScript.

thursdaysgeek
A: 

We use TestComplete from AutomatedQA, and it's a decent platform for doing gui testing. We do all of our TestComplete code in Jscript, which isn't great, but it gets the job done. I'm not sure i'd recommend Automated GUI testing though, I think you'll get a much better return on unit testing.

Nunit and rhino mock are great tools for unit testing.

CruiseControl looks like the best way to set up automated testing on each build.

chills42
+1  A: 

Gallio is actually a framework for the entire testing toolchain. From writing the tests, to running them to post build processes. It provides common facilities and standardized interfaces for each step to allow greater choice and flexibility when putting a build process together.

It comes with a version of the MbUnit framework, which it uses by default. It also comes with a GUI runner named Icarus, and a console runner named Echo. They are all well respected tools in the testing community.

It is an excellent choice for a large company, since it can allow you to take advantage of many of the popular testing and continuous integration tools with a minimum of integration headaches.

Picking a framework and writing tests is only half the battle, Gallio really does help with the other half; gluing up all the other steps in the build process.

The only real downside at the moment is the lack of a central repository of examples and information. For some, the fact that its a relatively new initiative may put them off using it right now.

Check out the docs here. They are a work in progress and very incomplete but will get you started on the basics of writing tests. Keep your eyes on Jeff Browns Blog for other information.

Jim Burger
A: 

I would recommend to take a look at Ranorex. It is a GUI test automation framework for testing many different application types (Win32, Winforms, Web 2.0, WPF, etc.). Since Ranorex is a .NET based automation framework you can write your test code also in C# and VB.NET and combine it with your unit tests.

gherget