NUnit is worth to use ??

[Sky Kim]

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..

 

[Helge Jensen]

Hi, all.

Hi there, controversial topic you've chosen, I'm expecting a lot of
traffic in this thread... possibly something like "you need to use
state-pattern, and store it as a member in the test-class"

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

I''ve used a few unit-test frameworks and have formed an opinion by now:
Unit-test frameworks are:

- applicable only for unit tests
- basically give you a success and failure-count

Integration tests are very hard to express in Unit-test terms, since
unit-tests usually are assumed to be unparametrised.

As you see, I'm not so fond of unit-test frameworks. Usually you end up
using some "configuration-language", which is not as powerfull as the
source-language and really dominates the way you code.

My current approach to testing is:

- Write tests, if a test is hard to write it will also be hard to
write the code that actually uses your library/class/... and something
may be wrong with the design (GUI tests are different)

- Code tests just like any other code, don't sacrifice simplicity to
fit into frameworks

- throw exceptions to indicate test-failure, be as specific as you
think is valuable, start with new Exception("reason"). Then refine that
to an exception with more information if an error is actually caught there

- dont use Assert(bool-expression), it removes meaning, define
functions like AssertEqual(object o1, object o2), that can throw
informational exceptions like "should be equal: {0}, {1}".

- compose sequentially dependent tests using language-sequencing:
void testFoo(DB db) { testBar(db); testBaz(db); }

- compose independent tests in adhoc-ways, whatever fits:

try {
testFoo(DB db);
} catch ( Exception e ) {
fail("testFoo", e, db);
}
try {
testBar(DB db);
} catch ( Exception e ) {
fail("testBar", e, db);
}

// or even (for the adventurous)
delegate void DBTest(DB db);
DBTest[] tests = { new DBTest(testFoo), new DBTest(testBar); }
foreach ( test in tests ) {
try {
test(db);
} catch ( Exception e ) {
// delegate wraps execptions
fail(test.Method.Name, e.Inner, db);
}
}

This approach makes for simple, easily readable, flexible tests, on the
downside, you have to count the successfull tests explicitly, if you
even care about how many there are.

Remember, tests are just programmes, and you should not write them any
differently than you would an actual program.

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.

Sounds like integration tests.

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

Sounds reasonable, if the framework makes testing hard, it probably
isn't applicable

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.

Are you suggesting to "capture" the input and output during debugging?
and then automatically replay the interaction later?

Try doing this manually a few times before going "auto", if you havent
already done so. Perhaps you would rather just save verified "positives"
of input and output -- atleast for a start.

Is there something wrong with just serializing the inputs and verified
output, then for testing: deserialize input, send, deserialize
expected-output, compare with actual output?

How do you guys use the tool in real world?

NUNit, not anymore.

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

To do what fits your situation... (obvious, but sadly much ignored

 

[Nick Malik [Microsoft]]

Check out NMock. It generates much of the mock object framework that is
needed to test a class seperately from the classes that it depends upon.

Not perfect, but pretty good.

--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.