Well we want that test the other way, we want it to pass everywhere except the buggy releases 3.3.0 and 3.3.9
Having a test to cover broken behaviour is exactly not what we want imho On Wed 1 Feb 2017 at 23:15, Christian Schulte <[email protected]> wrote: > Am 02/02/17 um 00:10 schrieb Stephen Connolly: > > Sorry we want the inverse, > > > > "(,3.3.0),(3.3.0,3.3.9),(3.3.9,)" > > > > If the test is expected to fail on everything except 3.3.0 and 3.3.9 but > > such a test is not the usecase for this tool > > That's what I was looking for. I have that use case for that MNG-2199 IT > I asked about. Class > 'MavenITmng2199DeprecatedParentVersionRangeTest.java' from the following > commit to branch MNG-2199. > > < > https://git-wip-us.apache.org/repos/asf?p=maven-integration-testing.git;a=commit;h=2348fbc31805560fdd6e1a68dbf7b52e00e0e992 > > > > Prior to this commit the test from that class was in class > 'MavenITmng2199ParentVersionRangeTest.java' with range [3.2.2,) although > that test is expected to fail with all Maven versions but 3.3.0 and 3.3.9. > > Regards, > -- > Christian > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Sent from my phone
