[Mono-devel-list] no regression policy for System.XML
jose.cornado at gmail.com
Mon May 30 15:19:15 EDT 2005
My two cents:
I think this should apply to the rest of the code base: the only real
solution is to run everything with each build. The Mythical Man Month
comes to mind.
Excluding the slowest test will be risky. They are slow because they
hit critical/complex paths more often than not. A bug caught here is
worth more than anywhere else.
The problem to solve is to increase the test/unit of time ratio so the
slow and critical tests can be included.
There is a hard limit set by the QA tools but a lot can still be
achieved by playing around with the QA machines/lab setup.
More information about the Mono-devel-list