JBehave

Error reporting in minimock could be better.

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Core
  • Labels:
    None
  • Number of attachments :
    0

Description

The error reporting in minimock gives no clue as to what expectations have been set up, and what arguments it's getting.

This makes it really hard to work out whether it's the code or the behaviour that's misbehaving.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Elizabeth Keogh added a comment -

I've added some info to tell me what was expected, and what I'm getting, when a method's expected but the arguments are wrong.

Doesn't say what's already been invoked yet, and I think there are other places which still throw VerificationException with minimal mesage.

Show
Elizabeth Keogh added a comment - I've added some info to tell me what was expected, and what I'm getting, when a method's expected but the arguments are wrong. Doesn't say what's already been invoked yet, and I think there are other places which still throw VerificationException with minimal mesage.
Hide
Permalink
Elizabeth Keogh added a comment -

No minimock in 2.0 - use Mockito instead

Show
Elizabeth Keogh added a comment - No minimock in 2.0 - use Mockito instead

People

  • Assignee:
    Elizabeth Keogh
    Reporter:
    Elizabeth Keogh
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: