Elizabeth Keogh wrote:
Hi all,
I've just checked in the @BeforeScenario and @AfterScenario stuff.
This enables you to run miscellaneous "admin" tasks before and after
any scenario. I recommend putting them in seperate Steps classes, so
that they're easy to inject into any scenario which needs them.
We suggest that Givens should still be used for setting up the context
of scenarios. These steps are intended for things like initializing
any test framework, setting up a production-like environment,
providing logging info, etc.. I'm using them to close down all the
windows in my Noughts and Crosses game.
Had a look at this - very nice work Liz! :-)
I don't want to mark this as "fixed" yet because our Ant build is
broken following the PicoContainer and Spring work. Dan and I are
about to Ivy the build anyway, which will help us resolve these
dependencies. Everything else is working.
Ant build fixed - Spring test was requiring commons-logging dependency.
Goes to show yet again how useful moving to Ivy to provide transitive
dependency management for Ant would be :-)
Until then - I've also replaced junit jar with junit-dep jar now that we
moved to specify hamcrest as an unbundled dependency. Keeping hamcrest
bundled and unbundled could lead to unexpected classloader behaviour
dependending on order in the classpath.
Cheers
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
