saasy 0.0.1

data/lib/generators/saucy/features/templates/features/new_account.feature

@@ -0,0 +1,33 @@
+Feature: user adds a new account
+
+  Background:
+    Given a plan exists with a name of "Free"
+
+  Scenario: existing user adds an account
+    Given I am signed up as "user@example.com/test"
+    When I go to the sign up page for the "Free" plan
+    And I fill in "Email" with "user@example.com"
+    And I fill in "Password" with "test"
+    And I press "Sign up"
+    Then I should see "created"
+    But I should not see "Instructions for confirming"
+    And I should be on the new project page for the newest account by "user@example.com"
+
+  Scenario: sign up for two accounts
+    When I go to the sign up page for the "Free" plan
+    And I fill in "Email" with "email@person.com"
+    And I fill in "Password" with "password"
+    And I press "Sign up"
+    Then I should see "created"
+    And I should be on the new project page for the newest account by "email@person.com"
+    When I go to the settings page
+    Then I should see 1 account
+    And I follow "Add new account"
+    And I follow "Free"
+    Then I should see "Your existing user, email, will be added as the first administrator on this new account."
+    And I press "Sign up"
+    Then I should see "created"
+    But I should not see "Instructions for confirming"
+    And I should be on the new project page for the newest account by "email@person.com"
+    When I go to the settings page
+    Then I should see 2 accounts

data/lib/generators/saucy/features/templates/features/project_dropdown.feature

@@ -0,0 +1,77 @@
+Feature: Project Dropdown
+  As a user
+  So that I can work on several projects
+  I can easily switch between projects
+
+  Background:
+    Given I am signed in as "user@example.com" under the "Werther's" account
+    And the following projects exist:
+      | name     | account         |
+      | Pacelog  | name: Werther's |
+      | Narrator | name: Werther's |
+      | Flapper  | name: Werther's |
+    And "user@example.com" is a member of the "Pacelog" project
+
+  @javascript
+  Scenario: Navigate from one project to another
+    Given "user@example.com" is a member of the "Narrator" project
+    When I go to the "Pacelog" project page
+    Then the page should not include "#project-selection ul.expanded"
+    When I click "#project-selection h1 a img"
+    Then the page should include "#project-selection ul.expanded"
+    And I should not see "Flapper"
+    When I follow "Narrator" within "#project-selection ul"
+    Then I should be on the "Narrator" project page
+
+  @javascript
+  Scenario: Click outside the projects dropdown to hide it
+    Given "user@example.com" is a member of the "Narrator" project
+    When I go to the "Narrator" project page
+    Then the page should not include "#project-selection ul.expanded"
+    When I click "#project-selection h1 a img"
+    Then the page should include "#project-selection ul.expanded"
+    When I click "body"
+    Then the page should not include "#project-selection ul.expanded"
+
+  Scenario: On project pages, the project name is rendered in the header
+    When I go to the "Pacelog" project page
+    Then I should see "Pacelog" within "#project-selection h1 a"
+
+  Scenario: On project pages with multiple projects, the project name and chooser are rendered in the header
+    Given "user@example.com" is a member of the "Narrator" project
+    When I go to the "Pacelog" project page
+    Then I should see "Pacelog" within "#project-selection h1 a"
+    And the page should include "#project-selection h1 a img"
+
+  Scenario: On non-project pages, the account name is rendered in the header with the project chooser
+    Given "user@example.com" is an admin of the "Narrator" project
+    When I am on the memberships page for the "Werther's" account
+    Then I should see "Projects" within "#project-selection h1 a"
+    And the page should include "#project-selection h1 a img"
+
+    When I am on the edit profile page
+    Then I should see "Projects" within "#project-selection h1 a"
+    And the page should include "#project-selection h1 a img"
+
+  Scenario: An admin on non-project pages, the new project link goes to the new project page for the right account
+    Given "user@example.com" is an admin of the "Narrator" project
+    When I am on the edit profile page
+    Then I should see "Create a new project" within "#project-selection"
+    When I follow "Create a new project"
+    Then I should be on the new project page for the "Werther's" account
+
+  Scenario: An admin on project pages, the new project link goes to the new project page for the right account
+    Given "user@example.com" is an admin of the "Narrator" project
+    When I go to the "Pacelog" project page
+    Then I should see "Create a new project" within "#project-selection"
+    When I follow "Create a new project"
+    Then I should be on the new project page for the "Werther's" account
+
+  Scenario: A non-admin on non-project pages, should not see the new project link
+    Given "user@example.com" is a member of the "Narrator" project
+    When I am on the edit profile page
+    Then I should not see "Create a new project" within "#project-selection"
+
+  Scenario: A non-admin on project pages, should not see the new project link
+    When I go to the "Pacelog" project page
+    Then I should not see "Create a new project" within "#project-selection"

