JUnit: A Little Beyond @Test, @Before, @After

Fabrizio,

 Have you tried testNG? It has a similar feature and seems easier to use than the example you posted here.

 See @DataProvider annotation. The test runs also display much nicer in eclipse IDE than what you posted in this article. It shows the test method with arguments passed.

 More over it has multi-threaded testing support though I haven't tried @DataProvider option combined with multi-threaded testing.

Hmm, could one not also write a generator extension that hooks in front of JUnit's preprocessor? Then something like this would be possible:

    // @ImagesTest support 

    @interface JUnitGenerator{
        // Marker
    } 

    @JUnitGenerator
    @interface ImagesTestGenerator{
        ImageTestParms[] value();
    }

    @interface ImageTestParms{
        String path();
        String md5();
        int w();
        int h();
    } 

    // Test file

    @ImagesTestGenerator(
    {
        @ImageTestParms(path = "coke.jpg", md5 = "baa62439fb6e5183bd7c7be304dbf45f", w=1080, h=900),
        @ImageTestParms(path = "pepsi.jpg", md5="5e2c9f279cfed2de1260d71ff7b3d9c2", w=1600, h=1200),
        @ImageTestParms(path = "coffee.jpg", md5="efcf7c6bcfad3179c8876a8b184d0551",w=480, h=360)
    })
    public void ImagesTestTemplate(String path, String md5, int w, int h) {
        ImageReader ir = getImageReader(path);
        assertRaster(ir, md5);
        assertWidth(ir, w);
        assertHeight(ir, h);
    } 

At compile time, let a simple AnnotationProcessor (recognizing the marker interface JUnitGenerator) generate the @Test methods via TreeTranslator. JUnit will see things as if you handcoded each and every test method.

-------------------------------------- 

All 3 tests passed.(0.066 s)

     ImageTest_coke passed (0.0 s)

     ImageTest_pepsi passed (0.0 s)

     ImageTest_coffee passed (0.0 s) 

-------------------------------------- 

I realize code generation is a touchy issue, but I always found it handy for testing (although admitedly  I've never done it exactly like this).

Hi Fabrizio - did you submit a patch for this? Was it accepted or rejected? It seems useful to have a name for reference rather than just an index? Something like this could be an extended Parameterized class - such as IdentifedParamerterizedClass.

 Am curious as I am going to use your patch for an upcoming presentation on this feature of JUnit. Will acknowledge you in my presentation and link to this page. Am also going to look at using a file/or group of files to contain the test data.