geordi 2.10.1 → 3.0.3

data/lib/geordi/version.rb

@@ -1,3 +1,3 @@
 module Geordi
-  VERSION = '2.10.1'
+  VERSION = '3.0.3'.freeze
 end

metadata

@@ -1,29 +1,29 @@
 --- !ruby/object:Gem::Specification
 name: geordi
 version: !ruby/object:Gem::Version
-  version: 2.10.1
+  version: 3.0.3
 platform: ruby
 authors:
 - Henning Koch
 autorequire: 
-bindir: bin
+bindir: exe
 cert_chain: []
-date: 2020-02-17 00:00:00.000000000 Z
+date: 2020-05-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: thor
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.18.0
+        version: '1'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - ">="
+    - - "~>"
       - !ruby/object:Gem::Version
-        version: 0.18.0
+        version: '1'
 description: Collection of command line tools we use in our daily work with Ruby,
   Rails and Linux at makandra.
 email:
@@ -59,36 +59,24 @@ files:
 - LICENSE
 - README.md
 - Rakefile
-- bin/b
-- bin/cap-all
-- bin/console-for
-- bin/cuc
-- bin/cuc-show
-- bin/cuc-vnc-setup
-- bin/deploy-to-production
-- bin/dump-for
-- bin/dumple
-- bin/geordi
-- bin/gitpt
-- bin/launchy_browser
-- bin/load-dump
-- bin/migrate-all
-- bin/rs
-- bin/run_tests
-- bin/shell-for
-- bin/tests
-- features/commit.feature
-- features/console.feature
-- features/cucumber.feature
-- features/deploy.feature
-- features/dump.feature
-- features/firefox.feature
-- features/server.feature
-- features/setup.feature
-- features/shell.feature
-- features/support/env.rb
-- features/support/step_definitions/aruba_backport_steps.rb
-- features/support/step_definitions/miscellaneous_steps.rb
+- exe/b
+- exe/cap-all
+- exe/console-for
+- exe/cuc
+- exe/cuc-show
+- exe/cuc-vnc-setup
+- exe/deploy-to-production
+- exe/dump-for
+- exe/dumple
+- exe/geordi
+- exe/gitpt
+- exe/launchy_browser
+- exe/load-dump
+- exe/migrate-all
+- exe/rs
+- exe/run_tests
+- exe/shell-for
+- exe/tests
 - geordi.gemspec
 - lib/geordi.rb
 - lib/geordi/COMMAND_TEMPLATE
@@ -149,14 +137,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 2.0.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.0.3
+rubygems_version: 3.1.3
 signing_key: 
 specification_version: 4
 summary: Collection of command line tools we use in our daily work with Ruby, Rails

data/features/commit.feature

@@ -1,17 +0,0 @@
-@ruby>=1.9
-Feature: Creating a git commit from a Pivotal Tracker story
-
-  Scenario: Extra arguments are forwarded to "git commit"
-    Given I have staged changes
-
-    When I run `geordi commit --extra-option` interactively
-      # No optional message
-      And I type ""
-    Then the output should contain "Util.system! git, commit, --allow-empty, -m, [#12] Test Story, --extra-option"
-
-
-  Scenario: With no staged changes, a warning is printed
-    When I run `geordi commit --allow-empty` interactively
-      # No optional message
-      And I type ""
-    Then the output should contain "> No staged changes. Will create an empty commit."

data/features/console.feature

@@ -1,7 +0,0 @@
-Feature: The console command
-  Most aspects of connection to a server are tested in shell feature.
-
-  Scenario: Opening a local Rails console
-    When I run `geordi console`
-    Then the output should contain "# Opening a local Rails console"
-      And the output should contain "Util.system! bundle exec rails console -e development"

data/features/cucumber.feature

@@ -1,261 +0,0 @@
-Feature: The cucumber command
-
-  Background:
-    Given a file named "config/cucumber.yml" with:
-    """
-    default: features
-    rerun: features
-    """
-
-
-  Scenario: Run a single feature
-    Given a file named "features/single.feature" with:
-    """
-    Feature: Running a single feature
-      Scenario: A single scenario
-    """
-
-    When I run `geordi cucumber features/single.feature`
-    Then the output should contain "# Running features"
-      And the output should contain "> Only: features/single.feature"
-      And the output should contain "Features green."
-    But the output should not contain "parallel"
-
-
-  Scenario: Multiple features are run in parallel
-    Given a file named "features/one.feature" with:
-    """
-    Feature: One
-      Scenario: One
-    """
-    And a file named "features/two.feature" with:
-    """
-    Feature: Two
-      Scenario: Two
-    """
-
-    When I run `geordi cucumber`
-    Then the output should contain "# Running features"
-      And the output should contain "> All features in features/"
-      And the output should contain "> Using parallel_tests"
-
-
-  Scenario: Rerunning tests until they pass
-    Given a file named "features/step_definitions/test_steps.rb" with:
-    """
-    Given /^this test fails$/ do
-      raise
-    end
-    """
-    And a file named "features/failing.feature" with:
-    """
-    Feature: Failing feature
-      Scenario: Failing scenario
-        And this test fails
-    """
-
-    When I run `geordi cucumber --rerun=2`
-    Then the output should contain "# Running features"
-      And the output should contain "# Rerun #1 of 2"
-      And the output should contain "# Rerun #2 of 2"
-      And the output should contain "Rerunning failed scenarios"
-      And the output should contain "Using the rerun profile"
-      And the exit status should be 1
-      And the output should contain "Features failed."
-
-
-  Scenario: A rerun should only consider the specified file
-    Note that we need a cucumber.yml to write the rerun.txt and read the rerun.txt for the reruns.
-
-    Given a file named "features/step_definitions/test_steps.rb" with:
-    """
-    Given /^this test fails$/ do
-      raise
-    end
-
-    Given /^I use puts with text "(.*)"$/ do |ann|
-      puts(ann)
-    end
-    """
-      And a file named "features/some.feature" with:
-      """
-      Feature: Failing feature
-        Scenario: Passing scenario
-          And I use puts with text "Running passing Feature"
-
-        Scenario: Failing scenario
-          And I use puts with text "Running failing Feature"
-          And this test fails
-      """
-      And an empty file named "tmp/rerun.txt"
-      And a file named "cucumber.yml" with:
-      """
-      <%
-      rerun_log = 'tmp/rerun.txt'
-      rerun_failures = File.file?(rerun_log) ? File.read(rerun_log).gsub("\n", ' ') : ''
-      log_failures = "--format=rerun --out=#{rerun_log}"
-      %>
-      default: features <%= log_failures %>
-      rerun: <%= rerun_failures %> <%= log_failures %>
-      """
-
-    When I run `geordi cucumber --rerun=1 features/some.feature`
-    Then the output should contain:
-    """
-    # Rerun #1 of 1
-    > Rerunning failed scenarios
-    > Run `geordi vnc` to view the Selenium test browsers
-
-    Using the rerun profile...
-
-    Running failing Feature
-    .F
-
-    (::) failed steps (::)
-
-     (RuntimeError)
-    features/some.feature:7:in `And this test fails'
-
-    Failing Scenarios:
-    cucumber -p rerun features/some.feature:5 # Scenario: Failing scenario
-    """
-
-
-  Scenario: Running all features in a given subfolder
-    Given a file named "features/sub/one.feature" with:
-    """
-    Feature: Testfeature
-    """
-    And a file named "features/sub/two.feature" with:
-    """
-    Feature: Testfeature
-    """
-
-    When I run `geordi cucumber features/sub`
-    Then the output should contain "> Only: features/sub/two.feature, features/sub/one.feature"
-      And the output should contain "> Using parallel_tests"
-
-
-  Scenario: Using the @solo tag
-
-    The cucumber command runs all features without the @solo tag. If any of the
-    specified .feature files contains '@solo', it boots Cucumber a second time
-    and runs only those of the features tagged with @solo.
-
-    Given a file named "features/no_solo.feature" with:
-    """
-    Feature: Test without solo tag
-      Scenario: This scenario can run in parallel
-    """
-    And a file named "features/solo.feature" with:
-    """
-    Feature: Solo test
-      @solo
-      Scenario: This scenario must NOT run in parallel
-    """
-
-    When I run `geordi cucumber --verbose features`
-    Then the output should contain "# Running @solo features"
-      And the output should match /^> .*cucumber .*--tags @solo/
-      And the output should contain "# Running features"
-      And the output should match /^> .*cucumber .*--tags \"~@solo\"/
-
-
-  Scenario: When there are no scenarios tagged @solo, the extra run is skipped
-    Given a file named "features/no_solo/one.feature" with:
-    """
-    Feature: Test without solo tag
-      Scenario: This scenario can run in parallel
-    """
-    And a file named "features/no_solo/two.feature" with:
-    """
-    Feature: A second test to provoke a parallel run
-      Scenario: Something
-    """
-    And a file named "features/solo.feature" with:
-    """
-    Feature: Solo test
-      @solo
-      Scenario: This scenario is not even run during this test
-    """
-
-    When I run `geordi cucumber features/no_solo --verbose`
-    Then the output should contain "# Running features"
-      And the output should match /^> .*features .*--tags \"~@solo\"/
-    But the output should not contain "# Running @solo features"
-
-
-  Scenario: When called with line numbers, the @solo extra run is skipped
-
-    Note that with line numbers in the passed file names, features are run
-    serially.
-
-    Given a file named "features/example.feature" with:
-    """
-    Feature: Test without solo tag
-      Scenario: Example scenario
-      Scenario: Other scenario
-    """
-
-    When I run `geordi cucumber --verbose features/example.feature:2`
-    Then the output should contain "# Running features"
-    But the output should not contain "# Running @solo features"
-      # Regression test, with line numbers grep would fail with:
-      #   grep: features/example.feature:2: No such file or directory
-      And the output should not contain "No such file or directory"
-
-
-  Scenario: It does not start the full test run when the @solo run fails
-    Given a file named "features/step_definitions/test_steps.rb" with:
-    """
-    Given 'this test fails' do
-      raise
-    end
-    """
-    And a file named "features/failing.feature" with:
-    """
-    Feature: Failing feature
-      @solo
-      Scenario: Failing scenario
-        And this test fails
-      Scenario: Other scenario
-    """
-
-    When I run `geordi cucumber`
-    Then the output should contain "# Running @solo features"
-      And the output should contain "Features failed."
-    But the output should not contain "# Running features"
-
-
-  Scenario: Specifying a firefox version to use
-    Given a file named "features/sub/one.feature" with:
-    """
-    Feature: Testfeature
-    """
-    And a file named ".firefox-version" with:
-    """
-    24.0
-    """
-
-    When I run `geordi cucumber --verbose`
-    Then the output should match /^> PATH=.*24.0:\$PATH.* features/
-
-
-  Scenario: Running all cucumber features matching a given string
-    Given a file named "features/given.feature" with "Feature: given"
-    And a file named "features/other.feature" with "Feature: other"
-
-    When I run `geordi cucumber --containing given`
-    Then the output should contain "Only: features/given.feature"
-    But the output should not contain "other.feature"
-
-
-  Scenario: Passing a format argument will skip the default format for a single run
-    Given a file named "features/single.feature" with:
-    """
-    Feature: Running a single feature
-      Scenario: A single scenario
-    """
-
-    When I run `geordi cucumber features/single.feature --format=pretty --verbose`
-    Then the output should contain "b cucumber features/single.feature --format pretty"