data/lib/generators/saucy/features/templates/features/sign_up.feature

@@ -0,0 +1,32 @@
+Feature: Sign up
+  In order to get access to protected sections of the site
+  A user
+  Should be able to sign up
+
+  Background:
+    Given a plan exists with a name of "Free"
+
+  Scenario: User sees signup terms
+    When I go to the plans page
+    Then I should see "Free"
+    And I should see "Upgrade or Downgrade Anytime"
+    And I there should be a link to the help site
+    When I follow "Free"
+    Then I should see "By clicking Sign up you agree to our Terms of Service"
+
+  Scenario: User signs up with invalid data
+    When I go to the sign up page for the "Free" plan
+    Then I should see "Free"
+    And I fill in "Email" with "invalidemail"
+    And I fill in "Password" with "password"
+    And I should not see "Billing Information"
+    And I press "Sign up"
+    Then the form should have inline error messages
+
+  Scenario: User signs up with valid data
+    When I go to the list of plans page
+    And I follow "Free"
+    And I fill in "Email" with "email@person.com"
+    And I fill in "Password" with "password"
+    And I press "Sign up"
+    Then I should see "created"

data/lib/generators/saucy/features/templates/features/sign_up_paid.feature

@@ -0,0 +1,65 @@
+Feature: Sign up
+  In order to get access to protected sections of the site
+  A user
+  Should be able to sign up
+
+  Background:
+    Given a paid plan exists with a name of "Paid"
+    And a plan exists with a name of "Free"
+
+  Scenario: User signs up for a paid plan with invalid data
+    When I go to the sign up page for the "Paid" plan
+    Then I should see "Paid"
+    And I should see "$1/month"
+    And the "Card number" field should have autocomplete off
+    And the "Verification code" field should have autocomplete off
+    And I fill in "Email" with "invalidemail"
+    And I fill in "Password" with "password"
+    And I should see "Billing Information"
+    And I press "Sign up"
+    Then the form should have inline error messages
+
+  Scenario: User signs up for a paid plan with valid data
+    When I go to the list of plans page
+    Then I should see the "Paid" plan before the "Free" plan
+    When I follow "Paid"
+    And I fill in "Email" with "email@person.com"
+    And I fill in "Password" with "password"
+    And I fill in "Cardholder name" with "Ralph Robot"
+    And I fill in "Billing email" with "accounting@example.com"
+    And I fill in "Card number" with "4111111111111111"
+    And I fill in "Verification code" with "123"
+    And I select "March" from "Expiration month"
+    And I select "2020" from "Expiration year"
+    And I press "Sign up"
+    Then I should see "created"
+
+  Scenario: User signs up for a paid plan with an invalid credit card number
+    Given that the credit card "4111112" is invalid
+    When I go to the list of plans page
+    And I follow "Paid"
+    And I fill in "Email" with "email@person.com"
+    And I fill in "Password" with "password"
+    And I fill in "Cardholder name" with "Ralph Robot"
+    And I fill in "Billing email" with "accounting@example.com"
+    And I fill in "Card number" with "4111112"
+    And I fill in "Verification code" with "123"
+    And I select "March" from "Expiration month"
+    And I select "2020" from "Expiration year"
+    And I press "Sign up"
+    Then "Card number" should have the error "is invalid"
+
+  Scenario: User signs up for a paid plan with a credit card that cannot be processed
+    Given that the credit card "4111111111111111" should not be honored
+    When I go to the list of plans page
+    And I follow "Paid"
+    And I fill in "Email" with "email@person.com"
+    And I fill in "Password" with "password"
+    And I fill in "Cardholder name" with "Ralph Robot"
+    And I fill in "Billing email" with "accounting@example.com"
+    And I fill in "Card number" with "4111111111111111"
+    And I fill in "Verification code" with "123"
+    And I select "March" from "Expiration month"
+    And I select "2020" from "Expiration year"
+    And I press "Sign up"
+    Then "Card number" should have the error "Do Not Honor"

data/lib/generators/saucy/features/templates/features/trial_plans.feature

