spockframework / spockframework/spock
Support @Exclude of specs
Open
Nobody has claimed this yet.
Module-Core
Type-NewFeature
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 483
- PR merge metrics
- No merged PRs in 30d
Description
Originally reported on Google Code with ID 236
An @Excluded spec shouldn't have a @RunWith annotation so that it won't normally be
run. EmbeddedSpecRunner should compensate for that with a Request that returns Sputnik.
This should allow to write most embedded specs as regular classes instead of strings.
Reported by pniederw on 2012-02-26 22:10:23
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 reading EmbeddedSpecRunner and the @Exclude/@RunWith behavior described in the issue. Confirm how excluded embedded specs are discovered and what Request should return; done means excluded specs no longer carry @RunWith while normal embedded specs still run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100