browsercms 3.3.4 → 3.4.0.rc1

data/features/generators/content_blocks_for_projects.feature

@@ -0,0 +1,109 @@
+@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
+    """
+

data/features/install_content.feature

@@ -0,0 +1,25 @@
+Feature: Install blank site
+  	As a developer installing BrowserCMS
+	there should be an initial set of starting data
+	so that there is a starting point for creating content.
+
+  Background:
+    Given the cms database is populated
+
+  Scenario: A homepage should exist
+    Given I am on the homepage
+    Then I should see a page titled "Home"
+
+  Scenario: An error page should exist
+    Given I am at /system/server_error
+    Then I should see a page titled "Server Error"
+
+  Scenario: A 404 page should exist
+    Given I am at /system/not_found
+    Then I should see a page titled "Page Not Found"
+
+
+
+
+
+

data/features/jquery-testplan.txt

@@ -0,0 +1,12 @@
+This file contains a manual test plan of areas of BrowserCMS that use Jquery/javascript and need to be tested manually (currently) when stuff is updated.
+Could be better done as a features file, with some additional investment time to automate it.
+
+Features:
+* Check all/Check none - Edit a section, verify the group's can be checked/unchecked using a single button.
+* Drag/Drop - On the sitemap, verify that Pages, Links, Sections can be moved via drag/drop. Refresh page to make sure they 'stick'.
+* Expanding Folders - On the sitemap, verify that sections can be opened/closed.
+* Hover over - On the sitemap, verify that 'hidden' sections can be hovered over and have a popup.
+* Remove Block - On a page, use the [-] to remove a block from the page. Refresh to verify it 'sticks'
+* Path Generator - Add a page, type in name. Verify the 'path' field is being generated based on value.
+* Dropdowns - Edit a page. Verify the 'section' selector works correctly.
+* Taglist - Add an Html Block. Add tags. Verify that it correctly autolooks up tags that exist already.

data/features/manage_groups.feature

@@ -0,0 +1,33 @@
+Feature: Manage Groups
+  CMS Admins should be able to create and manage groups and their permissions through the UI.
+
+  Background:
+    Given the cms database is populated
+    And I am logged in as a Content Editor
+
+  Scenario: Create a new content editor group
+    Given I request /cms/groups
+    Then I should see "List Groups"
+    When I click on "Add Group"
+    Then I should see a page titled "Add New Group"
+    When I fill in "Name" with "Publisher's Group"
+    And I select "CMS User" from "Type of User"
+    And I check "Edit Content"
+    And I check "Publish Content"
+    And I check "My Site"
+    And I press "Save"
+    Then I should see "Publisher's Group"
+    And the new group should have edit and publish permissions
+    And I should see "1 of 2 Sections"
+
+  Scenario: Create Public Group
+    Given I request /cms/groups
+    Then I should see "List Groups"
+    When I click on "Add Group"
+    Then I should see a page titled "Add New Group"
+    When I fill in "Name" with "Authenticated Users"
+    And I select "Registered Public User" from "Type of User"
+    And I press "Save"
+    Then I should see "Authenticated Users"
+    Then I click on "Authenticated Users"
+    And the new group should have neither edit nor publish permissions

data/features/manage_page_routes.feature

@@ -0,0 +1,72 @@
+Feature: Manage Page Routes
+  Admins should be able to see existing Rails routes, as well as add new 'dynamic' routes via the Admin.
+  These routes will be used to handle custom portlet pages (like viewing a single 'News' article) using a
+  nicely formatted path.
+
+  Background:
+    Given the cms database is populated
+    And I am logged in as a Content Editor
+
+  Scenario: Show Rails Routes
+    When I request /cms/routes
+    Then I should see a page titled "Rails Routes"
+
+  Scenario: Match a path to a Controller
+    When I request /cms/routes
+    And I search for a path including "/cms/sample_blocks/1"
+    Then I should see the following content:
+      | {:action=>"show", :controller=>"cms/sample_blocks", :id=>"1"} |
+
+  Scenario: Create Page Route
+    When I request /cms/page_routes
+    Then I should see a page titled "List Page Routes"
+    When I click on "Add"
+    Then I should see a page titled "New Page Route"
+    When create a Page Route with the following:
+      | name     |
+      | my_route |
+    Then I should see a page titled "'my_route' Page Route"
+    And I should see the following content:
+      | my_route |
+
+  Scenario: Edit Page Route
+    Given a Page Route exists
+    When I edit that page route
+    Then I should see a page titled "Edit Page Route"
+    When I fill in "Name" with "My Updated Route"
+    And I click on "Save"
+    Then I should see a page titled "'My Updated Route' Page Route"
+    And I should see "My Updated Route"
+
+  Scenario: A simple route to a CMS page
+    Given a public page exists
+    When there is a portlet that displays ":name" from the route
+    When a page route with the pattern "/hello/:name" exists
+    When I request /hello/World
+    Then I should see "World"
+
+
+  Scenario: Calling a route with valid segment constraints
+    Given there is a dynamic page that looks up content by date
+    And a page route with following exists:
+      | pattern        |
+      | /content/:year |
+    When I request /content/2011
+    Then I should see content for that year only
+
+  Scenario: Calling a route with invalid segment constraints
+    Given there is a dynamic page that looks up content by date
+    And a page route with following exists:
+      | pattern        | constraint |
+      | /content/:year | d{4}       |
+    When I request /content/20
+    Then I should see the CMS 404 page
+
+  Scenario: Calling a route with invalid method
+    Given there is a dynamic page that looks up content by date
+    And a page route with following exists:
+      | pattern        | method |
+      | /content/:year | GET    |
+    When I POST to /content/2011
+    Then I should see the CMS 404 page
+

data/features/manage_redirects.feature

@@ -0,0 +1,20 @@
+Feature: Manage Redirects
+  In order to avoid breaking links to old sites,
+  admins should be able to create redirects between arbitrary paths in the CMS.
+
+  Background:
+    Given the cms database is populated
+    And I am logged in as a Content Editor
+
+  Scenario: Create Redirect
+    When I view the Redirects page
+    Then I should see a page titled "List Redirects"
+    When I click on "Add"
+    Then I should see a page titled "New Redirect"
+    When create a Redirect with the following:
+      | from    | to      |
+      | /path-a | /path-b |
+    Then I should see a page titled "List Redirects"
+    And I should see the following content:
+    | /path-a |
+    | /path-b |

data/features/manage_sections.feature

@@ -0,0 +1,12 @@
+Feature: Manage Sections
+  Content Editors should be able to create sections from the sitemap in order to organize site content.
+
+  Background:
+    Given the cms database is populated
+    And I am logged in as a Content Editor
+
+  Scenario: Create Section
+    Given I am adding a section to the root section
+    When I create a public section
+    Then I should see a page titled "Sitemap"
+    And the new section should be accessible to everyone

data/features/page_templates.feature

@@ -0,0 +1,25 @@
+Feature: Page Templates
+  CMS Administrators should be able to create page and partial templates through the UI.
+
+  Background:
+    Given the cms database is populated
+    And I am logged in as a Content Editor
+
+  Scenario: Add a Page Template
+    When I am at /cms/page_templates
+    And I click on "Add"
+    Then I should see "New Cms/Page Template"
+    When I fill in the following:
+      | Name | hello |
+      | Body | World |
+    And I press "Save"
+    Then I should see a page titled "List Page Templates"
+    Then I should see the following content:
+      | Hello |
+
+  Scenario: Multiple pages of templates
+    Given there are 20 page templates
+    When I am at /cms/page_templates
+    Then I should see "Displaying 1 - 15 of 20"
+    When I click on "next_page_link"
+    Then I should see "Displaying 16 - 20 of 20"

data/features/portlets/email_friend_portlet.feature

@@ -0,0 +1,29 @@
+Feature: Email a Friend Portlet
+  Allows users to email a page to a friend by clicking on a link and filling out a form. An email will be generated with
+  a link to whatever page the portlet is embedded into.
+
+  Background:
+    Given the cms database is populated
+    And I am logged in as a Content Editor
+
+  Scenario: Add New Portlet
+    Given I visit /cms/portlets
+    When I click on "add new content"
+    And I click on "Email Page Portlet"
+    Then I should see a page titled "Add New Portlet"
+    When I fill in "Name" with "Hello"
+    And I click on "Save"
+    Then I should not see "ERROR"
+    Then I should see the following content:
+    | Recipients |
+    | Body       |
+    When I fill in "Recipients" with "test@example.com"
+    And I fill in "Body" with "Testing"
+    And I press "Send Email"
+    Then I should not see the following content:
+    | error |
+
+
+
+
+

data/features/portlets/portlets.feature

@@ -0,0 +1,93 @@
+Feature: Portlets
+  In order to support dynamic content on my site
+  As a content editor
+  I want to be able to dynamically display content.
+
+  Background:
+    Given the cms database is populated
+    And I am logged in as a Content Editor
+
+  Scenario: List Portlets
+    When I visit /cms/portlets
+    Then "Portlets" should be selected as the current Content Type
+
+  Scenario: Login portlet when logged in
+    And there is a LoginPortlet on the homepage
+    And I am on the homepage
+    Then I should see Welcome, cmsadmin
+
+  Scenario: Login portlet when logged out
+    Given there is a LoginPortlet on the homepage
+    And I am not logged in
+    And I am on the homepage
+    Then I should see the following content:
+      | Login       |
+      | Password    |
+      | Remember me |
+
+  Scenario: Viewing a portlet
+    Given there is a "Portlet" with:
+      | name          | template    |
+      | A new portlet | Hello World |
+    When I request /cms/content_library
+    And follow "Portlet"
+    Then I should see the following content:
+      | A new portlet |
+
+  Scenario: Deleting a portlet
+    Given there is a "Portlet" with:
+      | name          | template    |
+      | A new portlet | Hello World |
+    When I delete that portlet
+    And I request /cms/content_library
+    And I click on "Portlet"
+    And I should not see "A new portlet"
+    When I view that portlet
+    Then I should see the following content:
+      | has been deleted |
+
+  Scenario: Editing a portlet
+    Given there is a "Portlet" with:
+      | name          | template    |
+      | A new portlet | Hello World |
+    When I edit that portlet
+    And fill in "Name" with "New Name"
+    And fill in "Template" with "New World"
+    And I click on "Save"
+    Then I should see the following content:
+      | View Portlet 'New Name' |
+      | New World               |
+    And I should not see the following content:
+      | A new portlet |
+      | Hello World   |
+
+  Scenario: Page with portlet on it
+    Given I am not logged in
+    And a page with a portlet that display "Hello World" exists
+    When I visit that page
+    Then I should see the following content:
+      | Hello World |
+
+  Scenario: Portlet throws a 404 Error
+    Given I am not logged in
+    And a page with a portlet that raises a Not Found exception exists
+    When I visit that page
+    Then I should see the CMS 404 page
+
+  Scenario: Portlet throws an 403 Error
+    Given I am not logged in
+    And a page with a portlet that raises an Access Denied exception exists
+    When I visit that page
+    Then I should see the CMS :forbidden page
+
+  Scenario: Portlet throws 404 and 403 errors
+    Given I am not logged in
+    And a page with a portlet that raises both a 404 and 403 error exists
+    When I visit that page
+    Then I should see the CMS 404 page
+
+  Scenario: Portlet throws 403 and any other error
+    Given I am not logged in
+    And a page with a portlet that raises both a 403 and any other error exists
+    When I visit that page
+    Then I should see the CMS :forbidden page