@@ -0,0 +1,82 @@
+Feature: Trial plans
+
+  Background:
+    Given the following plan exists:
+      | name    | price | trial |
+      | Temp    | 0     | true  |
+      | Eternal | 0     | false |
+    And the following limits exist:
+      | plan          | name  | value | value_type |
+      | name: Temp    | users | 2     | number     |
+      | name: Eternal | users | 2     | number     |
+
+  Scenario: Sign up for a trial plan
+    When I go to the list of plans page
+    And I follow "Temp"
+    Then I should see "Free"
+    And I should see "Trial"
+    And I should see "Your trial will expire after 30 days"
+    But I should not see "users"
+    When I fill in "Email" with "email@person.com"
+    And I fill in "Password" with "password"
+    And I press "Sign up"
+    Then I should see "created"
+
+  Scenario: use an account during the trial
+    Given a "Temp" account exists with a name of "Test" created 29 days ago
+    And I am signed in as an admin of the "Test" account
+    When I go to the projects page for the "Test" account
+    Then I should see "Test"
+    And I should not see "expired"
+
+  Scenario: Try to use an expired trial plan
+    Given a "Temp" account exists with a name of "Test" created 30 days ago
+    And I am signed in as an admin of the "Test" account
+    When I go to the projects page for the "Test" account
+    Then I should be on the upgrade plan page for the "Test" account
+    And I should see "expired"
+    And the "Temp" plan should be disabled
+
+  Scenario: Sign up for a non-trial plan
+    When I go to the list of plans page
+    And I follow "Eternal"
+    Then I should see "users"
+    But I should not see "Trial"
+    And I should not see "expire"
+
+  Scenario: Use a non-trial plan forever
+    Given an "Eternal" account exists with a name of "Test" created 30 days ago
+    And I am signed in as an admin of the "Test" account
+    When I go to the projects page for the "Test" account
+    Then I should see "Test"
+    And I should not see "expired"
+
+  Scenario: Receive a reminder about an expiring trial plan
+    Given a "Temp" account exists with a name of "Test" created 23 days ago
+    And a user exists with an email of "admin@example.com"
+    And "admin@example.com" is an admin of the "Test" account
+    When the daily Saucy jobs are processed
+    And I sign in as "admin@example.com"
+    And I follow the link sent to "admin@example.com" with subject "Your trial is expiring soon"
+    Then I should be on the upgrade plan page for the "Test" account
+
+  Scenario: Receive a reminder about activating an account
+    Given an account exists with a name of "Test"
+    And a user exists with an email of "admin@example.com"
+    And "admin@example.com" is an admin of the "Test" account
+    And the "Test" account was created 7 days ago
+    When the daily Saucy jobs are processed
+    Then an email with subject "A check in" should be sent to "admin@example.com"
+    When I sign in as "admin@example.com/password"
+    And I follow the link sent to "admin@example.com" with subject "A check in"
+    Then I should be on the new project page for the newest account by "admin@example.com"
+
+  Scenario: Receive a reminder about an expired trial plan
+    Given a "Temp" account exists with a name of "Test" created 30 days ago
+    And a user exists with an email of "admin@example.com"
+    And "admin@example.com" is an admin of the "Test" account
+    When the daily Saucy jobs are processed
+    And I sign in as "admin@example.com"
+    And I follow the link sent to "admin@example.com" with subject "Your trial has ended"
+    Then I should be on the upgrade plan page for the "Test" account
+

data/lib/generators/saucy/features/templates/step_definitions/account_steps.rb

@@ -0,0 +1,30 @@
+Given /^an? "([^"]+)" account exists with a name of "([^"]*)" created (\d+) days ago$/ do |plan_name, account_name, days|
+  plan = Plan.find_by_name!(plan_name)
+  Factory(:account, :created_at => days.to_i.days.ago, :plan => plan, :name => account_name)
+end
+
+Given /^the "([^"]*)" account was created (\d+) days ago$/ do |account_name, days|
+  Account.find_by_name!(account_name).tap do |account|
+    account.created_at = days.to_i.days.ago
+    account.save!
+  end
+end
+
+Given /^the following limit exists for the "([^"]*)" account:$/ do |account_name, table|
+  Account.find_by_name!(account_name).tap do |account|
+    table.hashes.each do |limit|
+      account.plan.limits.create!(limit)
+    end
+  end
+end
+
+When /^I follow "([^"]*)" for the "([^"]*)" account$/ do |link_text, account_name|
+  account = Account.find_by_name!(account_name)
+  within "##{dom_id(account)}" do
+    click_link link_text
+  end
+end
+
+Then /^I should see (\d+) accounts?$/ do |count|
+  page.all("#user_accounts li").size.should == count.to_i
+end

data/lib/generators/saucy/features/templates/step_definitions/braintree_steps.rb

@@ -0,0 +1,25 @@
+Given /^that the credit card "([^"]*)" is invalid$/ do |number|
+  FakeBraintree.failures[number] = { "message" => "Credit card number is invalid.", "errors" => { "customer" => { "errors" => [], "credit-card" => { "errors" => [{ "message" => "Credit card number is invalid.", "code" => 81715, "attribute" => :number }] }}}}
+end
+
+Given /^that the credit card "([^"]*)" should not be honored$/ do |number|
+  FakeBraintree.failures[number] = { "message" => "Do Not Honor", "code" => "2000", "status" => "processor_declined" }
+end
+
+Given /^the "([^"]*)" account is past due$/ do |account_name|
+  account = Account.find_by_name!(account_name)
+  account.update_attribute(:subscription_status, Braintree::Subscription::Status::PastDue)
+end
+
+Given /^the following transaction exist for the "([^"]*)" account:$/ do |account_name, table|
+  account = Account.find_by_name!(account_name)
+  subscription = FakeBraintree.subscriptions[account.subscription_token]
+  subscription["transactions"] = []
+  table.hashes.each do |transaction|
+    FakeBraintree.transaction = { :status => transaction["status"],
+                                  :amount => transaction["amount"],
+                                  :created_at => Time.parse(transaction["created_at"]),
+                                  :subscription_id => account.subscription_token }
+    subscription["transactions"] << FakeBraintree.generated_transaction
+  end
+end

