[ 
http://jira.codehaus.org/browse/JBEHAVE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Elizabeth Keogh closed JBEHAVE-78.
----------------------------------

    Resolution: Fixed

We can mock classes.

> We should be able to mock classes.
> ----------------------------------
>
>                 Key: JBEHAVE-78
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-78
>             Project: JBehave
>          Issue Type: New Feature
>            Reporter: Elizabeth Keogh
>         Assigned To: Elizabeth Keogh
>             Fix For: 1.0
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to