Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Fetching contributors…

Cannot retrieve contributors at this time

48 lines (41 sloc) 1.812 kb
@slow
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 new Rails application with Kumade and Jammit
When I create a Heroku remote named "pretend-staging"
And I create a Heroku remote 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 with Kumade::JammitPackager
git push origin master
==> Pushed master -> origin
git branch deploy >/dev/null
git push -f pretend-staging deploy:master
==> Pushed deploy:master -> pretend-staging
==> Migrated pretend-staging
==> Restarted pretend-staging
==> Deployed to: pretend-staging
"""
Scenario: Default environment is staging
When I run kumade with "-p"
Then the output should contain "==> Deployed to: staging"
Scenario: Deploying to an arbitrary environment fails
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 a branch that isn't "master"
When I switch to the "new_branch" branch
And I run kumade with "pretend-staging -p"
Then the output should contain "==> Pushed new_branch -> origin"
And the output should contain "==> Deployed to: pretend-staging"
Jump to Line
Something went wrong with that request. Please try again.