> Now, I am all for re-organising the tests if it makes more sense and so on > (they are surely a mess at the moment). But I think that complaining about > others is extremely counter-productive. I also worry that once again we > will focus our energies on "re-organising" to the way we individually might > like things, rather than actually moving things forward (OK - this I admit > is cynical).
Let's make sure we spend our time understanding what is there and improving our overall testing strategy. > The general thrust of this discussion has been good. And I think I like the > way the discussion is going - however I do *not* want to rush into > anything. Further there is always a temptation to move the existing tests > "out of the way" to make room for pure unit tests, and to remove the > existing tests from the build. > > This would be a *HUGE* mistake. +100 > However I think the first step should probably be to examine and document > what tests we have at the moment. We already have people who are possibly > existing tests that are already there. The problem is that such a > documentation task isn't high up on anybody's list of fun tasks... and I > doubt that anyone is going to volunteer to do it? Like I said, I'm a > hypocrite since I'm not going to commit myself to doing this, even though I > know it needs to be done. I'll do that, as this is very important. I hope people will help me though as this is not a funny task. Arnaud
