RubyGems - locomotivecms - Versions diffs - 3.0.0.pre.alpha - Mend

locomotivecms 3.0.0.pre.alpha

Files changed (906) hide show

data/features/public/new_contact_form.feature ADDED Viewed

@@ -0,0 +1,95 @@
+Feature: Contact form [New way]
+  As a visitor
+  In order to keep in touch with the site
+  I want to be able to send them a message
+  Background:
+    Given I enable the CSRF protection for public submission requests
+    Given I have the site: "test site" set up
+    And I have a custom model named "Messages" with
+      | label       | type      | required    |
+      | Email       | string    | true        |
+      | Message     | text      | true        |
+      | Category    | select    | true        |
+    And I have "Design, Code, Business" as "Category" values of the "Messages" model
+    And I enable the public submission of the "Messages" model
+    And a page named "contact" with the template:
+      """
+      <html>
+        <head></head>
+        <body>
+          {% if message %}Thanks {{ message.email }}{% endif %}
+          {% model_form "messages" %}
+            <label for="email">E-Mail Address</label>
+            <input type="text" id="email" name="content[email]" />
+            {% if message.errors.email %}Email is required{% endif %}
+            <label for="category">Category</label>
+            <select id="category" name="content[category]">
+              <option value=""></option>
+              {% for name in contents.messages.category_options %}
+              <option value="{{ name }}">{{ name }}</option>
+              {% endfor %}
+            </select>
+            <label for="message">Message</label>
+            <textarea name="content[message]" id="message"></textarea>
+            <input name="submit" type="submit" id="submit" value="Submit" />
+          {% endmodel_form %}
+        </body>
+      </html>
+      """
+    And a page named "contact_with_redirection" with the template:
+      """
+      <html>
+        <head></head>
+        <body>
+          {% model_form "messages", success: "/success" %}
+            <label for="email">E-Mail Address</label>
+            <input type="text" id="email" name="content[email]" />
+            {% if message.errors.email %}Email is required{% endif %}
+            <label for="category">Category</label>
+            <select id="category" name="content[category]">
+              <option value=""></option>
+              {% for name in contents.messages.category_options %}
+              <option value="{{ name }}">{{ name }}</option>
+              {% endfor %}
+            </select>
+            <label for="message">Message</label>
+            <textarea name="content[message]" id="message"></textarea>
+            <input name="submit" type="submit" id="submit" value="Submit" />
+          {% endmodel_form %}
+        </body>
+      </html>
+      """
+    And a page named "success" with the template:
+      """
+      Thanks {{ message.email }}!
+      """
+  Scenario: Use the url of the current page for the contact form
+    When I view the rendered page at "/contact"
+    Then the rendered output should look like:
+      """
+      <form method="POST" enctype="multipart/form-data">
+      """
+  Scenario: Sending a message with success
+    When I view the rendered page at "/contact"
+    And I fill in "E-Mail Address" with "did@locomotivecms.com"
+    And I fill in "Message" with "LocomotiveCMS rocks"
+    And I select "Code" from "Category"
+    And I press "Submit"
+    Then I should see "Thanks did@locomotivecms.com"
+  Scenario: Display errors
+    When I view the rendered page at "/contact"
+    And I fill in "Message" with "LocomotiveCMS rocks"
+    And I press "Submit"
+    Then I should see "Email is required"
+  Scenario: Redirection after success
+    When I view the rendered page at "/contact_with_redirection"
+    And I fill in "E-Mail Address" with "estelle@locomotivecms.com"
+    And I fill in "Message" with "LocomotiveCMS rocks"
+    And I select "Code" from "Category"
+    And I press "Submit"
+    Then I should see "Thanks estelle@locomotivecms.com!"

data/features/public/pages.feature ADDED Viewed

