maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arnaud HERITIER" <>
Subject Re: Sane plugin testing
Date Fri, 08 Aug 2008 11:41:15 GMT
> >
> > ITs are needed for example in plugins when we wrap another tool, but
> > otherwise, and particularly in the core we should have a good unit tests
> > suite.
> In plugins world, we have a lot of UTs with our test harness and ITs.
> I think ITs is sometimes misunderstanding by dev or users wich provide
> patches. IMHO ITs should be used only if the test needs the Maven
> stack or a part like reactor or aggregate properties for a mojo. In
> the real world, users open issues with test cases like MJAVADOC-110 or
> MJAR-60 and dev just adds these test cases as ITs. So,  what to do if
> a user propose a test case? Add it as an IT or transform it to the
> plugin harness?

ITs are good, and especially for plugins.
We have effectively a lot of ITs submitted by our users, but often we (I'm
the first one the list) doesn't do the necessary to create UTs to check our
new developments.
Thus we have to keep ITs, but we have also to add UTs.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message