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
--
Simon Kent
QA Engineer
Gresham Computing PLC
e: [email protected]
Privileged or confidential information may be contained in this message. If you are not the addressee of this message please notify the sender by return and thereafter delete the message, and you may not use, copy, disclose or rely on the information contained in it. Internet e-mail may be susceptible to data corruption, interception and unauthorised amendment for which Gresham does not accept liability. Whilst we have taken reasonable precautions to ensure that this e-mail and any attachments have been swept for viruses, Gresham does not accept liability for any damage sustained as a result of viruses. Statements in this message that do not relate to the business of Gresham are neither given nor endorsed by the company or its directors. Gresham Computing plc Registered in England and Wales. Company No. 01072032 Registered Office: Sopwith House, Brook Avenue, Warsash, Southampton. Hants. SO31 9ZA Further information about Gresham Computing can be found on our website: www.gresham-computing.com
