MicroShed / MicroShed/microshed-testing
Test an application using JUnit 4
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 68
- Forks
- 25
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 6
Description
## User story:
As a user of this test framework, I want to test my application using JUnit 4 because I already have significant investment in JUnit 4 and do not wish to migrate to JUnit Jupiter.
## Additional detail:
JUnit Jupiter is the newest version of JUnit and has a good amount of adoption. From a test framework implementor perspective, Jupiter is far more flexible and powerful than previous versions of JUnit. By default, we will use Jupiter in implementation and examples, but it should also be possible for users to use JUnit 4 (although it may be a bit clunkier).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining how the framework currently uses JUnit Jupiter in its implementation and examples, then identify the entry points involved in running user tests. Define the compatibility approach for applications that remain on JUnit 4, and verify that a JUnit 4 application can be tested without migrating to JUnit Jupiter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100