data/features/deploy.feature

@@ -1,66 +0,0 @@
-Feature: The deploy command
-
-  Scenario: Deploying from master to staging
-
-    Unfortunately, Aruba cannot run commands truly interactively. We need to
-    answer prompts blindly, and check the output afterwards.
-
-    When I run `geordi deploy` interactively
-      # Answer three prompts
-      And I type "staging"
-      And I type "master"
-      And I type ""
-      # Confirm deployment
-      And I type "yes"
-    Then the output should contain:
-      """
-      # Checking whether your master branch is ready
-      Util.system! git checkout master
-      > All good.
-
-      # You are about to:
-      > Deploy to staging
-      Go ahead with the deployment? [n]
-      """
-      And the output should contain:
-      """
-      > cap staging deploy:migrations
-      Util.system! cap staging deploy:migrations
-
-      > Deployment complete.
-      """
-
-
-  Scenario: Deploying the current branch
-
-    Deploying the current branch requires support by the deployed application:
-    its deploy config needs to pick up the DEPLOY_BRANCH environment variable.
-
-    When I run `geordi deploy --current-branch` interactively
-      # Answer deployment stage prompt
-      And I type "staging"
-    Then the output should contain "configure config/deploy/staging.rb"
-      And the output should contain "ENV['DEPLOY_BRANCH']"
-
-    Given a file named "config/deploy/staging.rb" with:
-      """
-      set :branch, ENV['DEPLOY_BRANCH'] || 'master'
-      """
-    When I run `geordi deploy --current-branch` interactively
-      # Answer deployment stage prompt
-      And I type "staging"
-      # Confirm deployment
-      And I type "yes"
-    # Current branch is always "master" during tests
-    Then the output should contain "From current branch master"
-      And the output should contain "DEPLOY_BRANCH=master cap staging deploy:migrations"
-
-
-  Scenario: Deploying with a given stage
-    Given a file named "config/deploy/staging.rb" with "staging.rb exists"
-
-    When I run `geordi deploy staging` interactively
-      And I type "master"
-      And I type ""
-      And I type "no"
-    Then the output should not contain "Deployment stage: [staging]"