[
http://jira.codehaus.org/browse/JBEHAVE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216754#action_216754
]
Cristiano Gavião commented on JBEHAVE-265:
------------------------------------------
Hi,
I think the first thing that needed to be decided is: *where* will be started
the annotation interpretation process?
I could think in two alternatives:
# To use the junit native way and create a class extending from
BlockJUnit4ClassRunner. This way each jbehave class should have a @RunWith to
indicate that we wanted to use the annotated mode.
{code}
@StepsSettings(classes={StepsTestClass.class}, monitor="")
@JBehaveSettings(type = BehaviorType.USER_STORY, logLevel = LogLevel.DEBUG)
@RunWith(TestRunner4JBehave.class)
Class Cenario1 extends Scenario {
@Inject
public Cenario2(StoryConfiguration pConfiguration,
Set<CandidateSteps> pCandidateSteps) throws Exception {
super(pConfiguration, pCandidateSteps);
}
}
{code}
# To use some jbehave initialization method to call the annotation
interpretation inside it.
Particularly I prefer the first one, so I can use annotations with DI to
configure all my jbehave session.
More ideas?
> Allow annotation-based configuration
> ------------------------------------
>
> Key: JBEHAVE-265
> URL: http://jira.codehaus.org/browse/JBEHAVE-265
> Project: JBehave
> Issue Type: New Feature
> Components: Core
> Reporter: Mauro Talevi
> Fix For: 3.0
>
>
> Annotations-based configuration can be preferable to some users.
> Investigate and implement annotation-based alternatives to programmatic
> configuration, which should always be possible.
--
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
