Quote:
|
you do need to try them out yourself to find which one of them suits your needs well
|
I can't disagree with that... But, as i'm not well aware of unit testing concept, i'm not sure what are my needs, that's why I have posted my question like this "Hey guy, what unit test do you use, and what do you like/dislike about it", to have many different advices from different users, and help me identify what are my needs which can be filled by such tools...
Quote:
|
One option is to program a (usually small, if you don't want to spend a lot of time) unit test program yourself that fits your personal needs
|
Until now, it's more or less how I work, i make my own test case for each components i'm programming. But it's heavy (one function = N test cases where N is the number or validity spaces of my entry argument), and not really usable for regression tests or really big projects since my tests just stops at the first error, and more over no test coverage rate based on a measure...
So, for now, my needs are:
-test case automatically (more or less, OK less) done by the framework from commented sources: i don't know if some frameworks provide this kind of mechanism, but programs like "splint" (or "doxygen" for another purpose than testing) use comment syntax, maybe some unit testing framework does that too?
-"Real" results reports: not just "One test failed so just stop", but something like %95 success, %5 fail, with file and line for each failures. I hope all frameworks provide this, but maybe not, so if you're aware of one which doesn't, I won't test it.
-Code covered by test case, I want to be sure that 99% of my code is covered by tests, not just rely on my hope that I've not forget one logical branch...
Do you know if Cunit provide these features?
Thanks for any more advice.