Android 13.0.0 release 36
Allow @TestCaseName to be for names that are compatible with CTS/AJUR am: deb706635e am: a4ec4e26a9 am: 97bb2c51d7 am: 7e97deb1b6 am: cd5c1d11b3

Original change:

Change-Id: I3476c1eae468616a0de36fa95cc5a40a584df024
Signed-off-by: Automerger Merge Worker <>
tree: 74e54202b20114ddf260e2fe8c3515667eb96c1f
  1. apidocs/
  2. lib/
  3. src/
  4. Android.bp
  5. LICENSE.txt
  9. pom.xml
  12. README.version


Build Status Coverage Status Maven Central

Parameterised tests that don't suck


public class PersonTest {

  @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


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):


JUnitParams is available as Maven artifact:


If you want to see just one simple test class with all main ways to use JUnitParams see here:

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