browsercms 3.4.2 → 3.5.0.rc1

data/features/commands/upgrading_modules.feature

@@ -1,67 +0,0 @@
-@cli
-Feature: Upgrading BrowserCMS
-  As a developer who has a lot of module to maintain, I really don't want to have to work off a checklist and
-  would rather have an idiot proof script that will upgrade my module for me.
-
-  Background:
-    Given I am working on a BrowserCMS v3.3.x module named "bcms_petstore"
-
-  Scenario: Verify a Rails 3.0 app was created
-    Then the following directories should exist:
-      | script |
-      | app    |
-    And the following files should exist:
-      | config.ru |
-
-  Scenario: Avoid accidentally updating projects
-    Given I cd to ".."
-    And I am working on a BrowserCMS v3.3.x project named "petstore"
-    When I run `bcms-upgrade module`
-    Then the output should contain "This does not appear to be a BrowserCMS module. Skipping update"
-    And the following files should exist:
-      | config.ru |
-
-  Scenario: Upgrade a Module from 3.3.x to 3.4.x
-    When I run `bcms-upgrade module`
-    And the output should not contain "Upgrading to BrowserCMS 3.3.x..."
-    Then the file "script/rails" should contain "test/dummy/script/rails"
-    And the following files should not exist:
-      | config.ru                                 |
-      | MIT-LICENSE                               |
-      | README.rdoc                               |
-      | config/database.yml                       |
-      | app/controllers/application_controller.rb |
-      | app/helpers/application_helper.rb         |
-      | app/views/layouts                         |
-  # Confirm a Rails 3 mountable app was created
-    And the following directories should exist:
-      | app/assets/javascripts |
-      | test/dummy             |
-    And the following directories should not exist:
-      | public |
-    And the file "test/dummy/config/database.yml" should contain "@original-yml"
-    And the file "config/routes.rb" should not contain "@original-routes"
-    And the file "config/routes.rb" should contain "BcmsPetstore::Engine.routes.draw"
-    And the file "lib/bcms_petstore/engine.rb" should contain "require 'browsercms'"
-    And the file "lib/bcms_petstore/engine.rb" should contain "@original-engine"
-    And the file "lib/bcms_petstore/version.rb" should contain "@original-version"
-    And the file "app/assets/test.html" should contain "@original-html"
-    And the file "app/assets/js/test.js" should contain "@original-js"
-    And the file "test/dummy/config/routes.rb" should contain "mount_browsercms"
-    And the following files should not exist:
-      | db/migrate/20080815014337_browsercms_3_0_0.rb |
-      | db/migrate/20091109175123_browsercms_3_0_5.rb |
-      | db/schema.rb                                  |
-      | db/seeds.rb                                   |
-      | db/development.sqlite3                        |
-    And the following files should exist:
-      | db/migrate/my_module_migration.rb |
-    And the file "bcms_petstore.gemspec" should contain "@original-gemspec"
-    And the following files should exist:
-      | test/dummy/db/seeds.rb |
-
-
-
-
-
-

data/features/content_blocks/manage_custom_blocks.feature

@@ -1,67 +0,0 @@
-Feature: Manage Content Blocks
-  In BrowserCMS projects developers should be able to generate and manage content blocks via the UI.
-  This blocks will be generated as Rails resources, with a controller and views.
-
-  Background:
-    Given the cms database is populated
-    And a Content Type named "Product" is registered
-    And I am logged in as a Content Editor
-
-  Scenario: List Content Blocks
-    When I request /cms/products
-    Then I should see "List Products"
-
-  Scenario: List Content Blocks
-    When I request /cms/content_library
-    Then I should see the following content:
-      | Product       |
-      | Text          |
-      | File          |
-      | Image         |
-      | Portlet       |
-      | Category      |
-      | Category Type |
-      | Tag           |
-
-  Scenario: Create a new block
-    When I request /cms/products/new
-    Then I should see "Add New Product"
-    When I fill in "Name" with "iPhone"
-    And I fill in "Price" with "400"
-    And I click on "Save"
-    Then I should see "iPhone"
-    Then I should see "400"
-
-  Scenario: Delete a block
-    Given the following products exist:
-      | id | name        | price |
-      | 1  | iPhone      | 400   |
-      | 2  | Kindle Fire | 200   |
-    When I delete "Kindle Fire"
-    Then I should be redirected to /cms/products
-
-  Scenario: Add to a page
-    When I visit /
-    And I turn on edit mode for /
-    And I add content to the main area of the page
-    And I click on "Product"
-    And I fill in "Name" with "iPhone"
-    And I click on "Save"
-    Then the response should be 200
-    And I should see "Name: iPhone"
-
-  Scenario: View Usages
-    Given a product "iPhone" has been added to a page
-    When I view that product
-    Then the response should be 200
-    And the page header should be "View Product 'iPhone'"
-    And I should see "Used on: 1 page"
-
-
-
-
-
-
-
-
-

