> I do like CPPUNIT. It has it's drawbacks... but there's not really > any reason to use anything else. In particular Boost.Test has _many_ > drawbacks (as Boost stuff often does)... mainly that it's just tough > to work with. CPPUNIT is straightforward.... and does it's job well.
OK, the libmesh_tests/cppunit contents have been moved to libmesh_tests/ and the other stuff is gone. > Here at INL I'm implementing more like "system" tests. We don't > really have a lot to unit test... so I'm basically checking against > analytic solutions then archiving those solutions and just ensuring > that we keep getting ~ the same answer. Not the best... but it helps > with large regressions. I'm using exodiff for this (which helps with > the ~ part)... and it's all getting integrated with Trac and Bitten so > that tests are automatically run after each commit. > > Derek Cool. Roll those in when they are ready, and let's figure out a way to get the results uploaded to the web page. -Ben ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
