Hi Simon,
you can always provide your own impl of InjectableStepsFactory. The
main method returns the instances of the CandidateSteps classes, which
you can instantiate in the order you need.
Cheers
On 22/12/2011 18:41, Simon Kent wrote:
We are currently using JBehave 3.4.3 and considering an upgrade to
3.5.4. However one of the improvements (JBEHAVE-534) adds lazy loading
of steps classes, which makes the order of loading less deterministic.
This becomes an issue when we use generic steps classes with
@BeforeStories annotations which we'd like to assume are actioned up
front (and hence currently defined earlier in the list of steps
classes). Can you recommend any way around this?
e.g. with a list of steps : myGenericSteps, myStorySteps
with 3.4.3 these were executed in this order
with 3.5.4 they reverse
myGenericSteps :
@BeforeStories
public void before1() {
// want to execute this first
}
myStorySteps:
@BeforeStories
public void before2() {
// want to execute this second
}
@Given
..
@Then
..
etc
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
