@parameters in Junit 4

Question

Can I have more than one method with @Parameters in junit test class which is running with Parameterized class ?

@RunWith(value = Parameterized.class)
public class JunitTest6 {

 private String str;

 public JunitTest6(String region, String coverageKind,
        String majorClass, Integer vehicleAge, BigDecimal factor) {
    this.str = region;
 }

  @Parameters
 public static Collection<Object[]> data1() {
   Object[][] data = {{some data}}

   return Arrays.asList(data);
 }

 @Test
 public void pushTest() {
   System.out.println("Parameterized str is : " + str);
   str = null;
 }

 @Parameters
 public static Collection<Object[]> data() {
   Object[][] data = {{some other data}}
   return Arrays.asList(data);
 }

 @Test
 public void pullTest() {
   System.out.println("Parameterized new str is  : " + str);
   str = null;
 }
}

Answer 1

You can use the Theories runner (search for the word theories at that link) to pass different parameters to different methods.

Answer 2

Probably the data1 method, but no guarantee of that, it'll use whichever one the JVM gives junit4 first.

Here's the relevant code from junit:

private FrameworkMethod getParametersMethod(TestClass testClass) throws Exception {
    List<FrameworkMethod> methods= testClass.getAnnotatedMethods(Parameters.class);
    for (FrameworkMethod each : methods) {
        int modifiers= each.getMethod().getModifiers();
            if (Modifier.isStatic(modifiers) && Modifier.isPublic(modifiers))
                return each;
    }

    throw new Exception("No public static parameters method on class " + testClass.getName());
}

So the first public, static annotated method that it finds will be used, but it may find them in any order.

Why do you have uour test written that way? You should only have one @Parameters-annotated method.

Answer 3

It's not designated to have more than one data method. You can see it in skaffman's answer.

Why it's not provided to implement two data methods?
The answer could be: Coupling.

Is it too complex to split this test up into two testcases? You would be able to introduce a small inheritance and share common methods. With two testcases you could provide two separated data methods and test your stuff very well.

I hope it helps.