@@ -0,0 +1,116 @@
+Feature: Pages
+  As a designer
+  In order to improve my site navigation
+  I want to list its pages
+Background:
+  Given I have the site: "test site" set up with name: "test site"
+Scenario: List all of them
+  Given a page named "all" with the template:
+    """
+    {% for page in site.pages %}{{ page.title }}, {% endfor %}
+    """
+  When I view the rendered page at "/all"
+  Then the rendered output should look like:
+    """
+    Home page, Page not found, All,
+    """
+Scenario: Scoped listing
+  Given a page named "hidden-page" with the template:
+    """
+    Hidden content
+    """
+  And the page "hidden-page" is unpublished
+  And a page named "hidden-pages" with the template:
+    """
+    {% with_scope published: false %}
+      {% for page in site.pages %}{{ page.slug }}, {% endfor %}
+    {% endwith_scope %}
+    """
+  When I view the rendered page at "/hidden-pages"
+  Then the rendered output should look like:
+    """
+    hidden-page,
+    """
+Scenario: link_to tag
+  Given the site "test site" has locales "en, es"
+  And a page named "about-us" with the handle "about-us"
+  And the page named "about-us" has the title "Acerca de" in the "es" locale
+  And a page named "page-with-links" with the template:
+    """
+    {% locale_switcher %}
+    {% link_to about-us %}
+    {% link_to about-us, locale: es %}
+    {% link_to about-us %}
+      <i class="icon-info-sign"></i> {{ target.title }}
+    {% endlink_to %}
+    """
+  And the page named "page-with-links" has the title "Página con links" in the "es" locale
+  When I view the rendered page at "/page-with-links"
+  Then the rendered output should look like:
+    """
+    <a href="/about-us">About us</a>
+    <a href="/es/acerca-de">Acerca de</a>
+    <a href="/about-us">
+      <i class="icon-info-sign"></i> About us
+    </a>
+    """
+  When I follow "es"
+  Then the rendered output should look like:
+    """
+    <a href="/es/acerca-de">Acerca de</a>
+    <a href="/es/acerca-de">Acerca de</a>
+    <a href="/es/acerca-de">
+      <i class="icon-info-sign"></i> Acerca de
+    </a>
+    """
+Scenario: link_to templatized page
+  Given I have a custom model named "Articles" with
+      | label       | type      | required    |
+      | Title       | string    | true        |
+  And I have entries for "Articles" with
+    | title             |
+    | Hello world       |
+  And a templatized page for the "Articles" model and with the template:
+    """
+    Here is the title: "{{ article.title }}"
+    """
+  And a page named "page-with-links" with the template:
+    """
+    {% for article in contents.articles %}
+      Link to article: {% link_to article %}
+    {% endfor %}
+    """
+  When I view the rendered page at "/page-with-links"
+  And I follow "Hello world"
+  Then the rendered output should look like:
+  """
+  Here is the title: "Hello world"
+  """
+Scenario: Default locale fallback
+  Given the site "test site" has locales "en, es"
+  And a page named "only-english" with the template:
+    """
+    Only english, please
+    """
+  When I view the rendered page at "/es/only-english"
+  Then I should see "Only english, please"
+Scenario: fetch_page tag
+  Given a page named "print-the-slug-of-a-page" with the template:
+    """
+    {% fetch_page this-is-the-page-handle as my_page %}
+    {{ my_page.slug }}
+    """
+  And a page named "this-is-the-slug" with the handle "this-is-the-page-handle"
+  When I view the rendered page at "/print-the-slug-of-a-page"
+  Then the rendered output should look like:
+    """
+    this-is-the-slug
+    """

data/features/public/pagination.feature ADDED Viewed

@@ -0,0 +1,8 @@
+Feature: Pagination
+  As a designer
+  In order to display a sensible amount of items per page
+  I want to be able to paginate through models
+  Scenario: Paginating through a model
+    Given I have a site set up
+    Then I should be able to display paginated models

data/features/public/robots.feature ADDED Viewed

@@ -0,0 +1,22 @@
+Feature: Robots
+  As a designer
+  I want to be able to define a robots.txt file for my site
+Background:
+  Given I have the site: "test site" set up
+Scenario: Simple robots text
+  Given a robot_txt set to "robots text value"
+  When I view the rendered page at "/robots.txt"
+  Then the rendered output should look like:
+    """
+    robots text value
+    """
+Scenario: Robots.txt should provide access to request_host and all other liquid variables
+  Given a robot_txt set to "host: {{request_host}} path: {{path}}"
+  When I view the rendered page at "/robots.txt"
+  Then the rendered output should look like:
+    """
+    host: test.example.com path: /robots.txt
+    """

data/features/public/session.feature ADDED Viewed

@@ -0,0 +1,40 @@
+Feature: Session
+  As a designer
+  I want to record objects in the session and reach them later
+Background:
+  Given I have the site: "test site" set up
+  And a page named "store" with the template:
+    """
+    Store a string in the session. {% session_assign foo = 'monkey' %}
+    """
+  And a page named "retrieve" with the template:
+    """
+    Retrieve a string from the session: {{ session.foo }}.
+    """
+  And a page named "release" with the template:
+    """
+    Remove a string from the session. {% session_assign foo = null %}
+    """
+Scenario: Store and retrieve a string in session
+  When I view the rendered page at "/retrieve"
+  Then the rendered output should look like:
+    """
+    Retrieve a string from the session: .
+    """
+  When I view the rendered page at "/store"
+  And I view the rendered page at "/retrieve"
+  Then the rendered output should look like:
+    """
+    Retrieve a string from the session: monkey.
+    """
+Scenario: Remove a object from the session
+  When I view the rendered page at "/store"
+  And I view the rendered page at "/release"
+  And I view the rendered page at "/retrieve"
+  Then the rendered output should look like:
+    """
+    Retrieve a string from the session: .
+    """

data/features/public/sitemap.feature ADDED Viewed

