[jira] Commented: (JMOCK-222) An ability to use annotation to create mock objects

    [ http://jira.codehaus.org/browse/JMOCK-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174589#action_174589 ]

Nat Pryce commented on JMOCK-222:
---------------------------------

I like this suggestion.  Code that creates named mock objects is repetitive and this could solve that.  I've run the idea past a few people and they all like it.

My one reservation is that test setup is no longer explicit.  I think implementing this as a subclass of the JMock test-runner is a good idea, maybe named JMockMagic or something similar to warn the reader that magic set-up is happening.

Unused variable warnings can be avoided by making the variables package-protected.  I usually don't bother to make fields private in test classes anyway.  I do like them to be final, but there may be some reflection workaround for that.

The code submitted is not acceptable as it stands. It will fail if there are two mock objects of the same type, for example, does not  name the mock objects after the field names, and is written to an old version of JUnit 4.  

However, we'll implement something like this in a forthcoming JMock version.



--
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