Well ... trying to make the case that you cannot use jUnit 4 because your testcase extends another is simply not correct. It might be more modern to implement a runner in true jUnit 4 style - implying I agree with the sentiment of PLX-446 - but it is an overstatement to claim it cannot be used with jUnit 4.
2014-10-16 21:11 GMT+02:00 Robert Scholte <[email protected]>: > More links? Okay: > https://jira.codehaus.org/browse/PLX-446 > > I've been in situations where I needed the combination of 2 TestCase > extension (I think it was springtest + dbunit) > Since you can only extend one class, you'll run into a huge challenge. > You really want to avoid such situations, so if there's a need > rewrite/move PlexusTestCase, let's do it good so we won't block other > testing extensions. > Things like Mockito and PowerMock are very easy to include when using > JUnit4 Annotations. > > Robert > > Op Thu, 16 Oct 2014 00:28:38 +0200 schreef Barrie Treloar < > [email protected]>: > > > On 16 October 2014 03:49, Robert Scholte <[email protected]> wrote: >> >> "TestCase" is so 20th century... >>> >>> *If* you want to do it, please make a TestRule of it. >>> See also https://jira.codehaus.org/browse/MPLUGINTESTING-28 >>> >> >> >> Alright, I'll bite. >> Send me more links on why this is better? >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- -- +==============================+ | Bästa hälsningar, | [sw. "Best regards"] | | Lennart Jörelid | EAI Architect & Integrator | | jGuru Europe AB | Mölnlycke - Kista | | Email: [email protected] | URL: www.jguru.se | Phone | (skype): jgurueurope | (intl): +46 708 507 603 | (domestic): 0708 - 507 603 +==============================+
