NUnit is worth to use ??

[goodmorningsky]

Hi, all.

I've know NUnit for a while, now I try to use it.

Most of application I develope is data base driven.

I want to test data layer most with may input and checking the result, then compare with database if it returns right value or not.

 

To do so, I need to save all inputs and results as development, debugging goes on..

 

But, NUnit doesn't seem to support it. and It require wrong Test coding.

I dont' feel still confident that it's worth to use it. Since It takes time to write test code. I hope they provide auto test code generation reading dll and generate test code for NUnit, So, I just type only input param. This is what I desire.. One more thing, there is functionality to save all my inputs so I can reuse the input after debugging to make sure all code still work correctly.

If I can't do this with tool what the tool is for?

 

How do you guys use the tool in real world?

and What is best way to use it in my case?

Is there any other tools I can work with as well as NUnit??

 

Any comment will help!!

Thank you..

[Nerseus]

I'd suggest the following book:

Test-Driven Development in Microsoft .NET

 

It goes into detail on how to test DB related code as well as webservices, another tricky one. The basic idea is to have a "fake" set of data using NUnit. For example, in order to test some insert code, you have to know what you're inserting and verify that it got inserted. It's tedious, but worth it the very first time someone reports a bug. If you have a medium to large sized project you may think that the test code is going to take way longer to write - and you'd be absolutely correct. But, when you get near the end of the project and people start reporting more bugs (even when they're really just Change Orders), the test code will start to show its value.

 

-ner