1Story: autogenerated docstrings
2
3 As an RSpec user
4 I want examples to generate their own names
5 So that I can reduce duplication between example names and example code
6
7 Scenario: run passing examples with ruby
8 Given the file ../../examples/pure/autogenerated_docstrings_example.rb
9
10 When I run it with the ruby interpreter -fs
11
12 Then the stdout should match /should equal 5/
13 And the stdout should match /should be < 5/
14 And the stdout should match /should include "a"/
15 And the stdout should match /should respond to #size/
16
17 Scenario: run failing examples with ruby
18 Given the file ../../failing_examples/failing_autogenerated_docstrings_example.rb
19
20 When I run it with the ruby interpreter -fs
21
22 Then the stdout should match /should equal 2/
23 And the stdout should match /should be > 5/
24 And the stdout should match /should include "b"/
25 And the stdout should match /should not respond to #size/
26
27 Scenario: run passing examples with spec
28 Given the file ../../examples/pure/autogenerated_docstrings_example.rb
29
30 When I run it with the spec script -fs
31
32 Then the stdout should match /should equal 5/
33 And the stdout should match /should be < 5/
34 And the stdout should match /should include "a"/
35 And the stdout should match /should respond to #size/
36
37 Scenario: run failing examples with spec
38 Given the file ../../failing_examples/failing_autogenerated_docstrings_example.rb
39
40 When I run it with the spec script -fs
41
42 Then the stdout should match /should equal 2/
43 And the stdout should match /should be > 5/
44 And the stdout should match /should include "b"/
45 And the stdout should match /should not respond to #size/