Just create a new IT. I can not stress how EASY this is for the
developer, and how much WIN is for the end user. Just create a new IT.
You want a new version of xx-m-p? Just create a new IP. SVN COPY is so
cheap and easy to type, just do it. What is stopping you??? Seriously.
Just create a new IT for any new test.
It is {wrong,stupid,lazy,dumb,broken-by-design,bad,everything
negative} to change an existing IT. Just create a new one. Seriously,
what real objection do you have to creating a new IT? Stop trying to
be creative. Just create a new IT.
blah.
On Sun, Feb 9, 2014 at 11:00 PM, Mark Derricutt <[email protected]> wrote:
> Is it feasible to somehow change the IT test infrastructure to run against
> multiple versions? So that the best of both worlds is available ( at the
> expense of longer build times ).
>
> Thats one thing I'd love to have with the invoker plugin ( not sure if these
> IT tests use that ) for things like the clojure-maven-plugin, so that I can
> use the same IT test projects injecting different versions of clojure.
>
>
>
> On 10 Feb 2014, at 15:21, Jason van Zyl wrote:
>
>> I don't agree with this change and I think it potentially destabilizes the
>> most valuable resource we have for testing stability, but if you don't see
>> this as an issue then I leave it to you to decide.
>
>
> ---------------------------------------------------------------------
> 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]
