Google Git
Sign in
android / platform / external / junit-params / ab5f9f1d788a2cc59ae0e6b18d527a4f1acd5563
commitab5f9f1d788a2cc59ae0e6b18d527a4f1acd5563[log] [tgz]
authorPaul Duffin <[email protected]>Thu Mar 23 15:33:37 2017 +0000
committerPaul Duffin <[email protected]>Fri Mar 24 11:45:30 2017 +0000
treef709289deffa11c315718fd7f30b9ed3493aef6c
parent99fe7c3891c8a9600d9b568ff50f3e25863d6108 [diff]
Hard code text case name template for AndroidJUnitRunner and CTS

AndroidJUnitRunner and CTS require test names to be a specific
format. The default JUnitParams format is not suitable. This
change forces it to one that is suitable and prevents it from
being overridden using the @TestCaseName annotation.

These are a sample of parameterized and unparameterized test
names. The latter two are from a JUnitParamsRunner based test.

libcore.java.net.FtpURLConnectionTest#testOutputUrl pass
libcore.java.net.IDNTest#test_toUnicode_failures pass
libcore.java.net.InetAddressTest#test_getByName_invalid[0] pass
libcore.java.net.InetAddressTest#test_getByName_invalid[1] pass

Bug: 36074730
Bug: 36541809
Test: run cts -m CtsLibcoreTestCases and check test names of parameterized tests, e.g. those from libcore.java.net.InetAddressTest
Change-Id: Id9a8f8ce9affeb85fb2f410d11e764e99d7287b3
1 file changed
tree: f709289deffa11c315718fd7f30b9ed3493aef6c
  1. apidocs/
  2. lib/
  3. src/
  4. Android.mk
  5. LICENSE.txt
  6. MODULE_LICENSE_APACHE2
  7. pom.xml
  8. README.google
  9. README.md
  10. README.version
  11. RELEASES.md
README.md

JUnitParams

Build Status Coverage Status Maven Central

Parameterised tests that don't suck

Example

@RunWith(JUnitParamsRunner.class)
public class PersonTest {

  @Test
  @Parameters({"17, false", 
               "22, true" })
  public void personIsAdult(int age, boolean valid) throws Exception {
    assertThat(new Person(age).isAdult(), is(valid));
  }
  
}

See more examples

Latest News

About

JUnitParams project adds a new runner to JUnit and provides much easier and readable parametrised tests for JUnit >=4.6.

Main differences to standard JUnit Parametrised runner:

  • more explicit - params are in test method params, not class fields
  • less code - you don't need a constructor to set up parameters
  • you can mix parametrised with non-parametrised methods in one class
  • params can be passed as a CSV string or from a parameters provider class
  • parameters provider class can have as many parameters providing methods as you want, so that you can group different cases
  • you can have a test method that provides parameters (no external classes or statics anymore)
  • you can see actual parameter values in your IDE (in JUnit‘s Parametrised it’s only consecutive numbers of parameters):

Quickstart

JUnitParams is available as Maven artifact:

<dependency>
  <groupId>pl.pragmatists</groupId>
  <artifactId>JUnitParams</artifactId>
  <version>1.0.4</version>
  <scope>test</scope>
</dependency>

If you want to see just one simple test class with all main ways to use JUnitParams see here: https://github.com/Pragmatists/junitparams/tree/master/src/test/java/junitparams/usage

You can also have a look at Wiki:Quickstart

Note: We are currently moving the project from Google Code to Github. Some information may still be accessible only at https://code.google.com/p/junitparams/