search_biomodel 0.1.2 → 1.0.0

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/Rakefile

@@ -0,0 +1,81 @@
+# encoding: utf-8
+
+require 'rubygems'
+require 'bundler'
+
+begin
+  Bundler.setup(:default, :development)
+rescue Bundler::BundlerError => e
+  $stderr.puts e.message
+  $stderr.puts "Run `bundle install` to install missing gems"
+  exit e.status_code
+end
+
+$LOAD_PATH.unshift('lib')
+
+require 'rake'
+require 'jeweler'
+
+Jeweler::Tasks.new do |gem|
+  gem.name = "jeweler"
+  gem.version = Jeweler::Version::STRING
+  gem.homepage = "http://github.com/technicalpickles/jeweler"
+  gem.summary = "Opinionated tool for creating and managing RubyGem projects"
+  gem.description = "Simple and opinionated helper for creating Rubygem projects on GitHub"
+  gem.license = "MIT"
+  gem.authors = ["Josh Nichols"]
+  gem.email = "josh@technicalpickles.com"
+  gem.files.include %w(lib/jeweler/templates/.document lib/jeweler/templates/.gitignore)
+
+  # dependencies defined in Gemfile
+end
+
+Jeweler::RubygemsDotOrgTasks.new
+
+require 'rake/testtask'
+Rake::TestTask.new(:test) do |test|
+  test.test_files = FileList.new('test/**/test_*.rb') do |list|
+    list.exclude 'test/test_helper.rb'
+    list.exclude 'test/fixtures/**/*.rb'
+  end
+  test.libs << 'test'
+  test.verbose = true
+end
+
+namespace :test do
+  task :gemspec_dup do
+    gemspec = Rake.application.jeweler.gemspec
+    dupped_gemspec = gemspec.dup
+    cloned_gemspec = gemspec.clone
+    puts gemspec.to_ruby
+    puts dupped_gemspec.to_ruby
+  end
+end
+
+require 'yard'
+YARD::Rake::YardocTask.new do |t|
+  t.files   = FileList['lib/**/*.rb'].exclude('lib/jeweler/templates/**/*.rb')
+end
+
+require 'rcov/rcovtask'
+Rcov::RcovTask.new(:rcov => :check_dependencies) do |rcov|
+  rcov.libs << 'test'
+  rcov.pattern = 'test/**/test_*.rb'
+end
+
+require 'cucumber/rake/task'
+Cucumber::Rake::Task.new(:features) do |features|
+  features.cucumber_opts = "features --format progress"
+end
+namespace :features do
+  Cucumber::Rake::Task.new(:pretty) do |features|
+    features.cucumber_opts = "features --format progress"
+  end
+end
+
+if ENV["RUN_CODE_RUN"] == "true"
+  task :default => [:test, :features]
+else
+  task :default => :test
+end
+

data/search_biomodel/ruby/1.8/gems/jeweler-1.6.2/bin/jeweler

@@ -0,0 +1,5 @@
+#!/usr/bin/env ruby
+$LOAD_PATH.unshift File.join(File.dirname(__FILE__), '..', 'lib')
+require 'jeweler/generator'
+
+exit Jeweler::Generator::Application.run!(*ARGV)

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

@@ -0,0 +1,103 @@
+Feature: generating cucumber stories
+  In order to get started using cucumber in a project
+  A user should be able to
+  generate a project setup for their testing framework of choice
+
+  Scenario: sans cucumber setup
+    Given a working directory
+    And I have configured git sanely
+    And I do not want cucumber stories
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+
+    And a file named 'the-perfect-gem/features/the-perfect-gem.feature' is not created
+    And a file named 'the-perfect-gem/features/support/env.rb' is not created
+    And a file named 'the-perfect-gem/features/steps/the-perfect-gem_steps.rb' is not created
+
+  Scenario: basic cucumber setup
+    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 cucumber directories are created
+
+    And a file named 'the-perfect-gem/features/the-perfect-gem.feature' is created
+    And a file named 'the-perfect-gem/features/support/env.rb' is created
+    And a file named 'the-perfect-gem/features/step_definitions/the-perfect-gem_steps.rb' is created
+
+    And 'features/support/env.rb' requires 'bundler'
+    And 'features/support/env.rb' sets up bundler using the default and development groups
+    And 'features/support/env.rb' requires 'the-perfect-gem'
+
+  Scenario: bundler
+    Given a working directory
+    And I want bundler
+    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'
+    And 'features/support/env.rb' requires 'bundler'
+    And 'features/support/env.rb' sets up bundler using the default and development groups
+
+  Scenario: no bundler
+    Given a working directory
+    And I have configured git sanely
+    And I do not want bundler
+    And I want cucumber stories
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    And 'features/support/env.rb' does not require 'bundler'
+    And 'features/support/env.rb' does not setup bundler
+
+  Scenario: cucumber setup for bacon
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'test/unit/assertions'
+    And cucumber world extends "Test::Unit::Assertions"
+
+  Scenario: cucumber setup for shoulda
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'test/unit/assertions'
+    And cucumber world extends "Test::Unit::Assertions"
+
+  Scenario: cucumber setup for testunit
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'test/unit/assertions'
+    And cucumber world extends "Test::Unit::Assertions"
+
+  Scenario: cucumber setup for minitest
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'minitest/unit'
+    And cucumber world extends "MiniTest::Assertions"
+
+  Scenario: cucumber setup for rspec
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'the-perfect-gem'
+    And 'features/support/env.rb' requires 'rspec/expectations'
+
+  Scenario: cucumber setup for mirconaut
+    Given a working directory
+    And I have configured git sanely
+    And I want cucumber stories
+    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'features/support/env.rb' requires 'the-perfect-gem'
+    And 'features/support/env.rb' requires 'micronaut/expectations'
+    And cucumber world extends "Micronaut::Matchers"

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

