Benjamin Collins <[email protected]> writes: [...] > I'm not an expert, but if I remember correctly, isn't it one of the > more important principles of unit testing to have only one assertion > per test? In a practical sense, if something was wrong with a render- > body specialization, many tests will fail; it seems that this sort of > thing is very common in the testing suite and if, say, 350 of the 700+ > tests were to fail, how would you go about picking out the real > failures? I suppose some of the complexity would evaporate as > problems were fixed (like fixing syntax errors in C++ templates), but > I'd prefer to see only one test fail for any particular problem.
I think everyone here is aware that this is a problem, but no one had a good idea of how to fix it, so that things are tested without including the full HTML output. --J. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
