search_biomodel 1.0.0 → 1.0.1

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/features/generator/git.feature

@@ -1,102 +0,0 @@
-Feature: git support
-  In order to start a new gem for GitHub
-  A user should be able to
-  generate a project that is setup for git
-
-  Scenario: git remote configuration
-    Given a working directory
-    And I have configured git sanely
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then git repository has 'origin' remote
-    And git repository 'origin' remote should be 'git@github.com:technicalpickles/the-perfect-gem.git'
-
-  Scenario: .gitignore
-    Given a working directory
-    And I have configured git sanely
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then a sane '.gitignore' is created
-
-  Scenario: baseline repository
-    Given a working directory
-    And I have configured git sanely
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then a commit with the message 'Initial commit to the-perfect-gem.' is made
-    And 'README.rdoc' was checked in
-    And 'Rakefile' was checked in
-    And 'LICENSE.txt' was checked in
-    And 'lib/the-perfect-gem.rb' was checked in
-    And '.gitignore' was checked in
-
-    And no files are untracked
-    And no files are changed
-    And no files are added
-    And no files are deleted
-
-  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/spec_helper.rb' was checked in
-    And 'spec/the-perfect-gem_spec.rb' was checked in
-
-  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/helper.rb' was checked in
-    And 'test/test_the-perfect-gem.rb' was checked in
-
-  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/spec_helper.rb' was checked in
-    And 'spec/the-perfect-gem_spec.rb' was checked in
-
-  Scenario: shoulda
-    Given a working directory
-    And I have configured git sanely
-    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'test/helper.rb' was checked in
-    And 'test/test_the-perfect-gem.rb' was checked in
-
-  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/helper.rb' was checked in
-    And 'test/test_the-perfect-gem.rb' was checked in
-
-  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/example_helper.rb' was checked in
-    And 'examples/the-perfect-gem_example.rb' was checked in
-
-  Scenario: cucumber
-    Given a working directory
-    And I have configured git sanely
-    And I want cucumber stories
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'features/the-perfect-gem.feature' was checked in
-    And 'features/support/env.rb' was checked in
-    And 'features/step_definitions/the-perfect-gem_steps.rb' was checked in
-
-  Scenario: shindo
-    Given a working directory
-    And I have configured git sanely
-    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'tests/tests_helper.rb' was checked in
-    And 'tests/the-perfect-gem_tests.rb' was checked in

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/features/generator/license.feature

@@ -1,20 +0,0 @@
-Feature: generated license
-  In order to start a new gem
-  A user should be able to
-  generate a default license
-
-  Background:
-    Given a working directory
-
-  Scenario: crediting user
-    Given I have configured git sanely
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then LICENSE.txt credits 'foo'
-
-  Scenario: copyright in the current year
-    Given it is the year 2005
-    And I have configured git sanely
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then LICENSE.txt has a copyright in the year 2005

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/features/generator/rakefile.feature

