kumade_executable.feature

@extra-timeout @creates-remote @disable-bundler
Feature: Kumade executable
  As a user
  I want to be able to use the kumade executable
  So I can have a better experience than Rake provides

  Background:
    Given a directory named "executable"
    And I cd to "executable"
    And I set up the Gemfile with kumade
    And I add "jammit" to the Gemfile
    And I bundle
    When I set up a git repo
    And I create a Heroku remote for "pretend-staging-app" named "pretend-staging"
    And I create a Heroku remote for "app-two" named "staging"
    And I create a non-Heroku remote named "bad-remote"

  Scenario: Pretend mode with a Heroku remote
    When I run kumade with "pretend-staging -p"
    Then the output should contain "In Pretend Mode"
    And the output should contain:
      """
      ==> Git repo is clean
      ==> Packaged assets with Jammit
               run  git push origin master
      ==> Pushed master -> origin
               run  git branch deploy
               run  git push -f pretend-staging deploy:master
      ==> Pushed deploy:master -> pretend-staging
      ==> Migrated pretend-staging-app
               run  git checkout master && git branch -D deploy
      ==> Deployed to: pretend-staging
      """
    But the output should not contain "==> Packaged assets with More"

  Scenario: Default environment is staging
    When I run kumade with "-p"
    Then the output should contain "==> Deployed to: staging"

  Scenario: Can deploy to arbitrary environment
    When I run kumade with "bamboo"
    Then the output should contain "==> Deploying to: bamboo"
    And the output should match /Cannot deploy: /

  Scenario: Deploying to a non-Heroku remote fails
    When I run kumade with "bad-remote"
    Then the output should match /==> ! Cannot deploy: "bad-remote" remote does not point to Heroku/

  Scenario: Deploy from another branch
    When I run `git checkout -b new_branch`
    And I run kumade with "pretend-staging -p"
    Then the output should contain:
      """
      ==> Git repo is clean
      ==> Packaged assets with Jammit
               run  git push origin new_branch
      ==> Pushed new_branch -> origin
               run  git branch deploy
               run  git push -f pretend-staging deploy:master
      ==> Pushed deploy:master -> pretend-staging
      ==> Migrated pretend-staging-app
               run  git checkout new_branch && git branch -D deploy
      ==> Deployed to: pretend-staging
      """

  Scenario: Git is clean if there are untracked files
    Given I write to "new-file" with:
      """
      clean
      """
    When I run kumade with "pretend-staging"
    Then the output from "bundle exec kumade pretend-staging" should not contain "==> ! Cannot deploy: repo is not clean"

  Scenario: Git is not clean if a tracked file is modified
    Given I write to "new-file" with:
      """
      clean
      """
    And I commit everything in the current repo
    When I append to "new-file" with "dirty it up"
    And I run kumade with "pretend-staging"
    Then the output from "bundle exec kumade pretend-staging" should contain "==> ! Cannot deploy: repo is not clean"

  Scenario: Jammit packager runs if Jammit is installed
    When I run kumade with "pretend-staging"
    Then the output from "bundle exec kumade pretend-staging" should contain "==> ! Error: Jammit::MissingConfiguration"

  Scenario: Run custom task before jammit
    Given I write to "Rakefile" with:
      """
      namespace :kumade do
        task :before_asset_compilation do
          puts 'Hi!'
        end
      end
      """
    When I run kumade with "pretend-staging -p"
    Then the output should match /kumade:before_asset_compilation.*Packaged assets with Jammit/