locomotive_cms 2.0.0.rc12 → 2.0.0

data/features/api/pages.feature

@@ -0,0 +1,72 @@
+Feature: Pages
+  In order to access the Page resources
+  As an admin
+  I will perform the basic RESTFUL actions on them
+
+  Background:
+    Given I have the site: "test site" set up
+    And I have an "admin" API token
+    And a page named "hello world" with the template:
+    """
+    Hello world :-)
+    """
+    And a page named "goodbye-world" with the template:
+    """
+    Goodbye world :-(
+    """
+    And I have a custom model named "Projects" with id "4f832c2cb0d86d3f42fffffe" and
+      | label       | type      | required        |
+      | Name        | string    | true            |
+      | Description | text      | false           |
+
+  Scenario: Protect the pages resources if not authenticated
+    Given I do not have an API token
+    When I visit "/locomotive/api/pages.json"
+    Then the JSON response at "error" should be "You need to sign in or sign up before continuing."
+
+  Scenario: Accessing pages
+    When I visit "/locomotive/api/pages.json"
+    Then the JSON should have the following:
+      | 0/fullpath | "index"          |
+      | 1/fullpath | "hello-world"    |
+      | 2/fullpath | "404"            |
+      | 3/fullpath | "goodbye-world"  |
+
+  Scenario: Creating templatized page
+    # "target_entry_name": "projects",
+    When I do an API POST to pages.json with:
+    """
+    {
+      "page": {
+        "title": "My Templatized Page",
+        "templatized": "true",
+        "templatized_from_parent": "false",
+        "target_klass_slug": "projects",
+        "parent_fullpath": "index"
+      }
+    }
+    """
+    When I do an API GET request to pages.json
+    Then the JSON response should be an array
+    And the JSON response should have 5 entries
+    And the JSON response at "4/title" should be "My Templatized Page"
+    And the JSON response at "4/target_klass_slug" should be "projects"
+
+  Scenario: Saving page SEO data
+    Given a page named "yet another page" with id "4f832c2cb0d86d3f42fffffe"
+    And I have an "admin" API token
+    When I do an API PUT to pages/4f832c2cb0d86d3f42fffffe.json with:
+    """
+    {
+      "page": {
+        "seo_title": "Awesome SEO title",
+        "meta_keywords": "keywords,more_keywords,",
+        "meta_description": "It is awesome"
+      }
+    }
+    """
+    When I do an API GET request to pages/4f832c2cb0d86d3f42fffffe.json
+    Then the JSON response should have the following:
+      | seo_title           | "Awesome SEO title"       |
+      | meta_keywords       | "keywords,more_keywords," |
+      | meta_description    | "It is awesome"           |

data/features/backoffice/authorization/account_settings.feature

@@ -0,0 +1,28 @@
+Feature: Account Settings
+  In order to ensure sites are not tampered with
+  As an admin, designer or author
+  I will be restricted based on my role
+
+Background:
+  Given I have the site: "test site" set up
+  And I have a designer and an author
+
+  Scenario: As an unauthenticated user
+    Given I am not authenticated
+    When I go to account settings
+    Then I should see "Log in"
+
+  Scenario: Accessing site settings as an Admin
+    Given I am an authenticated "admin"
+    When I go to account settings
+    Then I should see "new site"
+
+  Scenario: Accessing site settings as a Designer
+    Given I am an authenticated "designer"
+    When I go to account settings
+    Then I should not see "new site"
+
+  Scenario: Accessing site settings as an Author
+    Given I am an authenticated "author"
+    When I go to account settings
+    Then I should not see "new site"

data/features/backoffice/authorization/content_type.feature