@@ -1,158 +0,0 @@
-Feature: generated Rakefile
-  In order to start a new gem
-  A user should be able to
-  generate a Rakefile
-
-  Background:
-    Given a working directory
-    And I have configured git sanely
-
-  Scenario: shared
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good' and described as 'Descriptive'
-
-    Then 'Rakefile' requires 'bundler'
-    And 'Rakefile' sets up bundler using the default and development groups
-    And 'Rakefile' requires 'rubygems'
-    And 'Rakefile' requires 'rake'
-    And 'Rakefile' requires 'rake/rdoctask'
-    And Rakefile has 'the-perfect-gem' for the Jeweler::Tasks name
-    And Rakefile has 'bar@example.com' for the Jeweler::Tasks email
-    And Rakefile has 'zomg, so good' for the Jeweler::Tasks summary
-    And Rakefile has 'Descriptive' for the Jeweler::Tasks description
-    And Rakefile has 'http://github.com/technicalpickles/the-perfect-gem' for the Jeweler::Tasks homepage
-    And Rakefile has 'MIT' for the Jeweler::Tasks license
-    And Rakefile instantiates a Jeweler::RubygemsDotOrgTasks
-    And Rakefile has a magic comment for UTF-8
-
-  Scenario: bacon
-    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'Rakefile' requires 'rcov/rcovtask'
-    And Rakefile has 'spec/**/*_spec.rb' for the Rake::TestTask pattern
-    And Rakefile has 'spec/**/*_spec.rb' for the Rcov::RcovTask pattern
-    And Rakefile has 'spec' in the Rcov::RcovTask libs
-    And Rakefile has "spec" as the default task
-
-  Scenario: minitest
-    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'Rakefile' requires 'rcov/rcovtask'
-    And Rakefile has 'test/**/test_*.rb' for the Rake::TestTask pattern
-    And Rakefile has 'test/**/test_*.rb' for the Rcov::RcovTask pattern
-    And Rakefile has 'test' in the Rcov::RcovTask libs
-    And Rakefile has "test" as the default task
-
-  @rspec
-  Scenario: rspec
-    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'Rakefile' requires 'rspec/core'
-    And 'Rakefile' requires 'rspec/core/rake_task'
-    And Rakefile has 'spec/**/*_spec.rb' for the RSpec::Core::RakeTask pattern
-    And Rakefile has "spec" as the default task
-
-  Scenario: shoulda
-    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'Rakefile' requires 'rcov/rcovtask'
-    And Rakefile has 'test/**/test_*.rb' for the Rake::TestTask pattern
-    And Rakefile has 'test/**/test_*.rb' for the Rcov::RcovTask pattern
-    And Rakefile has 'test' in the Rcov::RcovTask libs
-    And Rakefile has "test" as the default task
-
-  Scenario: micronaut
-    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'Rakefile' requires 'micronaut/rake_task'
-    And Rakefile has 'examples/**/*_example.rb' for the Micronaut::RakeTask pattern
-    And Rakefile has "examples" as the default task
-
-  Scenario: testunit
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'Rakefile' requires 'rcov/rcovtask'
-    Then Rakefile has 'test/**/test_*.rb' for the Rake::TestTask pattern
-    And Rakefile has 'test/**/test_*.rb' for the Rcov::RcovTask pattern
-    And Rakefile has 'test' in the Rcov::RcovTask libs
-    And Rakefile has '--exclude "gems/*"' in the Rcov::RcovTask rcov_opts
-    And Rakefile has "test" as the default task
-
-  Scenario: no cucumber
-    Given I do not want cucumber stories
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then Rakefile does not require 'cucumber/rake/task'
-    And Rakefile does not instantiate a Cucumber::Rake::Task
-
-  Scenario: cucumber
-    Given I want cucumber stories
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then Rakefile requires 'cucumber/rake/task'
-    And Rakefile instantiates a Cucumber::Rake::Task
-
-  Scenario: no reek
-    Given I do not want reek
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then Rakefile does not require 'reek/rake/task'
-    And Rakefile does not instantiate a Reek::Rake::Task
-
-  Scenario: reek
-    Given I want reek
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then Rakefile requires 'reek/rake/task'
-    And Rakefile instantiates a Reek::Rake::Task
-
-  Scenario: no roodi
-    Given I do not want roodi
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then Rakefile does not require 'roodi'
-    And Rakefile does not require 'roodi_task'
-    And Rakefile does not instantiate a RoodiTask
-
-  Scenario: roodi
-    Given I want roodi
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then Rakefile requires 'roodi'
-    And Rakefile requires 'roodi_task'
-    And Rakefile instantiates a RoodiTask
-
-  Scenario: no rubyforge
-    Given I do not want rubyforge setup
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then Rakefile does not instantiate a Jeweler::RubyforgeTasks
-
-  Scenario: yard
-    Given I want to use yard instead of rdoc
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'Rakefile' does not require 'rake/rdoctask'
-    And 'Rakefile' requires 'yard'
-    And Rakefile instantiates a YARD::Rake::YardocTask
-
-  Scenario: rdoc
-    Given I want to use rdoc instead of yard
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'Rakefile' does not require 'yard'
-    And 'Rakefile' requires 'rake/rdoctask'
-    And Rakefile does not instantiate a YARD::Rake::YardocTask
-    And Rakefile instantiates a Rake::RDocTask.new
-
-  Scenario: shindo
-    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
-    And 'Rakefile' requires 'shindo/rake'
-    And Rakefile instantiates a Shindo::Rake.new
-    And Rakefile has "tests" as the default task
-
-
-  Scenario: bundler
-    Given I want bundler
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good' and described as 'Descriptive'
-    Then 'Rakefile' requires 'bundler'
-    And 'Rakefile' sets up bundler using the default and development groups
-    And Rakefile does not add 'jeweler' as a development dependency to Jeweler::Tasks
-
-  Scenario: no bundler
-    Given I do not want bundler
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good' and described as 'Descriptive'
-    Then 'Rakefile' does not require 'bundler'
-    And 'Rakefile' does not setup bundler
-    And Rakefile adds 'jeweler' as a development dependency to Jeweler::Tasks

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/features/generator/readme.feature

@@ -1,12 +0,0 @@
-Feature: generated license
-  In order to start a new gem
-  A user should be able to
-  generate a default license
-
-  Scenario: copyright
-    Given a working directory
-    And I have configured git sanely
-    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
-
-    Then 'README.rdoc' contains '= the-perfect-gem'
-    And 'README.rdoc' mentions copyright belonging to me in the current year

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/features/generator/test.feature

