Hey guys, So I was thinking of making up some unit tests for my ExodusII reader/writer... but I've run into a bit of a decision. Should we just store a mesh/solution in the unit testing directory (maybe in a ./data directory??) to read in and check to make sure everything is ok? Doing so isn't really a "unit test" as it tests just a bit too much. Ideally, we would make mock objects for everything that the mesh reader needs data from... and only send it that data... without reading anything off disk. But of course, that comes with a pretty hefty overhead of making all of those mock objects and getting them to work just like a mesh would from disk.
So what do you guys think? Is it worthwhile to read a mesh from disk and check some things to see if it did it correctly? Or should we go whole hog with some mock objects??? Derek ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
