Joe Walnes wrote:
Just to clarify - is the scope of assemble() to avoid big constructors
or is there another usecase for it?
That's definitely one of the reasons.
Another is to allow the API to evolve over time without necessarily
breaking people's code when a new dependency is ad
Just to clarify - is the scope of assemble() to avoid big constructors
or is there another usecase for it?
That's definitely one of the reasons.
Another is to allow the API to evolve over time without necessarily breaking
people's code when a new dependency is added to the scenarios. It separ
Dan North wrote:
Hi gang.
Please read this all the way through - it probably affects _you_. :)
I reworked a lot of the scenario stuff over the last few days. Mostly it
comes down to this:
1. A MultiStepScenario is made up of a bunch of Steps, defined in an
assemble() method.
2. A Given, Eve
Hi gang.
Please read this all the way through - it probably affects _you_. :)
I reworked a lot of the scenario stuff over the last few days. Mostly it
comes down to this:
1. A MultiStepScenario is made up of a bunch of Steps, defined in an
assemble() method.
2. A Given, Event or Outcome is c