@@ -1,54 +0,0 @@
-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/test_the-perfect-gem.rb' should define 'TestThePerfectGem' as a subclass of 'MiniTest::Unit::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/test_the-perfect-gem.rb' should define 'TestThePerfectGem' 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/test_the-perfect-gem.rb' should define 'TestThePerfectGem' 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'
-
-  Scenario: riot
-    Given a working directory
-      And I have configured git sanely
-    When I generate a riot project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'test/the-perfect-gem_test.rb' should contextualize 'the-perfect-gem'
-      And 'test/the-perfect-gem_test.rb' requires 'teststrap'
-
-  Scenario: shindo
-    Given a working directory
-    And I have configured git sanely
-    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'tests/the-perfect-gem_tests.rb' should have tests for 'ThePerfectGem'

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/features/generator/test_helper.feature

@@ -1,149 +0,0 @@
-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 w/ bundler
-    Given a working directory
-    And I have configured git sanely
-    And I want bundler
-    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'spec/spec_helper.rb' requires 'bundler'
-    And 'spec/spec_helper.rb' sets up bundler using the default and development groups
-    And 'spec/spec_helper.rb' requires 'bacon'
-    And 'spec/spec_helper.rb' requires 'the-perfect-gem'
-
-  Scenario: bacon w/o bundler
-    Given a working directory
-    And I have configured git sanely
-    And I do not want bundler
-    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'spec/spec_helper.rb' does not require 'bundler'
-    And 'spec/spec_helper.rb' does not setup bundler
-
-  Scenario: minitest w/ bundler
-    Given a working directory
-    And I have configured git sanely
-    And I want bundler
-    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'test/helper.rb' requires 'bundler'
-    And 'test/helper.rb' sets up bundler using the default and development groups
-    And 'test/helper.rb' requires 'minitest/unit'
-    And 'test/helper.rb' requires 'the-perfect-gem'
-    And 'test/helper.rb' should autorun tests
-
-  Scenario: minitest w/o bundler
-    Given a working directory
-    And I have configured git sanely
-    And I do not want bundler
-    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'test/helper.rb' does not require 'bundler'
-    And 'test/helper.rb' does not setup bundler
-
-  Scenario: rspec w/ bundler
-    Given a working directory
-    And I have configured git sanely
-    And I want bundler
-    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'spec/spec_helper.rb' requires 'rspec'
-    And 'spec/spec_helper.rb' requires 'the-perfect-gem'
-
-  Scenario: rspec w/o bundler
-    Given a working directory
-    And I have configured git sanely
-    And I do not want bundler
-    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'spec/spec_helper.rb' does not require 'bundler'
-    And 'spec/spec_helper.rb' does not setup bundler
-
-  Scenario: shoulda w/ bundler
-    Given a working directory
-    And I have configured git sanely
-    And I want bundler
-    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'test/helper.rb' requires 'bundler'
-    And 'test/helper.rb' sets up bundler using the default and development groups
-    And 'test/helper.rb' requires 'test/unit'
-    And 'test/helper.rb' requires 'shoulda'
-    And 'test/helper.rb' requires 'the-perfect-gem'
-
-  Scenario: shoulda w/o bundler
-    Given a working directory
-    And I have configured git sanely
-    And I do not want bundler
-    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
-    And 'test/helper.rb' does not require 'bundler'
-    And 'test/helper.rb' does not setup bundler
-
-  Scenario: testunit w/ bundler
-    Given a working directory
-    And I have configured git sanely
-    And I want bundler
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'test/helper.rb' requires 'test/unit'
-    And 'test/helper.rb' requires 'the-perfect-gem'
-    And 'test/helper.rb' requires 'bundler'
-    And 'test/helper.rb' sets up bundler using the default and development groups
-
-  Scenario: testunit w/o bundler
-    Given a working directory
-    And I have configured git sanely
-    And I do not want bundler
-    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
-    And 'test/helper.rb' does not require 'bundler'
-    And 'test/helper.rb' does not setup bundler
-
-  Scenario: micronaut w/ bundler
-    Given a working directory
-    And I have configured git sanely
-    And I want bundler
-    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'examples/example_helper.rb' requires 'rubygems'
-    Then 'examples/example_helper.rb' requires 'micronaut'
-    Then 'examples/example_helper.rb' requires 'the-perfect-gem'
-    And 'examples/example_helper.rb' requires 'bundler'
-    And 'examples/example_helper.rb' sets up bundler using the default and development groups
-
-  Scenario: micronaut w/o bundler
-    Given a working directory
-    And I have configured git sanely
-    And I do not want bundler
-    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
-    And 'examples/example_helper.rb' does not require 'bundler'
-    And 'examples/example_helper.rb' does not setup bundler
-
-  Scenario: riot w/ bundler
-    Given a working directory
-      And I have configured git sanely
-      And I want bundler
-    When I generate a riot project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'test/teststrap.rb' requires 'riot'
-      And 'test/teststrap.rb' requires 'the-perfect-gem'
-      And 'test/teststrap.rb' requires 'bundler'
-      And 'test/teststrap.rb' sets up bundler using the default and development groups
-
-  Scenario: riot w/o bundler
-    Given a working directory
-      And I have configured git sanely
-      And I do not want bundler
-    When I generate a riot project named 'the-perfect-gem' that is 'zomg, so good'
-      And 'test/teststrap.rb' does not require 'bundler'
-      And 'test/teststrap.rb' does not setup bundler
-
-  Scenario: shindo w/ bundler
-    Given a working directory
-    And I have configured git sanely
-    And I want bundler
-    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'tests/tests_helper.rb' requires 'the-perfect-gem'
-    Then 'tests/tests_helper.rb' requires 'shindo'
-    Then 'tests/tests_helper.rb' requires 'bundler'
-    And 'tests/tests_helper.rb' sets up bundler using the default and development groups
-
-  Scenario: shindo w/o bundler
-    Given a working directory
-    And I have configured git sanely
-    And I do not want bundler
-    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
-    Then 'tests/tests_helper.rb' does not require 'bundler'
-    And 'tests/tests_helper.rb' does not setup bundler

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/features/placeholder.feature

