[
http://jira.codehaus.org/browse/JBEHAVE-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209596#action_209596
]
David Ron commented on JBEHAVE-133:
-----------------------------------
I created a pretty nice way to break the JBehave Inheritance Hierarchy that
isn't framework specific. Instead of inheriting from Scenario, it allows you
to delegate to a class that does so. If something like this were integrated
directly into JBehave, then framework-specific code would be minimal:
http://blog.davidron.com/2009/12/breaking-jbehave-inheritance-hierarchy.html
My company uses this code to run Jbehave tests inside of a standard spring
container. It works with both annotation-driven spring classes and with test
classes that extend AbstractTransactionalSpringContextTests.
It also supports finding the steps configuration file by name (string) or class
name.
> Allow Steps dependencies to be composable via PicoContainer
> -----------------------------------------------------------
>
> Key: JBEHAVE-133
> URL: http://jira.codehaus.org/browse/JBEHAVE-133
> Project: JBehave
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.4
> Reporter: Mauro Talevi
> Assignee: Mauro Talevi
> Fix For: 2.5
>
>
> In acceptance/integration tests is often common to have a lightweight
> container (Pico, Spring, Guice, etc ...) to configure the tests with.
> A container-supported Steps instance should be composable (either via
> constructor or setter dependency injection) with components configured in the
> container.
> Each container support will be contained in a separate optional module.
> We start with Pico support, with other containers to follow.
--
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
