spockframework / spockframework/spock
@Stepwise specs shouldn't be reordered even if optimizeRunOrder is set to true
Open
Nobody has claimed this yet.
Module-Core
Type-Enhancement
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 483
- PR merge metrics
- No merged PRs in 30d
Description
Originally reported on Google Code with ID 157
Should provide a new property on SpecInfo that tells if a spec needs to be run sequentially.
This property should be set by StepWiseExtension and read by OptimizeRunOrdeExtension.
Need to be careful about ordering issues (can the former run after the latter?).
Reported by pniederw on 2010-12-11 16:03:00
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 SpecInfo, StepWiseExtension, and OptimizeRunOrdeExtension to understand how spec ordering is currently represented and changed. Trace the ordering interaction between Stepwise specs and optimizeRunOrder, including which extension should run first. Done means Stepwise specs retain their required sequential order when optimization is enabled, with the ordering cases covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100