Sequence of logical steps: 1. my lib contains lots of templates [I don't mean a .lib/.a file, just a codebase to be shared, -- kind of like boost is mostly header-only] 2. until end user usage is widespread, the templates are only instantiated in my unittest++ testcases 3. keyword substitution can mask my errors and cause me to lose face claiming to future users that "everything's been tested"
On Nov 22, 2009, at 10:01 AM, Clark Gaebel wrote: > I don't quite understand. Libs and dlls are also compiled. Unless you're > building a template-only library, it should work fine and without confusion. > Also, accessing private and protected members is entirely optional, and > UnitTest++ will continue to work perfectly with just public access. > > -----Original Message----- > From: Vlad [mailto:v...@demoninsight.com] > Sent: November-22-09 1:02 AM > To: UnitTest++ development and use > Subject: Re: [unittest-cpp-devel] Testing your privates > > > On Nov 21, 2009, at 9:21 PM, Clark Gaebel wrote: > >> Interesting. I think I assume that tests are being run as a post-build to >> the main executable's compilation as that's the only way I've ever set it >> up. I don't think this is such a big deal because the main program will > fail >> to compile, stopping the tests from being run. Even if it doesn't stop > them >> though, you've still got compiler errors on the main project. >> >> Or am I missing something? > > > Consider a use case of someone developing a library for others. In this > case, there is no "main executable" as such, but there should be a test > suite. [e.g unittest++: it's only main() is its own test suite.] In my > current project, I deal with templates a lot and it's typical to see errors > only when templates get instantiated (at the moment, mostly inside my > testcases as the users haven't fully caught on to the API) -- I wouldn't > want that process to be subtly subverted with keyword redefinitions... ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ unittest-cpp-devel mailing list unittest-cpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unittest-cpp-devel
