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
original = SomeClass.a_value
SomeClass.a_value = 7
AfterCurrentScenario do
# undo stuff
SomeClass.a_value = original
end
end
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 page. The page length value is set
on a class variable, and would pollute other tests, so we want to
reset it when the scenario is finished.
e.g. Given the maximum number of Users to display is 2
And there are 3 Users
When I view the Users page
Then I should see the text “see all 3 users”
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 page.
Is this necessary? I mean, is the page length so long that creating
that many objects takes appreciably longer than otherwise?
I like to leave such values as page length alone in a scenario,
because that’s part of the user requirement (if not a vitally
important one).
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 After block inside of a step definition, it’s going to be
executed from that point on, rather than clear out at the end of the
scenario that ran it, correct?
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?
It clears out after the current scenario.
It doesn’t require to be run for scenarios that don’t need it.
It allows you to cleanly place the handler next to the code that it
is so closely related
It doesn’t require you know the name of the scenario(s) that would
need it (it’s simply determined by if a step definition is run)
After is used after any scenario completes thought, right? If you
add an After block inside of a step definition, it’s going to be
Aha now I understand. Matt, would Joseph’s suggestion work for you?
Aslak
It would work, yes, but I have to say I like ours a bit better - you
can put the undo code right next to the code it’s undoing, as Zach
pointed out. With the tags thing I’d have to put a tag in the feature
file which is introducing a tiny bit more coupling and noise which I’d
rather avoid.
I had pondered on the idea of changing the After method to use a
syntax a bit like RSpec’s #before(:each) where we could say: