Skip to content
Open
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Fix indentation
  • Loading branch information
mattwynne committed Jul 13, 2022
commit c241b30506fc0cce4a0009491090c2c92ea32541
23 changes: 11 additions & 12 deletions features/call_nested_wire_step.feature
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
Feature: Call nested wire step

If the user specifies a "nested" step in their Ruby step definitions, the
search for that step definition should include steps defined over the wire.

Expand All @@ -12,14 +11,14 @@ Feature: Call nested wire step
"""
host: localhost
port: 54321

"""
And a file named "features/nested_step.feature" with:
"""
Feature: Nested
Scenario: Nested
Given a step over the wire
Given a ruby step
Given a step over the wire
And a ruby step
"""
And a file named "features/step_definitions/steps.rb" with:
"""
Expand All @@ -28,18 +27,18 @@ Feature: Call nested wire step
end
"""
And there is a wire server running on port 54321 which understands the following protocol:
| request | response |
| ["step_matches",{"name_to_match":"a ruby step"}] | ["success",[]] |
| ["step_matches",{"name_to_match":"a step over the wire"}] | ["success",[{"id":"1", "args":[]}]] |
| ["begin_scenario"] | ["success"] |
| ["invoke",{"id":"1","args":[]}] | ["success"] |
| ["end_scenario"] | ["success"] |
| request | response |
| ["step_matches",{"name_to_match":"a ruby step"}] | ["success",[]] |
| ["step_matches",{"name_to_match":"a step over the wire"}] | ["success",[{"id":"1", "args":[]}]] |
| ["begin_scenario"] | ["success"] |
| ["invoke",{"id":"1","args":[]}] | ["success"] |
| ["end_scenario"] | ["success"] |
When I run `cucumber -f progress`
And it should pass with:
"""
.

1 scenario (1 passed)
1 step (1 passed)

"""