@@ -0,0 +1,74 @@
+Feature: Sitemap
+  As a designer
+  I want to have an automatically generated sitemap
+Background:
+  Given I have the site: "test site" set up
+Scenario: Simple sitemap
+  Given a page named "about" with the template:
+    """
+    <html>
+      <body>About us</body>
+    </html>
+    """
+  When I go to the sitemap
+  Then the response status should be 200
+  And I should see the following xml output:
+    """
+    <?xml version="1.0" encoding="UTF-8"?>
+    <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+      <url>
+        <loc>http://test.example.com:9886</loc>
+        <priority>1.0</priority>
+      </url>
+      <url>
+        <loc>http://test.example.com:9886/about</loc>
+        <lastmod>:now</lastmod>
+        <priority>0.9</priority>
+      </url>
+    </urlset>
+    """
+Scenario: Templatized page
+  Given I have a custom model named "Articles" with
+      | label       | type      | required    |
+      | Title       | string    | true        |
+      | Body        | text      | true        |
+  And I have entries for "Articles" with
+    | title             | body                    |
+    | Hello world       | Lorem ipsum             |
+    | Lorem ipsum       | Lorem ipsum...          |
+  And a templatized page for the "Articles" model and with the template:
+    """
+    <html>
+      <body>Template for an article</body>
+    </html>
+    """
+  When I go to the sitemap
+  Then the response status should be 200
+  And I should see the following xml output:
+    """
+    <?xml version="1.0" encoding="UTF-8"?>
+    <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
+      <url>
+        <loc>http://test.example.com:9886</loc>
+        <priority>1.0</priority>
+      </url>
+      <url>
+        <loc>http://test.example.com:9886/articles</loc>
+        <lastmod>:now</lastmod>
+        <priority>0.9</priority>
+      </url>
+      <url>
+        <loc>http://test.example.com:9886/articles/hello-world</loc>
+        <lastmod>:now</lastmod>
+        <priority>0.9</priority>
+      </url>
+      <url>
+        <loc>http://test.example.com:9886/articles/lorem-ipsum</loc>
+        <lastmod>:now</lastmod>
+        <priority>0.9</priority>
+      </url>
+    </urlset>
+    """

data/features/public/snippets.feature ADDED Viewed

@@ -0,0 +1,21 @@
+Feature: Snippets
+  As a designer
+  I want to insert re-usable piece of code among pages
+Background:
+  Given I have the site: "test site" set up
+  And a snippet named "yield" with the template:
+    """
+    HELLO WORLD !
+    """
+Scenario: Simple include
+  Given a page named "hello-world" with the template:
+    """
+    My application says {% include 'yield' %}
+    """
+  When I view the rendered page at "/hello-world"
+  Then the rendered output should look like:
+    """
+    My application says HELLO WORLD !
+    """

data/features/public/tablerow.feature ADDED Viewed

@@ -0,0 +1,42 @@
+Feature: TableRow liquid tags
+  As a designer
+  I want to be able to use the tablerow liquid tag with locomotive contents
+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      |
+  And I have entries for "Projects" with
+    | name        | _position |
+    | Project 1   | 1         |
+    | Project 2   | 2         |
+    | Project 3   | 3         |
+Scenario: Use the tablerow tag
+  Given a page named "project-table" with the template:
+    """
+    <h1>Projects</h1>
+    <table>
+    {% tablerow project in contents.projects cols: 2 %}
+    {{ project.name }}
+    {% endtablerow %}
+    </table>
+    """
+  When I view the rendered page at "/project-table"
+  Then the rendered output should look like:
+    """
+    <h1>Projects</h1>
+    <table>
+    <tr class="row1">
+    <td class="col1">
+    Project 1
+    </td><td class="col2">
+    Project 2
+    </td></tr>
+    <tr class="row2"><td class="col1">
+    Project 3
+    </td></tr>
+    </table>
+    """

data/features/public/tags.feature ADDED Viewed

@@ -0,0 +1,45 @@
+Feature: Tagged content
+  As a designer
+  In order to organize my content
+  I want to be able to tag it
+Background:
+  Given I have the site: "test site" set up
+  And I have a custom model named "Posts" with
+    | label         | type      | required    |
+    | Title         | string    | true        |
+    | Body          | string    | false       |
+    | Tags          | tags      | false       |
+  And I have entries for "Posts" with
+    | title             | body          | tags              |
+    | Fashion post      | Fashion body  | blogging, fashion |
+    | Diet post         | Diet body     | blogging, diet    |
+Scenario: Navigate by tags
+  Given a page named "my-posts" with the template:
+    """
+    {% if params.tag %}
+     {% with_scope tags: params.tag %}
+       {% assign posts = contents.posts.all %}
+     {% endwith_scope %}
+    {% else %}
+     {% assign posts = contents.posts.all %}
+    {% endif %}
+    {% for post in posts %}
+     {{ post.title }}<br>
+     {% for tag in post.tags %}
+     <a href="/my-posts?tag={{ tag }}">{{ tag }}</a>
+     {% endfor %}
+     <hr>
+    {% endfor %}
+    """
+  When I view the rendered page at "/my-posts"
+  Then I should see "Fashion post"
+  And I should see "Diet post"
+  When I follow "blogging"
+  Then I should see "Fashion post"
+  And I should see "Diet post"
+  When I follow "fashion"
+  Then I should see "Fashion"
+  And I should not see "Diet"