Pro's and Con's of unit testing after the fact.
Posted
by scope-creep
on Stack Overflow
See other posts from Stack Overflow
or by scope-creep
Published on 2010-03-22T16:49:19Z
Indexed on
2010/03/22
16:51 UTC
Read the original article
Hit count: 261
c#3.0
|unit-testing
I have a largish complex app around 27k lines. Its essentially a rule drive multithreaded processing engine, without giving too much away Its been partially tested as it's been built, certain components.
Question I have, is what is the pro's and con's of doing unit testing on after the fact, so to speak, after its been implemented. It is clear that traditional testing is going to take 2-3+ months to test every facet, and it all needs to work, and that time is not available really.
I've done a fair bit of unit testing in the past, but generally it's been on desktop automation or LOB apps, which are fairly simple. The app is itself is highly componentized internally, interface driven really. I've not decided on what particular framework to use. Any advice would be appreciated.
What say you.
© Stack Overflow or respective owner