[Improvement] JUnit5 ignores static classes
Open
improvement
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 935
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 315
Description
### What would you like to be improved?
JUnit5 ignores without any warning static methods. While we currently use JUnit4 it's assumed we update to JUnit5 at some Currently startIntegrationTest() is static in AbstractIT and sub-classes.
### How should we improve?
Change to be non-static.
Contributor guide
Research direction
Start by locating startIntegrationTest() in AbstractIT and its subclasses, then inspect how the JUnit4-to-JUnit5 migration affects those methods. Change the methods to be non-static and verify that JUnit5 no longer ignores them by running the relevant integration tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100