apache / apache/maven-surefire
[SUREFIRE-2237] Upgrade junit-jupiter to 5.10.2 and junit-platform to 1.10.2
- Dominant language
- Java
- Stars
- 461
- Forks
- 588
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 19
Description
**[Darius Cooper](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=dariusx)** opened **[SUREFIRE-2237](https://issues.apache.org/jira/browse/SUREFIRE-2237?redirect=false)** and commented
junit-jupiter 5.10.x introduced some new classes
Now that [spring-boot-starter-test pulls in that version](https://mvnrepository.com/artifact/org.springframework.boot/spring-boot-starter-test/3.2.2), tests give an error when we upgrade to the latest Spring. It would make things easier if surefire used the latest versions.
(Cloned SUREFIRE-2157, because that was a very similar change)
I did [notice this](https://github.com/apache/maven-surefire/blob/2fed802397f8c7de4cfc72f49ab4565e72f7aab7/pom.xml) **warning comment** in the parent pom:
```java
org.junit
junit-bom
5.9.3
pom
import
```
---
**Issue Links:**
- [SUREFIRE-2157](https://issues.apache.org/jira/browse/SUREFIRE-2157) Upgrade junit-jupiter to 5.9.2 and junit-platform to 1.9.2
(_**"is a clone of"**_)
Contributor guide
Research direction
Start in the parent pom at the junit-bom dependency and read the warning against upgrading beyond 5.9.3. Compare the related SUREFIRE-2157 change, then run the project tests with JUnit 5.10.2 and platform 1.10.2; done means the upgrade no longer causes the reported failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100