data/features/content_blocks/manage_html_blocks.feature

@@ -1,48 +0,0 @@
-Feature: Manage Html Blocks
-  As a content editor I should be able to add new HTML content to a site
-
-  Background:
-    Given the cms database is populated
-    And I am logged in as a Content Editor
-
-  Scenario: List Html Blocks
-    Given the following Html blocks exist:
-      | name      |
-      | Hello CMS |
-    Given I request /cms/html_blocks
-    Then the response should be 200
-    Then "Text" should be selected as the current Content Type
-    And I should see the following content:
-      | Hello CMS     |
-      | Include body? |
-
-  Scenario: Publishing a New Block
-    Given I request /cms/html_blocks/new
-    Then I should see a page titled "Add New Text"
-    When I fill in "Name" with "Hello World"
-    And I click on "Save And Publish"
-    Then I should see a page titled "Content Library / View Text"
-    And I should see the following content:
-      | published               |
-      | View Text 'Hello World' |
-
-  Scenario: Publishing an existing block
-    Given the following Html blocks exist:
-      | id  | name  |
-      | 100 | Hello |
-    When I request /cms/html_blocks/100/edit
-    When I fill in "Name" with "Hello World"
-    And I click on "Save And Publish"
-    Then I should see a page titled "Content Library / View Text"
-    And I should see the following content:
-      | published               |
-      | View Text 'Hello World' |
-
-  Scenario: View Usages
-    Given html with "Hello World" has been added to a page
-    When I view that block
-    Then the response should be 200
-    And the page header should be "View Text"
-    And I should see "Used on: 1 page"
-    
-  

data/features/content_blocks/manage_image_blocks.feature

@@ -1,41 +0,0 @@
-Feature: Manage Image Blocks
-  Content editors should be able to upload images into the content library.
-
-  Background:
-    Given the cms database is populated
-    And I am logged in as a Content Editor
-    And the following images exist:
-      | id  | name               |
-      | 150 | An LOL Cat Picture |
-    Then an image with id "150" should exist
-
-  Scenario: List Images
-    When I visit /cms/image_blocks
-    Then I should see a page titled "Content Library / List Images"
-    And I should see the following content:
-      | An LOL Cat Picture |
-    And I should see the section search filter
-
-
-  Scenario: Add New Image
-    Given I visit /cms/image_blocks/new
-    Then I should see a page titled "Content Library / Add New Image"
-
-  Scenario: Edit an Image
-    When I visit /cms/image_blocks/150/edit
-    Then I should see a page titled "Content Library / Edit Image"
-    And the page header should be "Edit Image 'An LOL Cat Picture'"
-
-  Scenario: Move an Image to another Section
-    And the following sections exist:
-      | name          |
-      | Image Gallery |
-    When I visit /cms/image_blocks/150/edit
-    And I select "Image Gallery" from "Section"
-    And I click on "Save"
-    Then the section 150 should be moved to "Image Gallery"
-
-
-
-
-

data/features/content_files.feature

@@ -1,37 +0,0 @@
-Feature: Content Files
-  The content management system should serve text and other uploaded files.
-
-  Background:
-    Given the cms database is populated
-
-  Scenario: Serve Text Files
-    Given a text file named "/test.txt" exists with:
-    """
-    Test Content
-    """
-    When I request /test.txt
-    Then I should see "Test Content"
-
-  Scenario: Guests viewing protected file
-    Given a protected text file named "/test.txt" exists with:
-    """
-    Test Content
-    """
-    When I request /test.txt
-    Then the response should be 403
-    And I should see a page titled "Access Denied"
-
-  Scenario: Authorized users viewing protected file
-    Given a protected text file named "/test.txt" exists with:
-    """
-    Test Content
-    """
-    When login as an authorized user
-    And I request /test.txt
-    Then the response should be 200
-    And I should see "Test Content"
-
-  Scenario: Guests viewing an Archived file
-    Given an archived file named "/test.txt" exists
-    When I request /test.txt
-    Then I should see the CMS 404 page

data/features/content_pages.feature

@@ -1,21 +0,0 @@
-Feature: Content Pages
-  Visitors should be able to see content pages
-
-  # This should be ported from test/functional/content_controller_test.rbover time.
-
-  Background:
-    Given the cms database is populated
-
-  Scenario: Page Not Found as Guest
-    Given I request /a/non-existent/page
-    Then I should see the CMS 404 page
-
-  Scenario: Viewing an archived page as a Guest
-    Given an archived page at "/an/archived-page" exists
-    When I request /an/archived-page
-    Then I should see the CMS 404 page
-
-  Scenario: A guest accesses a protected page
-    Given a protected page at "/protected-page" exists
-    When I request /protected-page
-    Then I should see the CMS :forbidden page

data/features/generators/content_blocks_for_modules.feature

