tang 0.0.1

data/spec/routing/tang/admin/customers_routing_spec.rb

@@ -0,0 +1,34 @@
+require "rails_helper"
+
+module Tang
+  RSpec.describe Admin::CustomersController, type: :routing do
+    routes { Tang::Engine.routes }
+    describe "routing" do
+
+      it "routes to #index" do
+        expect(:get => "/admin/customers").to route_to("tang/admin/customers#index")
+      end
+
+      it "routes to #show" do
+        expect(:get => "/admin/customers/1").to route_to("tang/admin/customers#show", :id => "1")
+      end
+
+      it "routes to #edit" do
+        expect(:get => "/admin/customers/1/edit").to route_to("tang/admin/customers#edit", :id => "1")
+      end
+
+      it "routes to #update via PUT" do
+        expect(:put => "/admin/customers/1").to route_to("tang/admin/customers#update", :id => "1")
+      end
+
+      it "routes to #update via PATCH" do
+        expect(:patch => "/admin/customers/1").to route_to("tang/admin/customers#update", :id => "1")
+      end
+
+      it "routes to #destroy" do
+        expect(:delete => "/admin/customers/1").to route_to("tang/admin/customers#destroy", :id => "1")
+      end
+
+    end
+  end
+end

data/spec/routing/tang/admin/plans_routing_spec.rb

@@ -0,0 +1,44 @@
+require "rails_helper"
+
+module Tang
+  RSpec.describe Admin::PlansController, type: :routing do
+
+    routes { Tang::Engine.routes }
+
+    describe "routing" do
+
+      it "routes to #index" do
+        expect(:get => "/admin/plans").to route_to("tang/admin/plans#index")
+      end
+
+      it "routes to #new" do
+        expect(:get => "/admin/plans/new").to route_to("tang/admin/plans#new")
+      end
+
+      it "routes to #show" do
+        expect(:get => "/admin/plans/1").to route_to("tang/admin/plans#show", :id => "1")
+      end
+
+      it "routes to #edit" do
+        expect(:get => "/admin/plans/1/edit").to route_to("tang/admin/plans#edit", :id => "1")
+      end
+
+      it "routes to #create" do
+        expect(:post => "/admin/plans").to route_to("tang/admin/plans#create")
+      end
+
+      it "routes to #update via PUT" do
+        expect(:put => "/admin/plans/1").to route_to("tang/admin/plans#update", :id => "1")
+      end
+
+      it "routes to #update via PATCH" do
+        expect(:patch => "/admin/plans/1").to route_to("tang/admin/plans#update", :id => "1")
+      end
+
+      it "routes to #destroy" do
+        expect(:delete => "/admin/plans/1").to route_to("tang/admin/plans#destroy", :id => "1")
+      end
+
+    end
+  end
+end

data/spec/routing/tang/admin/subscriptions_routing_spec.rb

@@ -0,0 +1,34 @@
+require "rails_helper"
+
+module Tang
+  RSpec.describe Admin::SubscriptionsController, type: :routing do
+    routes { Tang::Engine.routes }
+    describe "routing" do
+
+      it "routes to #index" do
+        expect(:get => "/admin/subscriptions").to route_to("tang/admin/subscriptions#index")
+      end
+
+      it "routes to #show" do
+        expect(:get => "/admin/subscriptions/1").to route_to("tang/admin/subscriptions#show", :id => "1")
+      end
+
+      it "routes to #edit" do
+        expect(:get => "/admin/subscriptions/1/edit").to route_to("tang/admin/subscriptions#edit", :id => "1")
+      end
+
+      it "routes to #update via PUT" do
+        expect(:put => "/admin/subscriptions/1").to route_to("tang/admin/subscriptions#update", :id => "1")
+      end
+
+      it "routes to #update via PATCH" do
+        expect(:patch => "/admin/subscriptions/1").to route_to("tang/admin/subscriptions#update", :id => "1")
+      end
+
+      it "routes to #destroy" do
+        expect(:delete => "/admin/subscriptions/1").to route_to("tang/admin/subscriptions#destroy", :id => "1")
+      end
+
+    end
+  end
+end

data/spec/spec_helper.rb

@@ -0,0 +1,99 @@
+# This file was generated by the `rails generate rspec:install` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# The `.rspec` file also contains a few flags that are not defaults but that
+# users commonly want.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
+  # have no way to turn it off -- the option exists only for backwards
+  # compatibility in RSpec 3). It causes shared context metadata to be
+  # inherited by the metadata hash of host groups and examples, rather than
+  # triggering implicit auto-inclusion in groups with matching metadata.
+  config.shared_context_metadata_behavior = :apply_to_host_groups
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # This allows you to limit a spec run to individual examples or groups
+  # you care about by tagging them with `:focus` metadata. When nothing
+  # is tagged with `:focus`, all examples get run. RSpec also provides
+  # aliases for `it`, `describe`, and `context` that include `:focus`
+  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
+  config.filter_run_when_matching :focus
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = "spec/examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
+  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
+  config.disable_monkey_patching!
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = 'doc'
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end

data/spec/support/controller_macros.rb

@@ -0,0 +1,21 @@
+module ControllerMacros
+  def login_admin
+    before(:each) do
+      @request.env["devise.mapping"] = Devise.mappings[:user]
+      sign_in FactoryGirl.create(:admin)
+    end
+  end
+
+  def login_customer
+    before(:each) do
+      @request.env["devise.mapping"] = Devise.mappings[:user]
+      customer = FactoryGirl.create(:customer)
+      # customer.confirm!
+      sign_in customer
+    end
+  end
+end
+
+RSpec.configure do |config|
+  config.extend ControllerMacros, type: :controller
+end

data/spec/support/devise.rb

@@ -0,0 +1,5 @@
+RSpec.configure do |config|
+  config.include Devise::Test::ControllerHelpers, type: :controller
+  config.include Devise::Test::ControllerHelpers, type: :view
+  # config.extend ControllerMacros, type: :controller
+end

data/spec/tang_app/README.md

@@ -0,0 +1,28 @@
+== README
+
+This README would normally document whatever steps are necessary to get the
+application up and running.
+
+Things you may want to cover:
+
+* Ruby version
+
+* System dependencies
+
+* Configuration
+
+* Database creation
+
+* Database initialization
+
+* How to run the test suite
+
+* Services (job queues, cache servers, search engines, etc.)
+
+* Deployment instructions
+
+* ...
+
+
+Please feel free to use a different markup language if you do not plan to run
+<tt>rake doc:app</tt>.

data/spec/tang_app/Rakefile

@@ -0,0 +1,6 @@
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require File.expand_path('../config/application', __FILE__)
+
+Rails.application.load_tasks

data/spec/tang_app/app/assets/javascripts/application.js

@@ -0,0 +1,17 @@
+// [App]
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or any plugin's vendor/assets/javascripts directory can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// compiled file.
+//
+// Read Sprockets README (https://github.com/rails/sprockets#sprockets-directives) for details
+// about supported directives.
+//
+//= require jquery
+//= require jquery_ujs
+//= require tang/tang
+//= require_tree .

data/spec/tang_app/app/assets/javascripts/home.js.coffee

@@ -0,0 +1,2 @@
+# Place all the behaviors and hooks related to the matching controller here.
+# All this logic will automatically be available in application.js.

data/spec/tang_app/app/assets/stylesheets/application.css

@@ -0,0 +1,17 @@
+/*
+ * [App]
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or any plugin's vendor/assets/stylesheets directory can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the bottom of the
+ * compiled file so the styles you add here take precedence over styles defined in any styles
+ * defined in the other CSS/SCSS files in this directory. It is generally better to create a new
+ * file per style scope.
+ *
+ *= require tang/tang
+ *= require_tree .
+ *= require_self
+ */

data/spec/tang_app/app/assets/stylesheets/home.css

@@ -0,0 +1,4 @@
+/*
+  Place all the styles related to the matching controller here.
+  They will automatically be included in application.css.
+*/

data/spec/tang_app/app/controllers/application_controller.rb

@@ -0,0 +1,7 @@
+class ApplicationController < ActionController::Base
+  # Prevent CSRF attacks by raising an exception.
+  # For APIs, you may want to use :null_session instead.
+  protect_from_forgery with: :exception
+
+  before_action :set_paper_trail_whodunnit
+end

data/spec/tang_app/app/controllers/home_controller.rb

@@ -0,0 +1,4 @@
+class HomeController < ApplicationController
+  def index
+  end
+end

data/spec/tang_app/app/helpers/application_helper.rb

@@ -0,0 +1,2 @@
+module ApplicationHelper
+end

data/spec/tang_app/app/helpers/home_helper.rb

@@ -0,0 +1,2 @@
+module HomeHelper
+end

data/spec/tang_app/app/models/ability.rb

@@ -0,0 +1,32 @@
+class Ability
+  include CanCan::Ability
+
+  def initialize(user)
+    # Define abilities for the passed in user here. For example:
+    #
+    #   user ||= User.new # guest user (not logged in)
+    #   if user.admin?
+    #     can :manage, :all
+    #   else
+    #     can :read, :all
+    #   end
+    #
+    # The first argument to `can` is the action you are giving the user
+    # permission to do.
+    # If you pass :manage it will apply to every action. Other common actions
+    # here are :read, :create, :update and :destroy.
+    #
+    # The second argument is the resource the user can perform the action on.
+    # If you pass :all it will apply to every resource. Otherwise pass a Ruby
+    # class of the resource.
+    #
+    # The third argument is an optional hash of conditions to further filter the
+    # objects.
+    # For example, here the user can only update published articles.
+    #
+    #   can :update, Article, :published => true
+    #
+    # See the wiki for details:
+    # https://github.com/CanCanCommunity/cancancan/wiki/Defining-Abilities
+  end
+end

data/spec/tang_app/app/models/user.rb

@@ -0,0 +1,10 @@
+class User < ActiveRecord::Base
+  # Include default devise modules. Others available are:
+  # :confirmable, :lockable, :timeoutable and :omniauthable
+  devise :database_authenticatable, :registerable,
+         :recoverable, :rememberable, :trackable, :validatable
+
+  include Tang::Customer
+
+  ROLES = %i[admin]
+end

data/spec/tang_app/app/views/devise/confirmations/new.html.erb

@@ -0,0 +1,16 @@
+<h2>Resend confirmation instructions</h2>
+
+<%= form_for(resource, as: resource_name, url: confirmation_path(resource_name), html: { method: :post }) do |f| %>
+  <%= devise_error_messages! %>
+
+  <div class="field">
+    <%= f.label :email %><br />
+    <%= f.email_field :email, autofocus: true, value: (resource.pending_reconfirmation? ? resource.unconfirmed_email : resource.email) %>
+  </div>
+
+  <div class="actions">
+    <%= f.submit "Resend confirmation instructions" %>
+  </div>
+<% end %>
+
+<%= render "devise/shared/links" %>

data/spec/tang_app/app/views/devise/mailer/confirmation_instructions.html.erb

@@ -0,0 +1,5 @@
+<p>Welcome <%= @email %>!</p>
+
+<p>You can confirm your account email through the link below:</p>
+
+<p><%= link_to 'Confirm my account', confirmation_url(@resource, confirmation_token: @token) %></p>

data/spec/tang_app/app/views/devise/mailer/password_change.html.erb

@@ -0,0 +1,3 @@
+<p>Hello <%= @resource.email %>!</p>
+
+<p>We're contacting you to notify you that your password has been changed.</p>

data/spec/tang_app/app/views/devise/mailer/reset_password_instructions.html.erb

@@ -0,0 +1,8 @@
+<p>Hello <%= @resource.email %>!</p>
+
+<p>Someone has requested a link to change your password. You can do this through the link below.</p>
+
+<p><%= link_to 'Change my password', edit_password_url(@resource, reset_password_token: @token) %></p>
+
+<p>If you didn't request this, please ignore this email.</p>
+<p>Your password won't change until you access the link above and create a new one.</p>

data/spec/tang_app/app/views/devise/mailer/unlock_instructions.html.erb

@@ -0,0 +1,7 @@
+<p>Hello <%= @resource.email %>!</p>
+
+<p>Your account has been locked due to an excessive number of unsuccessful sign in attempts.</p>
+
+<p>Click the link below to unlock your account:</p>
+
+<p><%= link_to 'Unlock my account', unlock_url(@resource, unlock_token: @token) %></p>