MicroShed / MicroShed/microshed-testing

Test an application using JUnit 4

Open
#19 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

is:enhancement
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.