spockframework / spockframework/spock
Test Dashboard
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 483
- PR merge metrics
- No merged PRs in 30d
Description
Flaky tests (last 30 days)
Includes the default branch and all protected branches with recent commits or pull requests
🟡 Branch master (default)
Branch and pull request builds (includes only tests with flaky results)
:spock-specs:test (11)
| Test | Failures | Flakiness |
|---|---|---|
| TimeoutExtension > method that doesn't complete in time | 0/631 (0%) | 5/631 (1%) 🟡 |
| IsolatedUseSpec > executing iterations in parallel works with annotated feature | 0/629 (0%) | 3/629 (1%) 🟡 |
| PollingConditionsSpec > succeeds if all conditions are eventually satisfied with condition method '#conditionMethod' and local variable > succeeds if all conditions are eventually satisfied with condition method '.call' and local variable | 0/316 (0%) | 1/316 (1%) 🟡 |
| PollingConditionsSpec > succeeds if all conditions are eventually satisfied with condition method '#conditionMethod' and field > succeeds if all conditions are eventually satisfied with condition method '.call' and field | 0/635 (0%) | 2/635 (1%) 🟡 |
| ParallelSpec > @ResourceLock with only READ allows parallel execution of data-driven features | 0/647 (0%) | 2/647 (1%) 🟡 |
| GlobalTimeoutExtension > can be overwritten by class-level annotation | 0/627 (0%) | 1/627 (1%) 🟡 |
| GlobalTimeoutExtension > can be overwritten by feature annotation | 0/627 (0%) | 1/627 (1%) 🟡 |
| TimeoutExtension > method that completes in time (millis) | 0/627 (0%) | 1/627 (1%) 🟡 |
| AsyncConditionsSpec > multiple passing evals | 0/635 (0%) | 1/635 (1%) 🟡 |
| AsyncConditionsSpec > passing example - check passes | 0/635 (0%) | 1/635 (1%) 🟡 |
| BlockingVariablesSpec > variable may be null | 0/635 (0%) | 1/635 (1%) 🟡 |
Branch builds (includes tests with flaky or failed results)
:tada: No flaky tests detected!
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 with the listed :spock-specs:test entries, especially TimeoutExtension and IsolatedUseSpec, and run the corresponding test suite to reproduce the reported flaky results. The issue does not specify a requested change or completion criterion, so the scope would need clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100