spockframework / spockframework/spock
Polling condition failure report.
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 350
Describe the enhancement you have in mind.
When I have a condition inside a condition.eventually and if the condition fails the
failure report is not helpful like in regular test.
The report should say what was actual value and what it was meaning to receive.
Which particular problem would this enhancement solve for you?
It will help to debug the issue with the test faster.
Reported by ritesh1869 on 2014-02-21 16:47:25
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 the implementation of condition.eventually and the existing failure-reporting tests for regular conditions. Compare how polling failures are reported with regular test failures. The work is done when a failed condition inside condition.eventually reports both the actual value and the expected value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy, java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100