spockframework / spockframework/spock
Add assertion error to reports for @PendingFeature
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 483
- PR merge metrics
- No merged PRs in 30d
Description
Issue description
Test methods marked with @PendingFeature run and they are expected to fail. If they not fail they are marked as failures. In the reports those test methods are marked as "skipped" with a small notification "Pending Feature".
That is okay.
Is it however possible to additionally add the assertion error to the reports and still mark them as "skipped" and "Pending Feature"? As well as the reason from the annotation?
The assertion error is available as the test method run.
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
Trace how @PendingFeature test results are classified and rendered in reports. Check where the assertion error from the test run and the annotation reason are available, then verify that completed reports retain the skipped and Pending Feature labels while also showing both details.
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
- 35/100