Sha256: dfb3f4ad814081d780d48689dce0816b8b0e51dcbeeb60a10024355be5e16d40
Contents?: true
Size: 1.54 KB
Versions: 3
Compression:
Stored size: 1.54 KB
Contents
Feature: RubyGems have features to be described and tested As a RubyGem developer I want to describe the project's features using Cucumber So that I can describe each feature of the project in readable text Scenario: Install Cucumber into a RubyGem Given an existing newgem scaffold [called 'my_project'] When 'install_cucumber' generator is invoked with arguments '' Then folder 'features/steps' is created And file 'features/development.feature' is created And file 'features/steps/common.rb' is created And file 'tasks/cucumber.rake' is not created as it is loaded via newgem itself Scenario: NewGem and generated gems should share some common files Given an existing newgem scaffold [called 'my_project'] When 'install_cucumber' generator is invoked with arguments '' Then gem file 'features/steps/common.rb' and generated file 'features/steps/common.rb' should be the same Then gem file 'features/development.feature' and generated file 'features/development.feature' should be the same Scenario: Installed Cucumber includes a 'rake features' task Given an existing newgem scaffold [called 'my_project'] And 'install_cucumber' generator is invoked with arguments '' When task 'rake features' is invoked Then task 'rake features' is executed successfully And output does match /Feature: Development processes of newgem itself \(rake tasks\)/ And output does match /And file matching 'pkg/\*\.gem' is created/ And output does not match /You can use these snippets to implement pending steps/
Version data entries
3 entries across 3 versions & 1 rubygems
Version | Path |
---|---|
newgem-1.0.4 | features/install_cucumber.feature |
newgem-1.0.5 | features/install_cucumber.feature |
newgem-1.0.6 | features/install_cucumber.feature |