Sha256: f4df250f0f2d17ff110ffab2d14b32e9354c0b21b0aced73adc311ce664f1a5d
Contents?: true
Size: 1.47 KB
Versions: 8
Compression:
Stored size: 1.47 KB
Contents
Feature: After Hooks
After hooks can be used to clean up any state you've altered during your
scenario, or to check the status of the scenario and act accordingly.
You can ask a scenario whether it has failed, for example.
Mind you, even if it hasn't failed yet, you can still make the scenario
fail if your After hook throws an error.
Background:
Given the standard step definitions
Scenario: Check the failed status of a scenario in a hook
Given a file named "features/support/debug_hook.rb" with:
"""
After do |scenario|
if scenario.failed?
puts "eek"
end
end
"""
And a file named "features/fail.feature" with:
"""
Feature:
Scenario:
Given this step fails
"""
When I run `cucumber -f progress`
Then the output should contain:
"""
eek
"""
Scenario: Make a scenario fail from an After hook
Given a file named "features/support/bad_hook.rb" with:
"""
After do
fail 'yikes'
end
"""
And a file named "features/pass.feature" with:
"""
Feature:
Scenario:
Given this step passes
"""
When I run `cucumber -f pretty`
Then it should fail with:
"""
Scenario: # features/pass.feature:2
Given this step passes # features/step_definitions/steps.rb:1
yikes (RuntimeError)
./features/support/bad_hook.rb:2:in `After'
"""
Version data entries
8 entries across 8 versions & 1 rubygems