spockframework / spockframework/spock
Better stack traces for unsatisfied interactions
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 18
Too few invocations: Completely synthetic stack trace(s) that point(s) to all affected
interactions
Too many invocations: Truncate after call to matching method, replace name of proxy
class (e.g.
$Proxy9)
Reported by pniederw on 2009-04-03 04:53: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
No source files, tests, or entry points are named in the issue. Start by locating the interaction-failure reporting path, then compare the requested too-few and too-many invocation cases; the work is done when those failures produce focused traces and avoid opaque proxy-class names.
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