Community
Participate
Working Groups
It should b ecool if JUnit test could provide codeminings to show as codeminings before an test method: * Status test * Run button to launch the test * Debug button to launch the test
Created attachment 272082 [details] JUnit demo CodeMinings Here a demo with my current work.
From the demo, it seems to add the status/run/debug on a method based on the @Test annotation. It should also work with JUnit 3 tests having no annotation and JUnit 5 tests which can have any composed annotation in place of @Test, test interface default methods etc. (see http://junit.org/junit5/docs/current/user-guide/). For the test results, you should also think about the parameterized tests and dynamic tests from JUnit 5.
@Noopur thanks for your information. IMHO I think Junit core should provide a isTestMethod(IMethod method). I have created a bug for that https://bugs.eclipse.org/bugs/show_bug.cgi?id=531779
@Noopur do you think we could integrate this issue in 4.10? If yes I will start to create a gerrit patch.
(In reply to Angelo ZERR from comment #4) > @Noopur do you think we could integrate this issue in 4.10? If yes I will > start to create a gerrit patch. I think we already have enough critical stuff related to references/implementations code mining to fix for 4.10 before adding this new use-case. Adding JUnit mining would cascade to discovery and need to fix several bugs (which is fine), but we don't really have enough time to grow the list of bugs to fix before the release. I think 4.11 is a better target both technically, and also as it's be a nice thing to add to the N&N (which already looks nice with references/implementations for 4.10).
This can be taken up after existing open bugs related to code minings are fixed.
