Skip to content

Commit

Permalink
Merge 0755c72 into b8647f1
Browse files Browse the repository at this point in the history
  • Loading branch information
mbapl committed Aug 20, 2020
2 parents b8647f1 + 0755c72 commit 5eee9d1
Showing 1 changed file with 8 additions and 2 deletions.
10 changes: 8 additions & 2 deletions README.md
Expand Up @@ -2,7 +2,7 @@

[![Build Status](https://secure.travis-ci.org/Pragmatists/JUnitParams.png)](http://travis-ci.org/Pragmatists/JUnitParams) [![Coverage Status](https://coveralls.io/repos/github/Pragmatists/JUnitParams/badge.svg?branch=coverage)](https://coveralls.io/github/Pragmatists/JUnitParams?branch=master) [![Maven Central](https://maven-badges.herokuapp.com/maven-central/pl.pragmatists/JUnitParams/badge.svg)](https://maven-badges.herokuapp.com/maven-central/pl.pragmatists/JUnitParams)

*Parameterised tests that don't suck*
*JUnit 4.0 parameterised tests that don't suck*

## Example

Expand Down Expand Up @@ -66,4 +66,10 @@ You can also have a look at [Wiki:Quickstart](https://github.com/Pragmatists/jun

## Integration with Spring framework

Since **spring version 4.2** it is possible to integrate JUnitParams and spring. More about this [here.](https://github.com/Pragmatists/junitparams-spring-integration-example)
Since **spring version 4.2** it is possible to integrate JUnitParams and spring. More about this [here.](https://github.com/Pragmatists/junitparams-spring-integration-example)

## Integration with JUnit 5

JUnitParams does not currently support the the `@ExtendWith` mechanism.

In the meantime, see [JUnit 5 Vintage](https://junit.org/junit5/docs/current/user-guide/#migrating-from-junit4-running) to continue using `@RunWith(JUnitParamsRunner.class)` within JUnit 5 codebases.

0 comments on commit 5eee9d1

Please sign in to comment.