Yeah, "long" tests and things like that are exactly what I was thinking.
I should add that there are several nuances that will require a review of all
downstream labs projects etc., that inherit from jclouds-parent. Testng is
flexible with regard to these groups, but certain things like @BeforeXXX
annotations in parent test classes also respect group names and you must
specifically name the group or tell them to run every time or else the bare
@BeforeXXX annotations won't run. I see evidence from early jclouds code that
this was known, but some more recent work doesn't take that into account.
I am also capturing test statistics to compare the old and new approach to make
sure we get the same tests run :-)
I'll try to get this published in a PR soon so you guys can see the changes
required and discuss options.
Thanks,
Chris
--
Chris Custine
On July 25, 2014 at 11:29:43 AM, Ignasi Barrera (n...@apache.org) wrote:
> +1000 that would be highly appreciated.
>
> There has been a recent discussion to include a new kind of test group
> ("long" tests) and this will make that config much cleaner.
> El 25/07/2014 19:05, "Andrew Phillips" escribió:
>
> > I will open a PR with my code later today but I just wanted to throw this
> >> out there for comments.
> >>
> >
> > +1! I don't think there's any particular reason for us to stick with the
> > filename-based approach if this works now...
> >
> > Thanks!
> >
> > ap
> >
>
