spockframework / spockframework/spock
Extend exception hierarchy below SpockAssertionError, InvalidSpeckException, and SpeckExecutionException
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 32
Exception subclasses should reveal information beyond just the error message.
Reported by pniederw on 2009-06-28 21:42:41
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 SpockAssertionError, InvalidSpeckException, and SpeckExecutionException in the repository and reviewing their current hierarchy and uses. Clarify which error-specific information each exception should expose beyond its message, then verify that the resulting hierarchy preserves the intended behavior across the affected testing framework paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100