¿ªÔÆÌåÓýIt might well depend on the size and complexity of the system. I agree that ten minutes is long, but¡ on a system with several million lines of code and and tends of thousands of unit tests, it could take quite a while, especially if your build tool runs each test class separately to prevent tests from affecting one another.There are a few things you could look into. First, as Adam notes, you may have a lot of tests which are too slow. Unit tests should be very very fast - if they are taking more than a few milliseconds each, they are too slow and need to be rewritten. Second, your system could be too large. There is no reason that a single releasable item should be millions of lines long. Ideally, you should be able to break it into smaller projects which integrate. But, a bit of perspective. The ideal world isn¡¯t always the real one. I have worked on enormously large systems that had very poor unit test coverage, and used functional tests for everything. The full check in suite on one ran over 8 hours, which was mitigated by building once (which took over an hour by itself) and then spawning each test to a separate computer, leading to checkin times of 2-3 hours. Very very painful. ----------------- Author,?Getting Started with Apache Maven <> Author, HttpUnit <> and SimpleStub <> Come read my webnovel,?Take a Lemon?<>,? and listen to the Misfile radio play <>!
|