data/lib/generators/saucy/features/templates/step_definitions/cron_steps.rb

@@ -0,0 +1,23 @@
+require 'rake'
+
+module RakeHelpers
+  def fake_rake
+    old_rake = Rake.application
+    rake = Rake::Application.new
+    Rake.application = rake
+    task :environment
+    yield(rake)
+  ensure
+    Rake.application = old_rake
+  end
+end
+
+World(RakeHelpers)
+
+When /^the daily Saucy jobs are processed$/ do
+  fake_rake do |rake|
+    Saucy::Engine.new.load_tasks
+    rake['saucy:daily'].invoke
+  end
+end
+

data/lib/generators/saucy/features/templates/step_definitions/email_steps.rb

@@ -0,0 +1,40 @@
+When /^I follow the link sent to "([^"]+)"$/ do |email_address|
+  email = ActionMailer::Base.deliveries.detect do |tmail|
+    tmail.to.include?(email_address)
+  end or raise "No email sent to #{email_address}"
+
+  unless match = email.body.match(%r{http://\S+})
+    raise "No link included in the email:\n#{email.body}"
+  end
+  url = match[0]
+
+  visit url
+end
+
+When /^I follow the link sent to "([^"]+)" with subject "([^"]+)"$/ do |email_address, subject|
+  to_address = ActionMailer::Base.deliveries.select do |tmail|
+    tmail.to.include?(email_address)
+  end or raise "No email sent to #{email_address}"
+
+  email = to_address.detect do |tmail|
+    tmail.subject.include?(subject)
+  end or raise "No email sent to #{email_address} with subject #{subject}"
+
+  unless match = email.body.match(%r{http://\S+})
+    raise "No link included in the email:\n#{email.body}"
+  end
+  url = match[0]
+
+  visit url
+end
+
+Then /^an email with subject "([^"]*)" should be sent to "([^"]*)"$/ do |subject, to_address|
+  email = ActionMailer::Base.deliveries.detect do |tmail|
+    tmail.subject.include?(subject)
+  end or raise "No email with subject #{subject}"
+
+  unless email.to.include?(to_address)
+    raise "No email sent to #{to_address}"
+  end
+end
+

data/lib/generators/saucy/features/templates/step_definitions/factory_girl_steps.rb

@@ -0,0 +1 @@
+require 'factory_girl/step_definitions'

data/lib/generators/saucy/features/templates/step_definitions/html_steps.rb

@@ -0,0 +1,51 @@
+Then /^the form should have inline error messages$/ do
+  page.should have_css(".error")
+end
+
+When /^the "([^"]*)" field should have autocomplete off$/ do |field|
+  field = page.find_field(field)
+  field["autocomplete"].should == "off"
+end
+
+Then /^"([^"]*)" should have the error "([^"]*)"$/ do |field, error|
+  field = page.find_field(field)
+  field.find(:xpath, "following-sibling::p[@class='inline-errors'][contains(text(), '#{error}')]").should_not be_nil
+end
+
+Then /^the "([^"]*)" field(?: within "([^"]*)")? should have nothing in it$/ do |field, selector|
+  with_scope(selector) do
+    field = find_field(field)
+    field_value = (field.tag_name == 'textarea') ? field.text : field.value
+    if field_value.respond_to? :should
+      field_value.should be_nil
+    else
+      assert_nil(field_value)
+    end
+  end
+end
+
+Then /^I there should be a link to the help site$/ do
+  page.should have_css("a[href*='help.example.com']")
+end
+
+Then /^"([^"]*)" should not be expanded$/ do |selector|
+  page.has_css?("#{selector}")
+  page.has_no_css?("#{selector}.expanded")
+end
+
+Then /^"([^"]*)" should be expanded/ do |selector|
+  page.has_css?("#{selector}")
+  page.has_css?("#{selector}.expanded")
+end
+
+When %r{^I click "([^"]*)"$} do |selector|
+  find(selector).click
+end
+
+Then /^the page should (not )?include "([^"]*)"$/ do |should_not_contain, selector|
+  if should_not_contain.present?
+    page.should have_no_css(selector)
+  else
+    page.should have_css(selector)
+  end
+end