@@ -1,58 +0,0 @@
-@cli
-Feature: Generate Content Blocks
-  Developers should be able to generate content blocks within projects to define new data structures.
-
-  Background:
-    Given I create a module named "bcms_widgets"
-    When I cd into the project "bcms_widgets"
-
-  Scenario: Generate content block in a module
-    When I run `rails g cms:content_block product name:string price:string`
-    And the file "app/models/bcms_widgets/product.rb" should contain:
-    """
-    module BcmsWidgets
-      class Product < ActiveRecord::Base
-        acts_as_content_block
-      end
-    end
-    """
-    And the file "app/controllers/bcms_widgets/products_controller.rb" should contain:
-    """
-    module BcmsWidgets
-      class ProductsController < Cms::ContentBlockController
-      end
-    end
-    """
-    And the file "app/views/bcms_widgets/products/render.html.erb" should contain:
-    """
-    <p><b>Name:</b> <%= @content_block.name %></p>
-    <p><b>Price:</b> <%= @content_block.price %></p>
-    """
-    And a migration named "create_bcms_widgets_products.rb" should contain:
-        """
-        class CreateBcmsWidgetsProducts < ActiveRecord::Migration
-          def change
-            Cms::ContentType.create!(:name => "BcmsWidgets::Product", :group_name => "BcmsWidgets")
-            create_content_table :bcms_widgets_products, :prefix=>false do |t|
-              t.string :name
-              t.string :price
-
-              t.timestamps
-            end
-          end
-        end
-        """
-    And the file "config/routes.rb" should contain:
-    """
-    BcmsWidgets::Engine.routes.draw do
-      content_blocks :products
-
-    end
-    """
-
-
-
-
-
-
-

data/features/generators/content_blocks_for_projects.feature

@@ -1,109 +0,0 @@
-@cli
-Feature:
-  Developers working in BrowserCMS projects should be able to generate blocks.
-
-  Background:
-    Given a BrowserCMS project named "petstore" exists
-    And I cd into the project "petstore"
-
-  Scenario: Create an content block for a project
-    When I run `rails g cms:content_block product name:string price:string`
-    And the file "app/models/product.rb" should contain:
-    """
-    class Product < ActiveRecord::Base
-      acts_as_content_block
-    end
-    """
-    And a file named "test/unit/product_test.rb" should exist
-    And the file "app/controllers/cms/products_controller.rb" should contain:
-    """
-    class Cms::ProductsController < Cms::ContentBlockController
-    end
-    """
-    And the file "app/views/cms/products/render.html.erb" should contain:
-    """
-    <p><b>Name:</b> <%= @content_block.name %></p>
-    <p><b>Price:</b> <%= @content_block.price %></p>
-    """
-    And a migration named "create_products.rb" should contain:
-    """
-    class CreateProducts < ActiveRecord::Migration
-      def change
-        Cms::ContentType.create!(:name => "Product", :group_name => "Product")
-        create_content_table :products, :prefix=>false do |t|
-          t.string :name
-          t.string :price
-
-          t.timestamps
-        end
-      end
-    end
-    """
-    And the file "config/routes.rb" should contain:
-    """
-    Petstore::Application.routes.draw do
-      namespace :cms  do content_blocks :products end
-
-      mount_browsercms
-    """
-
-  Scenario: With Belongs To
-    When I run `rails g cms:content_block product size:belongs_to`
-    Then the file "app/models/product.rb" should contain:
-    """
-    class Product < ActiveRecord::Base
-      acts_as_content_block
-      belongs_to :size
-    end
-    """
-    And a migration named "create_products.rb" should contain:
-    """
-    t.belongs_to :size
-    """
-
-  Scenario: With Categories
-    When I run `rails g cms:content_block product category:category`
-    Then the file "app/models/product.rb" should contain:
-    """
-    class Product < ActiveRecord::Base
-      acts_as_content_block
-      belongs_to_category
-    end
-    """
-    And a migration named "create_products.rb" should contain:
-    """
-    t.belongs_to :category
-    """
-
-  Scenario: With Attachments
-    When I run `rails g cms:content_block product attachment:attachment`
-    Then the file "app/models/product.rb" should contain:
-    """
-    class Product < ActiveRecord::Base
-      acts_as_content_block :belongs_to_attachment => true
-    end
-    """
-    And a migration named "create_products.rb" should contain the following:
-      | t.belongs_to :attachment      |
-      | t.integer :attachment_version |
-
-  Scenario: With Html attributes
-    When I run `rails g cms:content_block product content:html`
-    Then a migration named "create_products.rb" should contain the following:
-      | t.text :content, :size => (64.kilobytes + 1) |
-
-  Scenario: [Bug Fix] Block names starting with 'do' should work
-    When I run `rails g cms:content_block dog`
-    And a migration named "create_dogs.rb" should contain:
-    """
-    class CreateDogs < ActiveRecord::Migration
-      def change
-        Cms::ContentType.create!(:name => "Dog", :group_name => "Dog")
-        create_content_table :dogs, :prefix=>false do |t|
-
-          t.timestamps
-        end
-      end
-    end
-    """
-