Sha256: 5d8f3e929d770283b02256ba3dc0513be985991ba3fecaf0772b3adbb2f427df
Contents?: true
Size: 1.71 KB
Versions: 19
Compression:
Stored size: 1.71 KB
Contents
Feature: generated test or spec In order to start a new gem A user should be able to generate a test or spec Scenario: bacon Given a working directory And I have configured git sanely When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good' Then 'spec/the-perfect-gem_spec.rb' should describe 'ThePerfectGem' Scenario: minitest Given a working directory And I have configured git sanely When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good' Then 'test/the-perfect-gem_test.rb' should define 'ThePerfectGemTest' as a subclass of 'Mini::Test::TestCase' Scenario: rspec Given a working directory And I have configured git sanely When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good' Then 'spec/the-perfect-gem_spec.rb' should describe 'ThePerfectGem' Scenario: shoulda Given a working directory And I have configured git sanely And I intend to test with shoulda When I generate a project named 'the-perfect-gem' that is 'zomg, so good' Then 'test/the-perfect-gem_test.rb' should define 'ThePerfectGemTest' as a subclass of 'Test::Unit::TestCase' Scenario: testunit Given a working directory And I have configured git sanely When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good' Then 'test/the-perfect-gem_test.rb' should define 'ThePerfectGemTest' as a subclass of 'Test::Unit::TestCase' Scenario: micronaut Given a working directory And I have configured git sanely When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good' Then 'examples/the-perfect-gem_example.rb' should describe 'ThePerfectGem'
Version data entries
19 entries across 19 versions & 8 rubygems