@@ -0,0 +1,35 @@
+Feature: Editing a content type
+  In order to edit a content type
+  As an admin, designer, or author
+  I will be restricted based on my role
+
+Background:
+  Given I have the site: "test site" set up
+  And I have a custom model named "Projects" with
+    | label       | type      | required        |
+    | Name        | string    | true            |
+    | Description | text      | false           |
+  And I have a designer and an author
+
+  Scenario: As an unauthenticated user
+    Given I am not authenticated
+    When I go to the "Projects" model edition page
+    Then I should see "Log in"
+
+  Scenario: Accessing edition functionality as an Admin
+    Given I am an authenticated "admin"
+    When I go to the "Projects" model edition page
+    Then I should see "Editing model"
+    And I should see "Custom fields"
+
+  Scenario: Accessing edition functionality as a Designer
+    Given I am an authenticated "designer"
+    When I go to the "Projects" model edition page
+    Then I should see "Editing model"
+    And I should see "Custom fields"
+
+  Scenario: Accessing edition functionality as an Author
+    Given I am an authenticated "author"
+    When I go to the "Projects" model edition page
+    Then I should be on the pages list
+    And I should see the access denied message

data/features/backoffice/authorization/current_site.feature

@@ -0,0 +1,53 @@
+Feature: Site Settings
+  In order to ensure site settings are not tampered with
+  As an admin, designer or author
+  I will be restricted based on my role
+
+Background:
+  Given I have the site: "test site" set up
+  And I have a designer and an author
+
+  Scenario: As an unauthenticated user
+    Given I am not authenticated
+    When I go to site settings
+    Then I should see "Log in"
+
+  @javascript
+  Scenario: Accessing site settings as an Admin
+    Given I am an authenticated "admin"
+    When I go to site settings
+    Then I should see "add account"
+    And I should see "SEO settings"
+    And I should see "Access points"
+    And I should not see the role dropdown on myself
+    And I should see the role dropdown on the "designer"
+    And I should see the role dropdown on the "author"
+    And I should not see delete on myself
+    And I should see delete on the "designer"
+    And I should see delete on the "author"
+
+  @javascript
+  Scenario: Accessing site settings as a Designer
+    Given I am an authenticated "designer"
+    When I go to site settings
+    Then I should not see "add account"
+    And I should see "SEO settings"
+    And I should see "Access points"
+    And I should not see the role dropdown on myself
+    And I should not see the role dropdown on the "admin"
+    And I should see the role dropdown on the "author" without the "Administrator" option
+    And I should not see delete on the "admin"
+    And I should not see delete on myself
+    And I should see delete on the "author"
+
+  @javascript
+  Scenario: Accessing site settings as an Author
+    Given I am an authenticated "author"
+    When I go to site settings
+    Then I should not see "add account"
+    And I should see "SEO settings"
+    And I should not see "Access points"
+    And I should not see "Accounts"
+    # Paranoid Checks
+    And I should not see any role dropdowns
+    And I should not see any delete buttons

data/features/backoffice/authorization/inline_front_end_editing.feature

@@ -0,0 +1,46 @@
+@javascript
+Feature: Inline frontend editing
+  In order to ensure site content is not tampered with
+  As an admin, designer or author
+  I will be restricted based on my role
+
+  Background:
+    Given I have the site: "test site" set up
+    And I have a designer and an author
+    Given a page named "about" with the template:
+    """
+    <html>
+      <head>{% inline_editor %}</head>
+      <body>Page Content</body>
+    </html>
+    """
+
+  Scenario: As an unauthenticated user
+    Given I am not authenticated
+    When I view the rendered page at "/about"
+    Then I should not see "Admin"
+    When I view the rendered page at "/about/_admin"
+    Then I should not see "Editing mode"
+    And I should see "Log in"
+
+  Scenario: Inline editing as an Admin
+    Given I am an authenticated "admin"
+    When I view the rendered page at "/about"
+    Then I should see "Admin"
+    When I view the rendered page at "/about/_admin"
+    Then I should see "Editing mode"
+
+  @javascript
+  Scenario: Inline editing as a Designer
+    Given I am an authenticated "designer"
+    When I view the rendered page at "/about"
+    Then I should see "Admin"
+    When I view the rendered page at "/about/_admin"
+    Then I should see "Editing mode"
+
+  Scenario: Inline editing as an Author
+    Given I am an authenticated "author"
+    When I view the rendered page at "/about"
+    Then I should see "Admin"
+    When I view the rendered page at "/about/_admin"
+    Then I should see "Editing mode"

