Details
-
Type: New Feature
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.0
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Currently JBehave throws an error if an attempt to mock a class, rather than an interface, is made.
The ability to mock classes means that users don't have to create interfaces artificially. In many instances, where a default implementation of a class exists (eg: repositories, file handlers, etc.) there will only ever be one implementation outside of the behaviours.
Activity
Elizabeth Keogh
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Elizabeth Keogh [ sirenian ] |
Elizabeth Keogh
made changes -
Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] |
We can mock classes.