Sha256: 92f123a237f8f93b4e8ada348904236a08494d9411498fc0496293ce35e6907f
Contents?: true
Size: 1.55 KB
Versions: 3
Compression:
Stored size: 1.55 KB
Contents
Feature: implicit docstrings As an RSpec user I want examples to generate their own names So that I can reduce duplication between example names and example code Scenario: run passing examples with ruby Given the file ../../examples/passing/implicit_docstrings_example.rb When I run it with the ruby interpreter -fs And the stdout should match /should be < 5/ And the stdout should match /should include "a"/ And the stdout should match /should respond to #size/ Scenario: run failing examples with ruby Given the file ../../examples/failing/failing_implicit_docstrings_example.rb When I run it with the ruby interpreter -fs Then the stdout should match /should equal 2/ And the stdout should match /should be > 5/ And the stdout should match /should include "b"/ And the stdout should match /should not respond to #size/ Scenario: run passing examples with spec Given the file ../../examples/passing/implicit_docstrings_example.rb When I run it with the spec command -fs And the stdout should match /should be < 5/ And the stdout should match /should include "a"/ And the stdout should match /should respond to #size/ Scenario: run failing examples with spec Given the file ../../examples/failing/failing_implicit_docstrings_example.rb When I run it with the spec command -fs Then the stdout should match /should equal 2/ And the stdout should match /should be > 5/ And the stdout should match /should include "b"/ And the stdout should match /should not respond to #size/
Version data entries
3 entries across 3 versions & 1 rubygems