Well, I finally managed to get some of my way and we'll be using
automated unit testing for a coming development at work.
Here is what I plan to do to "survive" cppunit evolution:
- only use HelperMacros and TestCase: macros can always be rewritten in
the worst case, and they provide isolation from the framework.
- use a "proxy header": this header will include need cppunit headers.
This provides isolation from the actual location of those header.
- not using assertEquals traits (though I would really like to be able,
it might still evolve)
I believe I should be safe enough with those. Does somebody else have any
experience of using CppUnit in production environment ?
Thanks,
Baptiste.
---
Baptiste Lepilleur <gai...@fr...> http://gaiacrtn.free.fr/index.html
Author of The Text Reformatter, a tool for fanfiction readers and writers.
Language: English, French (Well, I'm French).
|
