Over a million developers have joined DZone.

Doing more with less in JUnit 4

· Java Zone

Microservices! They are everywhere, or at least, the term is. When should you use a microservice architecture? What factors should be considered when making that decision? Do the benefits outweigh the costs? Why is everyone so excited about them, anyway?  Brought to you in partnership with IBM.

JUnit is a popular testing framework for writing unit tests in Java projects. Every software engineer should always try to consider using less code to achieve objectives and the same is true for test code. This post shows one way to write less test code by increasing code re-use using JUnit 4 annotations.
Ok, so let's set the scene. You have a bunch of tests that are very similar but vary only slightly in context. For example, let's say you have three tests which do pretty much the same thing. They all read in data from a file, and count the number of lines in the file. Essentially you want the one test to run three times, but read
a different file and test for a specific amount of lines each time.

This can be achieved in an elegant way in JUnit 4 using the @RunWith and @Parameters annotations. An example is shown below.

@RunWith(Parameterized.class)
public class FileReadTest {
   @Parameters
   public static Collection<Object[]> data() {
            return Arrays.asList(
              new Object[][]{{"players10.txt", 10}, {"players100.txt", 100},
   {"players300.txt", 300}});
   }
 
   private String fileName;
   private int expectedNumberOfRows;
 
   public FileReadTest(String fileName, int expectedNumberOfRows) {
       this.fileName = fileName;
       this.expectedNumberOfRows = expectedNumberOfRows;
   }
 
   @Test
   public testFile() {
       LineNumberReader  lnr = new LineNumberReader(new FileReader(fileName)));
       lnr.skip(Long.MAX_VALUE);
       assertEquals("line number not correct", expectedNumberOfRows,                    lnr.getLineNumber());
   }
}

W.R.T. to code above:

  1. The RunWith annotation tells JUnit to run with Parameterized runner instead of the default runner.
  2. The @Parameters annotation is defined by the JUnit class org.junit.runners.Parameterized.
    It is used to define the parameters that will be injected into the test.
  3. The data() method is annotated with the parameters annotation. It defines a two dimensional array. The first array is: "players10.txt", 10. These parameters will be used the first time the test is run. "players10.txt" is the file name. 10 is the expected number of rows.
So hopefully this makes sense. Not only is this a way to cut down on test code, it is also a way to provide extra testing of your code. Every time you write a test all you have to do is ask yourself if it makes sense to parameterize your test.
Enjoy...

 

From http://dublintech.blogspot.com/2012/01/doing-more-with-less-in-junit-4.html

Discover how the Watson team is further developing SDKs in Java, Node.js, Python, iOS, and Android to access these services and make programming easy. Brought to you in partnership with IBM.

Topics:

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

SEE AN EXAMPLE
Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.
Subscribe

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}