[
http://jira.codehaus.org/browse/JBEHAVE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elizabeth Keogh closed JBEHAVE-52.
----------------------------------
Resolution: Fixed
Extending JUnit which supports this already as part of 2.0
> Have a way to register a setup and a teardown that will be invoked before and
> after EACH method
> -----------------------------------------------------------------------------------------------
>
> Key: JBEHAVE-52
> URL: http://jira.codehaus.org/browse/JBEHAVE-52
> Project: JBehave
> Issue Type: New Feature
> Components: Core
> Reporter: Shane Duan
>
> You probably would not need this in an ideal enviornment. But in the case
> where you want to make sure that everyone on the team is cleaning up after
> themselves (deleting the test data from database, cleaning up the files,
> etc), it is something that can save days of work.
> An enhanced version would be to allow dependency injection into each
> behaviour class so that it won't have to use singleton on certain case (like
> database connection).
> Yes I konw you are not supposed to do database connection tests, but in order
> to fix the existing tests a feature like this would come in very handy.
--
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
