>> 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???
> On the other hand, testing multiple major classes like that together
> is more of a module test than a unit te
On Mon, 19 Nov 2007, Derek Gaston wrote:
> 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 s