@@ -1,5 +0,0 @@
-Feature: I am a placeholder
-
-    Scenario: I am also a placeholder
-      Given a working directory
-

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/features/step_definitions/debug_steps.rb

@@ -1,6 +0,0 @@
-Then /^I debug$/ do
-  require 'ruby-debug'
-  breakpoint
-  0
-end
-

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/features/step_definitions/filesystem_steps.rb

@@ -1,70 +0,0 @@
-Given 'a working directory' do
-  @working_dir = create_construct
-end
-
-After do
-  @working_dir.destroy! if @working_dir
-end
-
-Given /^I use the jeweler command to generate the "([^"]+)" project in the working directory$/ do |name|
-  @name = name
-
-  return_to = Dir.pwd
-  path_to_jeweler = File.expand_path File.join(File.dirname(__FILE__), '..', '..', 'bin', 'jeweler')
-
-  begin
-    FileUtils.cd @working_dir
-    @stdout = `#{path_to_jeweler} #{@name}`
-  ensure
-    FileUtils.cd return_to
-  end
-end
-
-Given /^"([^"]+)" does not exist$/ do |file|
-  assert ! File.exists?(File.join(@working_dir, file))
-end
-
-When /^I run "([^"]+)" in "([^"]+)"$/ do |command, directory|
-  full_path = File.join(@working_dir, directory)
-
-  lib_path = File.expand_path 'lib'
-  command.gsub!(/^rake /, "rake --trace -I#{lib_path} ")
-
-  assert File.directory?(full_path), "#{full_path} is not a directory"
-
-  @stdout = `cd #{full_path} && #{command}`
-  @exited_cleanly = $?.exited?
-end
-
-Then /^the updated version, (.*), is displayed$/ do |version|
-  assert_match "Updated version: #{version}", @stdout
-end
-
-Then /^the current version, (\d+\.\d+\.\d+), is displayed$/ do |version|
-  assert_match "Current version: #{version}", @stdout
-end
-
-Then /^the process should exit cleanly$/ do
-  assert @exited_cleanly, "Process did not exit cleanly: #{@stdout}"
-end
-
-Then /^the process should not exit cleanly$/ do
-  assert !@exited_cleanly, "Process did exit cleanly: #{@stdout}"
-end
-
-Given /^I use the existing project "([^"]+)" as a template$/ do |fixture_project|
-  @name = fixture_project
-  FileUtils.cp_r File.join(fixture_dir, fixture_project), @working_dir
-end
-
-Given /^"VERSION\.yml" contains hash "([^"]+)"$/ do |ruby_string|
-  version_hash = YAML.load(File.read(File.join(@working_dir, @name, 'VERSION.yml')))
-  evaled_hash = eval(ruby_string)
-  assert_equal evaled_hash, version_hash
-end
-
-Given /^"VERSION" contains "([^\"]*)"$/ do |expected|
-  version = File.read(File.join(@working_dir, @name, 'VERSION')).chomp
-  assert_equal expected, version
-end
-