Search code examples
.nettestingnunitteamcityfitnesse

Testing and Continuous Integration architecture approach using nUnit and FitNesse

I'm looking for opinions and thoughts surrounding testing and Continuous Integration using nUnit and/or FitNesse.

We develop applications, both windows and web with .net and are using TeamCity for continuous integration

I'm wondering what is the best way (and tools) to go about testing the various layers of our applications.

For example, should I be using FitNesse for UA Testing Stored Procedure Testing and nUnit for c# Unit Testin

Should I be using FitNesse to test everything? Can I run FitNesse tests from TeamCity and see the output?

Thanks for any help and direction :-)

Solution

  • We're using nUnit for unit testing and FitNesse for story testing (aka acceptance testing, integration testing, etc). We don't use stored procedures but dbFit is a useful add-on to FitNesse that can do that. We use TeamCity to execute the nUnit and FitNesse tests.