issues Search Results · repo:junit-team/junit5 language:Java
Filter by
2k results
(88 ms)2k results
injunit-team/junit5 (press backspace or delete to remove)!-- Start by telling us what problem you’re trying to solve. Often a solution already exists! Please, don’t send pull
requests to implement new features without first getting our support. --
Currently, ...
component: Jupiter
theme: extensions
type: new feature
marcphilipp
- 1
- Opened 21 hours ago
- #4434
According to the documentation, it should be possible to get the injected parameters from the store in a Junit
extension. From the docs:
Other extensions can access the parameters and resolved arguments ...
component: Jupiter
status: works-as-designed
theme: parameterized tests
type: question
Yspadadden
- 3
- Opened 2 days ago
- #4431
AnnotationHelper provides false guarantees in getXxxMethods and getXxxFields return type.
Context
- Used versions (Jupiter/Vintage/Platform): junit-jupiter-params, all versions up to 5.13.0-M2
- ...
status: invalid
neboskreb
- 2
- Opened 2 days ago
- #4428
Arguments class is not Generic, and neither is of this probably cant be changed, but I m thinking we could do cleaner,
or at least more idiomatic than this.
static class Clients implements ArgumentsProvider ...
status: team discussion
theme: parameterized tests
theme: programming model
type: enhancement
xenoterracide
- 2
- Opened 4 days ago
- #4421
When using AutoExtensionRegistration together with the include and exclude properties, the ServiceLoader should not
throw an exception for extensions that would be filtered out anyway.
Currently, this ...
component: Platform
status: waiting-for-feedback
type: enhancement
amishra-u
- 9
- Opened 6 days ago
- #4418
Nested tests are failing with new milestone version (5.13.0-M1), when running with Java 17.
Output from gradle build:
2025-03-22T17:04:12.060+0100 [DEBUG] [TestEventLogger] org.junit.platform.commons.PreconditionViolationException: ...
component: Jupiter
theme: extensions
theme: parameterized tests
type: regression
BlueIce
- 3
- Opened 6 days ago
- #4417
Introduction
Currently, there is no way to run specific setup code before each nested class.
I like to write my tests using nested classes combined with @DisplayName in order to have a clear test structure, ...
component: Jupiter
status: declined
theme: programming model
type: new feature
Luktronic
- 7
- Opened 9 days ago
- #4410
!-- Please provide us the version of JUnit 5 you are using and, if possible, a failing unit test with your bug report.
Don t forget to describe the rationale for this issue (e.g. expected vs. actual behavior). ...
3rd-party: Maven Surefire
status: invalid
type: question
paolopiccinini
- 3
- Opened 10 days ago
- #4404
We should add testRuntimeOnly org.junit.platform:junit-platform-launcher to the classpath See
https://github.com/junit-team/junit5/issues/4335
status: invalid
rwinch
- 2
- Opened 11 days ago
- #4395
Currently, JUnit 5 requires tests to specify a DisplayNameGenerator either:
- Globally via the junit.jupiter.displayname.generator system property.
- On a per-class basis using @DisplayNameGeneration(SomeGenerator.class). ...
component: Jupiter
status: declined
theme: extensions
theme: reporting
type: enhancement
sljinlet
- 5
- Opened 12 days ago
- #4391
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Restrict your search to the title by using the in:title qualifier.Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip!
Press the /
key to activate the search input again and adjust your query.