mevuorin

I've tried CUnit and Check for unit testing in c. CUnit has so far seemed good: it's simple and powerful enough. Check is probably better than CUnit, but I couldn't realy use it, because I'm novice to GNU autotools and the only Check tutorial I found used autotools a lot and figuring out why I got a weird errors following the tutorial became too hard. I switched back to CUnit for now and study autotools more when I'll find time.

Have you used Check, CUnit or other unit testing frameworks? Which one would you choose?

I think I've heard/read somewhere, that CUnit could be integrated with eclipse. I've tried to find information about that, but have had no luck. Am I just dreaming about easy c unit testing using eclipse?

jim mcnamara

Dreaming? Probably.

We looked extensively for tools for unit testing and complete QA. In the end we do the following for unit testing:

1. use Clint - zero warnings required.
2. bought and use PolySpace verifier (static code analysis)
3. ported existing code to generate McCabe numbers (cyclomatic indices) and other static measures.
4. Based on the results of the above, we have a defined unit test suite set of procedures we run our code through, we know the expected outputs ahead of time. If the any of the above numbers or performance numbers are not good or there are issues with expected results, we have to back pedal into development.

5. All of the above results a stored in Serena TeamTrack, then passed on to official QA.

I have one blob of C code that takes two-three days just to unit test.

mevuorin

You're involved with a lot bigger projects than I am. I'm doing projects with just few thousand lines of code. I guess most of the techniques you're using would be too heavy for small projects like mine. I think I'll start using lint though. I had forgotten it. Thanks for reminding.

Wow. Thats one big blob. :eek: How many lines of code?

jim mcnamara

100K lines of C code - several dozen C modules, plus 30 standard database interface C modules.