data/features/backoffice/authorization/pages.feature

@@ -0,0 +1,95 @@
+Feature: Pages
+  In order to ensure pages are not tampered with
+  As an admin, designer or author
+  I will be restricted based on my role
+
+  Background:
+    Given I have the site: "test site" set up
+    And I have a custom model named "Projects" with
+      | label       | type      | required        |
+      | Name        | string    | true            |
+      | Description | text      | false           |
+    And I have a designer and an author
+    And a page named "hello-world" with the template:
+    """
+    Hello World
+    """
+
+  Scenario: As an unauthenticated user
+    Given I am not authenticated
+    When I go to pages
+    Then I should see "Log in"
+
+  # listing pages
+
+  Scenario: Accessing pages as an Admin
+    Given I am an authenticated "admin"
+    When I go to pages
+    Then I should see "new page"
+    And I should see delete page buttons
+    And I should see "new model"
+    And I should see "Projects"
+
+  Scenario: Accessing pages as a Designer
+    Given I am an authenticated "designer"
+    When I go to pages
+    Then I should see "new page"
+    And I should see delete page buttons
+    And I should see "new model"
+    And I should see "Projects"
+
+  Scenario: Accessing pages as an Author
+    Given I am an authenticated "author"
+    When I go to pages
+    Then I should not see "new page"
+    And I should not see delete page buttons
+    And I should not see "new model"
+    And I should see "Projects"
+
+  # new page
+
+  Scenario: Accessing new page as an Admin
+    Given I am an authenticated "admin"
+    When I go to the new page
+    Then I should see "New page"
+
+  Scenario: Accessing new page as a Designer
+    Given I am an authenticated "designer"
+    When I go to the new page
+    Then I should see "New page"
+
+  Scenario: Accessing new page as an Author
+    Given I am an authenticated "author"
+    When I go to the new page
+    Then I should be on the pages list
+    And I should see the access denied message
+
+  # edit page
+
+  Scenario: Accessing edit page as an Admin
+    Given I am an authenticated "admin"
+    When I go to the "hello-world" edition page
+    Then I should see "some title"
+    And I should see "General information"
+    And I should see "SEO settings"
+    And I should see "Advanced options"
+    And I should see "Template"
+
+  Scenario: Accessing edit page as a Designer
+    Given I am an authenticated "designer"
+    When I go to the "hello-world" edition page
+    Then I should see "some title"
+    And I should see "General information"
+    And I should see "SEO settings"
+    And I should see "Advanced options"
+    And I should see "Template"
+
+  Scenario: Accessing edit page as an Author
+    Given I am an authenticated "author"
+    When I go to the "hello-world" edition page
+    Then I should see "some title"
+    And I should not see "General Information"
+    And I should see "SEO settings"
+    And I should not see "Advanced options"
+    And I should not see "Template"
+

data/features/backoffice/authorization/theme_assets.feature

@@ -0,0 +1,50 @@
+Feature: Theme Assets
+  In order to ensure theme assets are not tampered with
+  As an admin, designer or author
+  I will be restricted based on my role
+
+Background:
+  Given I have the site: "test site" set up
+  And I have a designer and an author
+  And I have an image theme asset named "dog.png"
+
+  Scenario: As an unauthenticated user
+    Given I am not authenticated
+    When I go to theme assets
+    Then I should see "Log in"
+
+  @javascript
+  Scenario: Accessing theme assets as an Admin
+    Given I am an authenticated "admin"
+    When I go to theme assets
+    Then I should see "new snippet"
+    And I should see "new file"
+    And I should see "Snippets"
+    And I should see "Style and javascript"
+    And I should see "Images"
+    And I should see "dog.png"
+    And I should see a delete link
+
+  @javascript
+  Scenario: Accessing theme assets as a Designer
+    Given I am an authenticated "designer"
+    When I go to theme assets
+    Then I should see "new snippet"
+    And I should see "new file"
+    And I should see "Snippets"
+    And I should see "Style and javascript"
+    And I should see "Images"
+    And I should see "dog.png"
+    And I should see a delete link
+
+  @javascript
+  Scenario: Accessing theme assets as an Author
+    Given I am an authenticated "author"
+    When I go to theme assets
+    Then I should not see "new snippet"
+    And I should not see "new file"
+    And I should not see "Snippets"
+    And I should not see "Style and javascript"
+    And I should see "Images"
+    And I should see "dog.png"
+    And I should not see a delete link

