On 3/26/07, Brett Porter <[EMAIL PROTECTED]> wrote:
On 26/03/2007, at 4:45 PM, Jochen Wiedmann wrote: > On 3/26/07, Brett Porter <[EMAIL PROTECTED]> wrote: > >> So, this indicates the problem with the test (and how to reproduce >> it) - it can't depend on running the plugin itself unless it's an >> integration test. The unit tests should be simplified to some >> quicker, unit-testing tests, and the long tests made into integration >> tests. > > I might help by rewriting the tests using the plugin-testing-harness. > (That would fit "quicker, unit-testing tests", doesn't it?) I would have thought that was what was there before - to be honest I haven't actually looked into the current tests (but it's on my list as part of a general review of how we are testing plugins before I started doing them for surefire).
We need to look into this. I'm sorry but before that the tests were hardly understandable.
> > Can you specify what the "long tests" are? I have no idea what to do > in that area. I just noted that there are currently 2 test classes that take 20 seconds each - IMO too long for unit tests.
Nothing to do with the actual test. The processing is slow, not the test itself. This needs to be improved. Whatever solution is choosen is fine by me provided that we can build use cases using standard maven project. Stéphane
- Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