@@ -0,0 +1,86 @@
+Feature: generated directory layout
+  In order to start a new gem
+  A user should be able to
+  generate a directory layout
+
+  Scenario: shared
+    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 directory named 'the-perfect-gem' is created
+    And a directory named 'the-perfect-gem/lib' is created
+
+    And a file named 'the-perfect-gem/README.rdoc' is created
+    And a file named 'the-perfect-gem/.document' is created
+    And a file named 'the-perfect-gem/lib/the-perfect-gem.rb' is created
+
+  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 a directory named 'the-perfect-gem/spec' is created
+
+    And a file named 'the-perfect-gem/spec/spec_helper.rb' is created
+    And a file named 'the-perfect-gem/spec/the-perfect-gem_spec.rb' is created
+
+  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 a directory named 'the-perfect-gem/test' is created
+
+    And a file named 'the-perfect-gem/test/helper.rb' is created
+    And a file named 'the-perfect-gem/test/test_the-perfect-gem.rb' is created
+
+  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 a directory named 'the-perfect-gem/spec' is created
+
+    And a file named 'the-perfect-gem/spec/spec_helper.rb' is created
+    And a file named 'the-perfect-gem/spec/the-perfect-gem_spec.rb' is created
+
+  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 a directory named 'the-perfect-gem/test' is created
+
+    And a file named 'the-perfect-gem/test/helper.rb' is created
+    And a file named 'the-perfect-gem/test/test_the-perfect-gem.rb' is created
+
+  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 a directory named 'the-perfect-gem/test' is created
+
+    And a file named 'the-perfect-gem/test/helper.rb' is created
+    And a file named 'the-perfect-gem/test/test_the-perfect-gem.rb' is created
+
+  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 a directory named 'the-perfect-gem/examples' is created
+
+    And a file named 'the-perfect-gem/examples/example_helper.rb' is created
+    And a file named 'the-perfect-gem/examples/the-perfect-gem_example.rb' is created
+
+  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 a directory named 'the-perfect-gem/tests' is created
+
+    And a file named 'the-perfect-gem/tests/tests_helper.rb' is created
+    And a file named 'the-perfect-gem/tests/the-perfect-gem_tests.rb' is created

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

@@ -0,0 +1,13 @@
+Feature: generated .document
+  In order to easily generate RDoc
+  A user should be able to
+  generate reasonable .document file
+
+  Scenario: .document
+    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 '.document' contains 'lib/**/*.rb'
+    And '.document' contains 'bin/*'
+    And '.document' contains 'features/**/*.feature'
+    And '.document' contains 'LICENSE.txt'

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

@@ -0,0 +1,9 @@
+Feature: Getting options from environment variable
+  In order to avoid having to type --rspec over and over
+  A user will need to set up a JEWELER_OPTS environment variable
+
+  Scenario: Environment variable set
+    Given a working directory
+    And I set JEWELER_OPTS env variable to "--rspec"
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'spec/the-perfect-gem_spec.rb' should describe 'ThePerfectGem'

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

@@ -0,0 +1,71 @@
+Feature: generated Gemfiel
+  In order to start a new gem
+  A user should be able to
+  generate a Gemfile
+
+  Background:
+    Given a working directory
+    And I have configured git sanely
+
+  Scenario: disabled
+    Given I do not want bundler
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    Then a file named 'the-perfect-gemGemfile' is not created
+
+  Scenario: enabled
+    Given I want bundler
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    Then a file named 'the-perfect-gem/Gemfile' is created
+
+  Scenario: default
+    When I generate a project named 'the-perfect-gem' that is 'zomg, so good'
+    Then a file named 'the-perfect-gem/Gemfile' is created
+    And 'Gemfile' uses the gemcutter source
+    And 'Gemfile' has a development dependency on 'bundler'
+    And 'Gemfile' has a development dependency on the current version of jeweler
+    And 'Gemfile' has a development dependency on 'rcov'
+
+  Scenario: bacon
+    When I generate a bacon project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'bacon'
+
+  Scenario: minitest
+    When I generate a minitest project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'minitest'
+
+  Scenario: rspec
+    When I generate a rspec project named 'the-perfect-gem' that is 'zomg, so good'
+
+    Then 'Gemfile' has a development dependency on 'rspec'
+
+  Scenario: shoulda
+    When I generate a shoulda project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'shoulda'
+
+  Scenario: micronaut
+    When I generate a micronaut project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'micronaut'
+
+  Scenario: cucumber
+    Given I want cucumber stories
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'cucumber'
+
+  Scenario: reek
+    Given I want reek
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'reek'
+
+  Scenario: roodi
+    Given I want roodi
+    When I generate a testunit project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'roodi'
+
+  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 'Gemfile' has a development dependency on 'yard'
+
+  Scenario: shindo
+    When I generate a shindo project named 'the-perfect-gem' that is 'zomg, so good'
+    Then 'Gemfile' has a development dependency on 'shindo'

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

@@ -0,0 +1,102 @@
+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