Skip to content

issues Search Results · repo:junit-team/junit-framework language:Java

Filter by

2k results
 (90 ms)

2k results

injunit-team/junit-framework (press backspace or delete to remove)

Reading the error message in #4801 made me realize that we should actually log/report canonical type names instead of binary type names. org.junit.jupiter.api.extension.ParameterResolutionException: Error ...
component: Jupiter
status: new
theme: diagnostics
type: enhancement
  • sbrannen
  • Opened 
    17 hours ago
  • #4806

Overview Now that we cache {arguments} patterns globally (see #4804), we should revisit the need for and/or implementation of CachingByArgumentsLengthPartialFormatter in ParameterizedInvocationNameFormatter. ...
component: Jupiter
theme: parameterized tests
type: task
  • sbrannen
  • 1
  • Opened 
    18 hours ago
  • #4805

Overview Currently, {arguments} patterns are generated for every @ParameterizedTest and @ParameterizedClass, which results in generation of the same pattern strings potentially hundreds of times per test ...
component: Jupiter
theme: parameterized tests
type: enhancement
  • sbrannen
  • Opened 
    19 hours ago
  • #4804

Currently, EmptyArgumentsProvider directly checks the type of the first declared parameter and does not know of potential converters declared for that parameter, so it will throw a PreconditionViolationException ...
status: new
status: team discussion
theme: parameterized tests
type: bug
  • scordio
  • 1
  • Opened 
    2 days ago
  • #4801

!-- Please describe what needs to be done to consider this task completed. -- Deliverables - [ ] ...
status: invalid
  • Exhorder1
  • 2
  • Opened 
    5 days ago
  • #4798

With JUnit 4 it was possible to ignore a suite. For example: package io.cucumber.examples.calculator; ... @Ignore @RunWith(Cucumber.class) public class RunCucumberTest { } This allowed people to disable ...
status: new
type: new feature
  • mpkorstanje
  • Opened 
    6 days ago
  • #4797

Version: github/main (e1f503f5) Not sure if this is a documentation issue, or a genuine bug. I implemented some code based on the docs and it didn t work for me, so I went digging. I wanted to be able ...
component: Platform
theme: discovery
theme: documentation
type: enhancement
  • ptomli
  • 6
  • Opened 
    9 days ago
  • #4791

If a test from a superclass is overriden, it does t run. Yes, I saw https://github.com/junit-team/junit-framework/issues/3553 But it still don t run tests. That s very very annoying and unacceptable. ...
component: Jupiter
status: works-as-designed
theme: discovery
type: bug
  • Lars-jnk
  • 9
  • Opened 
    9 days ago
  • #4790

Overview As I mentioned in #4783, name-argument pairs in display names for parameterized classes and tests have different formatting/spacing depending on the use case. When using useHeadersInDisplayName ...
component: Jupiter
theme: parameterized tests
type: enhancement
  • sbrannen
  • Opened 
    10 days ago
  • #4786

Problem The StoreScope enum and ExtensionContext.getStore(StoreScope, Namespace) method introduced in JUnit 5.13 are not documented in the User Guide. This new feature for resource lifecycle management ...
component: Jupiter
component: Platform
theme: documentation
type: enhancement
  • JKomoroski
  • 5
  • Opened 
    10 days ago
  • #4784
Issue origami icon

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 Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

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 Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub