administer 0.2.2 → 0.3.0

data/spec/rails_root/db/migrate/20110104100347_add_publish_on_to_post.rb

@@ -0,0 +1,9 @@
+class AddPublishOnToPost < ActiveRecord::Migration
+  def self.up
+    add_column :posts, :publish_on, :date
+  end
+
+  def self.down
+    remove_column :posts, :publish_on
+  end
+end

data/spec/rails_root/db/migrate/20110214190645_add_category_to_post.rb

@@ -0,0 +1,9 @@
+class AddCategoryToPost < ActiveRecord::Migration
+  def self.up
+    add_column :posts, :category_id, :integer
+  end
+
+  def self.down
+    remove_column :posts, :category_id, :integer
+  end
+end

data/spec/rails_root/db/migrate/20110609184125_create_comments.rb

@@ -0,0 +1,13 @@
+class CreateComments < ActiveRecord::Migration
+  def self.up
+    create_table :comments do |t|
+      t.text :body
+      t.integer :post_id
+      t.timestamps
+    end
+  end
+
+  def self.down
+    drop_table :comments
+  end
+end

data/spec/rails_root/db/migrate/20110628215407_create_attachments.rb

@@ -0,0 +1,13 @@
+class CreateAttachments < ActiveRecord::Migration
+  def self.up
+    create_table :attachments do |t|
+      t.integer :post_id
+      t.text :content
+      t.timestamps
+    end
+  end
+
+  def self.down
+    drop_table :attachments
+  end
+end

data/spec/rails_root/db/schema.rb

@@ -0,0 +1,44 @@
+# This file is auto-generated from the current state of the database. Instead
+# of editing this file, please use the migrations feature of Active Record to
+# incrementally modify your database, and then regenerate this schema definition.
+#
+# Note that this schema.rb definition is the authoritative source for your
+# database schema. If you need to create the application database on another
+# system, you should be using db:schema:load, not running all the migrations
+# from scratch. The latter is a flawed and unsustainable approach (the more migrations
+# you'll amass, the slower it'll run and the greater likelihood for issues).
+#
+# It's strongly recommended to check this file into your version control system.
+
+ActiveRecord::Schema.define(:version => 20110628215407) do
+
+  create_table "attachments", :force => true do |t|
+    t.integer  "post_id"
+    t.text     "content"
+    t.datetime "created_at"
+    t.datetime "updated_at"
+  end
+
+  create_table "categories", :force => true do |t|
+    t.string   "name"
+    t.datetime "created_at"
+    t.datetime "updated_at"
+  end
+
+  create_table "comments", :force => true do |t|
+    t.text     "body"
+    t.integer  "post_id"
+    t.datetime "created_at"
+    t.datetime "updated_at"
+  end
+
+  create_table "posts", :force => true do |t|
+    t.string   "title"
+    t.text     "body"
+    t.datetime "created_at"
+    t.datetime "updated_at"
+    t.date     "publish_on"
+    t.integer  "category_id"
+  end
+
+end

data/spec/rails_root/features/administer/dashboard.feature

@@ -0,0 +1,15 @@
+Feature: Dashboard
+  In order to administer the blog
+  I want to use administration dashboard
+
+  Scenario: Viewing Dashboard page
+    When I am on the administer dashboard page
+    Then I should see "Administer Dashboard"
+    And I should see "Models:"
+    And I should see "Posts" within "ul.administer_model_list"
+    And I should see "Categories" within "ul.administer_model_list"
+    
+  Scenario: Link to application home page
+    When I am on the administer dashboard page
+    And I follow "Go to application"
+    Then I should be on the home page

data/spec/rails_root/features/administer/posts.feature

@@ -0,0 +1,72 @@
+Feature: Managing posts via administer
+  In order to make sure administer works
+  I want to be able to manage posts via administer
+
+  Scenario: Listing posts
+    Given following posts exists:
+      | title                   | body                      |
+      | How to raise your kid   | You should be good parent |
+    When I am on the administer dashboard page
+    And I follow "Posts"
+    Then I should see "How to raise your kid"
+    And I should see "You should be good parent"
+
+  Scenario: Creating posts
+    Given following categories exist:
+      | name          |
+      | Awesome Posts |
+    Given following comments exist:
+      | body          |
+      | First comment |
+      | What is this? |
+    When I am on administer posts list
+    And I follow "New Post"
+    Then I should see textfield with label "Title"
+    And I should see textarea with label "Body"
+    And I should see dateselect with label "Publish on"
+    And I should see select with label "Category"
+    And I should see checkbox with label "First comment"
+    And I should see checkbox with label "What is this"
+    And I fill in "Title" with "How to raise your kid"
+    And I fill in "Body" with "You should be good parent."
+    And I select "Awesome Posts" from "Category"
+    And I check "First comment"
+    And I press "Create Post"
+    Then I should be on administer posts list
+    And following posts should exist:
+      | title                   | body                        | category_name   | comments      |
+      | How to raise your kid   | You should be good parent.  | Awesome Posts   | First comment |
+
+  Scenario: Creating invalid post
+    Given following categories exist:
+      | name          |
+      | Awesome Posts |
+    When I am on administer posts list
+    And I follow "New Post"
+    Then I fill in "Body" with "Post without title"
+    And I press "Create Post"
+    Then I should see "can't be blank"
+    And there should be no posts
+
+  Scenario: Editing Posts
+    Given following posts exists:
+      | title                   | body                      |
+      | How to raise your kid   | You should be good parent |
+    When I am on administer posts list
+    And I follow "Edit"
+    Then I fill in "Title" with "Can we?"
+    And I fill in "Body" with "Yes, we can"
+    And I press "Update Post"
+    Then I should be on administer posts list
+    And following posts should exist:
+      | title     | body        |
+      | Can we?   | Yes, we can |
+
+  Scenario: Deleting post
+    Given following posts exists:
+      | title                   | body                      |
+      | How to raise your kid   | You should be good parent |
+    When I am on administer posts list
+    And I press "Delete"
+    Then I should be on administer posts list
+    And there should be no posts

data/spec/rails_root/features/listing_posts.feature

@@ -0,0 +1,15 @@
+Feature: Listing Posts
+  In order to read blog
+  As a blog guest
+  I want to be able to list posts
+
+  Scenario: List all blog posts
+    Given following posts exists:
+      | title                   | body                      |
+      | How to raise your kid   | You should be good parent |
+      | How to make great coffe | Add whipped cream to it   |
+    When I am on the home page
+    Then I should see "How to raise your kid"
+    And I should see "You should be good parent"
+    And I should see "How to make great coffe"
+    And I should see "Add whipped cream to it"

data/spec/rails_root/features/managing_posts.feature

@@ -0,0 +1,70 @@
+Feature: Managing posts
+  In order to manage my blog
+  As a blog owner
+  I want to be able to manage posts
+
+  Scenario: Adding new blog post
+    Given no posts exist
+    When I am on the home page
+    And I follow "new post"
+    And I fill in "Title" with "How to disassemble atomic bomb?"
+    And I fill in "Body" with "You should avoid using fork for that."
+    And I press "Create Post"
+    Then I should be on posts list
+    And I should see "How to disassemble atomic bomb?"
+    And I should see "You should avoid using fork for that."
+  
+  Scenario: Adding new blog post without title
+    Given no posts exist
+    When I am on the home page
+    And I follow "new post"
+    And I fill in "Body" with "You should avoid using fork for that."
+    And I press "Create Post"
+    Then I should see "Title can't be blank"
+    And there should be no posts
+    
+  Scenario: Adding new blog post without body
+    Given no posts exist
+    When I am on the home page
+    And I follow "new post"
+    And I fill in "Title" with "How to disassemble atomic bomb?"
+    And I press "Create Post"
+    Then I should see "Body can't be blank"
+    And there should be no posts
+    
+  @javascript
+  Scenario: Deleting blog post
+    Given following posts exists:
+      | title                   | body                      |
+      | How to raise your kid   | You should be good parent |
+    When I am on the home page
+    Then I should see "How to raise your kid"
+    When I press "delete" and confirm
+    Then I should be on posts list
+    And I should not see "How to raise your kid"
+  
+  @javascript
+  Scenario: Cancel deleting blog post
+    Given following posts exists:
+      | title                   | body                      |
+      | How to raise your kid   | You should be good parent |
+    When I am on the home page
+    Then I should see "How to raise your kid"
+    When I press "delete" and not confirm
+    Then I should be on the home page
+    And I should see "How to raise your kid"
+
+  Scenario: Editing blog post
+    Given following posts exists:
+      | title                   | body                      |
+      | How to raise your kid   | You should be good parent |
+    When I am on the home page
+    Then I should see "How to raise your kid"
+    When I follow "edit"
+    And I fill in "Title" with "What do you want to do today?"
+    And I fill in "Body" with "Every god damn thing"
+    And I press "Update"
+    Then I should be on posts list
+    And I should see "What do you want to do today"
+    And I should see "Every god damn thing"
+  

data/spec/rails_root/features/step_definitions/categories_steps.rb

@@ -0,0 +1,6 @@
+Given /^following categories exist:$/ do |categories_table|
+  Category.destroy_all
+  categories_table.hashes.each do |attributes|
+    Factory(:category, attributes)
+  end
+end

data/spec/rails_root/features/step_definitions/comments_steps.rb

@@ -0,0 +1,6 @@
+Given /^following comments exist:$/ do |comments_table|
+  Comment.destroy_all
+  comments_table.hashes.each do |attributes|
+    Factory(:comment, attributes)
+  end
+end

data/spec/rails_root/features/step_definitions/post_steps.rb

@@ -8,3 +8,24 @@ Given /^following posts exists:$/ do |posts_table|
     Factory(:post, attributes)
   end
 end
+
+Then /^there should be no posts$/ do
+  Post.all.should be_empty
+end
+
+Then /^following posts should exist:$/ do |posts_table|
+  posts_table.hashes.each do |attributes|
+    category = attributes.delete("category_name")
+    comments = attributes.delete("comments").try(:split, ";")
+    post = Post.first(:conditions => attributes)
+    post.should_not be_nil
+    post.category.name.should == category if category
+    if comments.present?
+      post_comments_mapped = post.comments.map(&:body)
+      comments.all? { |c| post_comments_mapped.should include(c) }
+    end
+  end
+end
+
+
+

data/spec/rails_root/features/step_definitions/web_steps.rb

@@ -104,6 +104,10 @@ Then /^(?:|I )should see JSON:$/ do |expected_json|
   expected.should == actual
 end
 
+Then /^(?:|I )should see (.*) with label "([^"]*)"$/ do |fieldtype, label|
+  page.should send("have_#{fieldtype}".to_sym, label)
+end
+
 Then /^(?:|I )should see "([^"]*)"(?: within "([^"]*)")?$/ do |text, selector|
   with_scope(selector) do
     if page.respond_to? :should
@@ -193,7 +197,7 @@ Then /^the "([^"]*)" checkbox(?: within "([^"]*)")? should not be checked$/ do |
 end
  
 Then /^(?:|I )should be on (.+)$/ do |page_name|
-  current_path = URI.parse(current_url).path
+  current_path = URI.parse(current_url).request_uri
   if current_path.respond_to? :should
     current_path.should == path_to(page_name)
   else
@@ -227,4 +231,3 @@ Then /^(?:|I )press "([^"]*)" and not confirm$/ do |button|
   page.evaluate_script("window.confirm = function(msg) { return false; }")
   When %{I press "#{button}"}
 end
-

data/spec/rails_root/features/support/env.rb

@@ -4,61 +4,47 @@
 # instead of editing this one. Cucumber will automatically load all features/**/*.rb
 # files.
 
-ENV["RAILS_ENV"] ||= "test"
-require File.expand_path(File.dirname(__FILE__) + '/../../config/environment')
+require 'cucumber/rails'
 
-require 'cucumber/formatter/unicode' # Remove this line if you don't want Cucumber Unicode support
-require 'cucumber/rails/rspec'
-require 'cucumber/rails/world'
-require 'cucumber/rails/active_record'
-require 'cucumber/web/tableish'
-
-require 'capybara/rails'
-require 'capybara/cucumber'
-require 'capybara/session'
-# require 'cucumber/rails/capybara_javascript_emulation' # Lets you click links with onclick javascript handlers without using @culerity or @javascript
 # Capybara defaults to XPath selectors rather than Webrat's default of CSS3. In
 # order to ease the transition to Capybara we set the default here. If you'd
 # prefer to use XPath just remove this line and adjust any selectors in your
 # steps to use the XPath syntax.
 Capybara.default_selector = :css
-Capybara.javascript_driver = :selenium
-Capybara.ignore_hidden_elements = true
 
-# If you set this to false, any error raised from within your app will bubble 
-# up to your step definition and out to cucumber unless you catch it somewhere
-# on the way. You can make Rails rescue errors and render error pages on a
-# per-scenario basis by tagging a scenario or feature with the @allow-rescue tag.
+# By default, any exception happening in your Rails application will bubble up
+# to Cucumber so that your scenario will fail. This is a different from how 
+# your application behaves in the production environment, where an error page will 
+# be rendered instead.
 #
-# If you set this to true, Rails will rescue all errors and render error
-# pages, more or less in the same way your application would behave in the
-# default production environment. It's not recommended to do this for all
-# of your scenarios, as this makes it hard to discover errors in your application.
-ActionController::Base.allow_rescue = false
-
-# If you set this to true, each scenario will run in a database transaction.
-# You can still turn off transactions on a per-scenario basis, simply tagging 
-# a feature or scenario with the @no-txn tag. If you are using Capybara,
-# tagging with @culerity or @javascript will also turn transactions off.
+# Sometimes we want to override this default behaviour and allow Rails to rescue
+# exceptions and display an error page (just like when the app is running in production).
+# Typical scenarios where you want to do this is when you test your error pages.
+# There are two ways to allow Rails to rescue exceptions:
 #
-# If you set this to false, transactions will be off for all scenarios,
-# regardless of whether you use @no-txn or not.
+# 1) Tag your scenario (or feature) with @allow-rescue
 #
-# Beware that turning transactions off will leave data in your database 
-# after each scenario, which can lead to hard-to-debug failures in 
-# subsequent scenarios. If you do this, we recommend you create a Before
-# block that will explicitly put your database in a known state.
-Cucumber::Rails::World.use_transactional_fixtures = true
-# How to clean your database when transactions are turned off. See
-# http://github.com/bmabey/database_cleaner for more info.
-if defined?(ActiveRecord::Base)
-  begin
-    require 'database_cleaner'
-    DatabaseCleaner.strategy = :truncation
-  rescue LoadError => ignore_if_database_cleaner_not_present
-  end
+# 2) Set the value below to true. Beware that doing this globally is not
+# recommended as it will mask a lot of errors for you!
+#
+ActionController::Base.allow_rescue = false
+
+# Remove/comment out the lines below if your app doesn't have a database.
+# For some databases (like MongoDB and CouchDB) you may need to use :truncation instead.
+begin
+  DatabaseCleaner.strategy = :transaction
+rescue NameError
+  raise "You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it."
 end
 
-# factory_girl setup
-require 'factory_girl'
-Dir["#{File.dirname(__FILE__)}/../../spec/factories/*.rb"].each {|f| require f}
+# You may also want to configure DatabaseCleaner to use different strategies for certain features and scenarios.
+# See the DatabaseCleaner documentation for details. Example:
+#
+#   Before('@no-txn,@selenium,@culerity,@celerity,@javascript') do
+#     DatabaseCleaner.strategy = :truncation, {:except => %w[widgets]}
+#   end
+#
+#   Before('~@no-txn', '~@selenium', '~@culerity', '~@celerity', '~@javascript') do
+#     DatabaseCleaner.strategy = :transaction
+#   end
+#

data/spec/rails_root/features/support/factory_girl.rb

@@ -0,0 +1,2 @@
+require 'factory_girl'
+Dir["#{File.dirname(__FILE__)}/../../../factories/*.rb"].each { |f| require f }

data/spec/rails_root/features/support/matchers.rb

@@ -0,0 +1,55 @@
+class Capybara::Session
+  def has_textfield?(locator)
+    find_field(:textfield, locator)
+  end
+
+  def has_textarea?(locator)
+    find_field(:textarea, locator)
+  end
+
+  def has_select?(locator)
+    find_field(:select, locator)
+  end
+
+  def has_dateselect?(locator)
+    id_prefix = find(:xpath, XPath::HTML.label(locator))[:for]
+    year = find_field(:select, "#{id_prefix}_1i")
+    month = find_field(:select, "#{id_prefix}_2i")
+    day = find_field(:select, "#{id_prefix}_3i")
+    year && month && day
+  end
+
+  def has_checkbox?(locator)
+    find_field(:checkbox, locator)
+  end
+
+  def find_field(type, locator)
+    all(:xpath, XPath::HTML.field_of_type(type, locator)).present?
+  end
+end
+
+module XPath::HTML
+  def self.field_of_type(type, locator)
+    xpath = fieldtype_to_xpath(type)
+    xpath = locate_field(xpath, locator)
+    xpath
+  end
+
+  def self.label(label)
+    anywhere(:label)[string.n.is(label)]
+  end
+
+  private
+  def self.fieldtype_to_xpath(type)
+    case type
+    when :textfield
+      descendant(:input)[~attr(:type).one_of('submit', 'image', 'radio', 'checkbox', 'hidden', 'file')]
+    when :checkbox
+      descendant(:input)[attr(:type) == 'checkbox']
+    when :textarea
+      descendant(:textarea)
+    when :select
+      descendant(:select)
+    end
+  end
+end