spockframework / spockframework/spock
Extract EmbeddedSpecRunner-related stuff to separate (publishable) module
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 483
- PR merge metrics
- No merged PRs in 30d
Description
Issue description
Occasionally. it is confusing to have junit-platform-testkit provided as an optional spock-core dependency (with its own dependencies). Namely here and here.
Proposed solution
As regular tests with Spock don't need EmbeddedSpecRunner nor junit-platform-testkit it would be good to extract the related stuff (probably also with EmbeddedSpecification) to a separate publishable module (spock-testkit?) to make it used as a dependency for the Spock plugin writers or the people writing more sophisticated tests (which need to reproduce a complete (embedded) Spock life-cycle in Spock tests).
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 locating EmbeddedSpecRunner and EmbeddedSpecification, then trace the junit-platform-testkit dependency and the embedded Spock lifecycle tests that use them. Done means the related functionality is isolated in a separate publishable module and regular spock-core users no longer receive that optional dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100