[#JBEHAVE-265] Allow annotation-based configuration - jira.codehaus.org

Details

Type: New Feature
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 3.0
Component/s: Core
Labels:
None

Number of attachments :
0

Description

Annotations-based configuration can be preferable to some users.

Investigate and implement annotation-based alternatives to programmatic configuration, which should always be possible.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Cristiano Gavião added a comment - 05/Apr/10 1:35 PM

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.

@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);
	}
}

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?

Show

Cristiano Gavião added a comment - 05/Apr/10 1:35 PM 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.

@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);
	}
}

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?

Hide

Permalink

Mauro Talevi added a comment - 06/Apr/10 5:47 PM

The issue I see in approach 1 is the tie-in with JUnitRunner, which works fine in IDE but we'd need to change the command-line runner. This may not be a bad thing, we may decide to leverage the JUnit runner for command-line too.

I think it's important to have configuration mechanism that are valid in IDE as well as command-line.

Show

Mauro Talevi added a comment - 06/Apr/10 5:47 PM The issue I see in approach 1 is the tie-in with JUnitRunner, which works fine in IDE but we'd need to change the command-line runner. This may not be a bad thing, we may decide to leverage the JUnit runner for command-line too. I think it's important to have configuration mechanism that are valid in IDE as well as command-line.

JBehave

Allow annotation-based configuration

Details

Description

Activity

People

Dates