On 17 Apr 2009, at 18:20, Aslak Hellesøy wrote:
Den 17. april. 2009 kl. 18.58 skrev Zach Dennis
:
On Fri, Apr 17, 2009 at 12:31 PM, Aslak Hellesøy
wrote:
Den 17. april. 2009 kl. 18.06 skrev Matt Wynne :
Is there currently a way to register a block to run after the
current
scenario c
Den 17. april. 2009 kl. 18.58 skrev Zach Dennis :
On Fri, Apr 17, 2009 at 12:31 PM, Aslak Hellesøy
wrote:
Den 17. april. 2009 kl. 18.06 skrev Matt Wynne :
Is there currently a way to register a block to run after the
current
scenario completes?
After.
After is used after *any* scen
On Fri, Apr 17, 2009 at 12:31 PM, Aslak Hellesøy
wrote:
>
>
> Den 17. april. 2009 kl. 18.06 skrev Matt Wynne :
>
>> Is there currently a way to register a block to run after the current
>> scenario completes?
>>
> After.
After is used after *any* scenario completes thought, right? If you
add an A
Matt Wynne wrote:
Is there currently a way to register a block to run after the current
scenario completes?
You could achieve the same thing with After and tags:
http://wiki.github.com/aslakhellesoy/cucumber/hooks
@please-clean-me
Scenario: dirty
...
After "@please-clean-me" do
#clean
On Fri, Apr 17, 2009 at 9:06 AM, Matt Wynne wrote:
>
> If you're interested, our use case is for pagination, where we explicitly
> set the length of a page to something much shorter than the default in a
> step, so that we only have to create a small number of objects to spill over
> onto another
Den 17. april. 2009 kl. 18.06 skrev Matt Wynne :
Is there currently a way to register a block to run after the
current scenario completes?
After.
If not, we've implemented one. Would anyone be interested in us
submitting it as a patch to Cucumber?
How is this different from After?
As
Is there currently a way to register a block to run after the current
scenario completes?
If not, we've implemented one. Would anyone be interested in us
submitting it as a patch to Cucumber?
Something like
Given "something that will not be rolled back after the scenario is
finished" do