data/features/backoffice/content_types/edit.feature

@@ -0,0 +1,20 @@
+Feature: Edit the different properties of a content type
+
+Background:
+  Given I have the site: "test site" set up
+  And I have a custom model named "Projects" with
+    | label       | type        | required    | target  |
+    | Name        | string      | true        |         |
+    | Description | text        | false       |         |
+  And I have entries for "Projects" with
+    | name              | description                    |
+    | Fun project       | Description for the fun one    |
+    | Boring project    | Description for the boring one |
+  And I am an authenticated user
+
+@javascript
+Scenario: I remove all notified accounts
+  Given I enable the public submission of the "Projects" model
+  When I go to the "Projects" model edition page
+  And I unselect the notified accounts
+  Then there should not be any notified accounts on the "Projects" model

data/features/backoffice/content_types/has_many.feature

@@ -0,0 +1,60 @@
+Feature: Create and manage has many relationships
+  In order to work with two associated models together
+  As an administrator
+  I want to set up and manage a has many relationship
+
+Background:
+  Given I have the site: "test site" set up
+  And I have a custom model named "Clients" with
+    | label       | type      | required    | target   |
+    | Name        | string    | true        |          |
+    | Description | string    | false       |          |
+  And I have a custom model named "Projects" with
+    | label       | type        | required    | target  |
+    | Name        | string      | true        |         |
+    | Description | text        | false       |         |
+    | Client      | belongs_to  | false       | Clients |
+  And I set up a has_many relationship between "Clients" and "Projects"
+  And I have entries for "Clients" with
+    | name              | description                |
+    | Alpha, Inc        | Description for Alpha, Inc |
+    | Beta, Inc         | Description for Beta, Inc  |
+    | Gamma, Inc        | Description for Gamma, Inc |
+  And I have entries for "Projects" with
+    | name              | description                    |
+    | Fun project       | Description for the fun one    |
+    | Boring project    | Description for the boring one |
+
+  And I am an authenticated user
+
+@javascript
+Scenario: I view a client without any projects
+  When I go to the list of "Clients"
+  And I choose "Alpha, Inc" in the list
+  Then I should see "The list is empty" within the list of entries
+
+@javascript
+Scenario: I add a project to a client
+  When I go to the list of "Projects"
+  And I choose "Fun project" in the list
+  And I select "Alpha, Inc" from "Client"
+  And I press "Save"
+  Then I should see "Entry was successfully updated."
+  When I go to the list of "Clients"
+  And I choose "Alpha, Inc" in the list
+  Then I should see "Fun project" within the list of entries
+
+@javascript
+Scenario: I add a project to a client from the client page
+  When I go to the list of "Clients"
+  And I choose "Beta, Inc" in the list
+  And I follow "+ Add a new entry"
+  Then I should see "Projects — new entry"
+  When I press "Create" within the dialog popup
+  Then I should see "Entry was not created."
+  When I fill in "Name" with "Project X" within the dialog popup
+  And I fill in "Description" with "Lorem ipsum" within the dialog popup
+  And I press "Create" within the dialog popup
+  Then I should see "Entry was successfully created."
+  And I should see "Project X" within the list of entries
+  And "p.empty" should not be visible within the list of entries