middleman-core 3.0.0.alpha.7

data/features/directory_index.feature

@@ -0,0 +1,36 @@
+Feature: Directory Index
+  In order output Apache-friendly directories and indexes
+
+  Scenario: Checking built folder for content
+    Given a successfully built app at "indexable-app"
+    When I cd to "build"
+    Then the following files should exist:
+      | needs_index/index.html                        |
+      | a_folder/needs_index/index.html               |
+      | leave_me_alone.html                           |
+      | regular/index.html                            |
+      | .htaccess                                     |
+    Then the following files should not exist:
+      | egular/index/index.html                       |
+      | needs_index.html                              |
+      | a_folder/needs_index.html                     |
+      | leave_me_alone/index.html                     |
+    And the file "needs_index/index.html" should contain "Indexable"
+    And the file "a_folder/needs_index/index.html" should contain "Indexable"
+    And the file "leave_me_alone.html" should contain "Stay away"
+    And the file "regular/index.html" should contain "Regular"
+    
+  Scenario: Preview normal file
+    Given the Server is running at "indexable-app"
+    When I go to "/needs_index/"
+    Then I should see "Indexable"
+    
+  Scenario: Preview normal file subdirectory
+    Given the Server is running at "indexable-app"
+    When I go to "/a_folder/needs_index/"
+    Then I should see "Indexable"
+    
+  Scenario: Preview ignored file
+    Given the Server is running at "indexable-app"
+    When I go to "/leave_me_alone/"
+    Then I should see "File Not Found"

data/features/dynamic_pages.feature

@@ -0,0 +1,95 @@
+Feature: Dynamic Pages
+  In order to use a single view to generate multiple output files
+
+  Scenario: Checking built folder for content
+    Given a successfully built app at "dynamic-pages-app"
+    When I cd to "build"
+    Then the following files should exist:
+      | fake.html                                     |
+      | fake2.html                                    |
+      | fake3.html                                    |
+      | fake4.html                                    |
+      | fake/one.html                                 |
+      | fake/two.html                                 |
+      | fake2/one.html                                |
+      | fake2/two.html                                |
+      | fake3/one.html                                |
+      | fake3/two.html                                |
+      | fake4/one.html                                |
+      | fake4/two.html                                |
+      | target_ignore.html                            |
+      | target_ignore2.html                           |
+      | target_ignore3.html                           |
+      | target_ignore4.html                           |
+    Then the following files should not exist:
+      | should_be_ignored.html                        |
+      | should_be_ignored2.html                       |
+      | should_be_ignored3.html                       |
+      | should_be_ignored4.html                       |
+      | should_be_ignored5.html                       |
+      | should_be_ignored6.html                       |
+      | should_be_ignored7.html                       |
+      | should_be_ignored8.html                       |
+    
+  Scenario: Preview basic proxy
+    Given the Server is running at "dynamic-pages-app"
+    When I go to "/fake.html"
+    Then I should see "I am real"
+    When I go to "/fake2.html"
+    Then I should see "I am real"
+    When I go to "/fake3.html"
+    Then I should see "I am real"
+    When I go to "/fake4.html"
+    Then I should see "I am real"
+    
+  Scenario: Preview proxy with variable one
+    Given the Server is running at "dynamic-pages-app"
+    When I go to "/fake/one.html"
+    Then I should see "I am real: one"
+    When I go to "/fake2/one.html"
+    Then I should see "I am real: one"
+    When I go to "/fake3/one.html"
+    Then I should see "I am real: one"
+    When I go to "/fake4/one.html"
+    Then I should see "I am real: one"
+    
+  Scenario: Preview proxy with variable two
+    Given the Server is running at "dynamic-pages-app"
+    When I go to "/fake/two.html"
+    Then I should see "I am real: two"
+    When I go to "/fake2/two.html"
+    Then I should see "I am real: two"
+    When I go to "/fake3/two.html"
+    Then I should see "I am real: two"
+    When I go to "/fake4/two.html"
+    Then I should see "I am real: two"
+    
+  Scenario: Target ignore
+    Given the Server is running at "dynamic-pages-app"
+    When I go to "/target_ignore.html"
+    Then I should see "Ignore me! 3"
+    When I go to "/target_ignore2.html"
+    Then I should see "Ignore me! 6"
+    When I go to "/target_ignore3.html"
+    Then I should see "Ignore me! 7"
+    When I go to "/target_ignore4.html"
+    Then I should see "Ignore me! 8"
+    
+  Scenario: Preview ignored paths
+    Given the Server is running at "dynamic-pages-app"
+    When I go to "/should_be_ignored.html"
+    Then I should see "File Not Found"
+    When I go to "/should_be_ignored2.html"
+    Then I should see "File Not Found"
+    When I go to "/should_be_ignored3.html"
+    Then I should see "File Not Found"
+    When I go to "/should_be_ignored4.html"
+    Then I should see "File Not Found"
+    When I go to "/should_be_ignored5.html"
+    Then I should see "File Not Found"
+    When I go to "/should_be_ignored6.html"
+    Then I should see "File Not Found"
+    When I go to "/should_be_ignored7.html"
+    Then I should see "File Not Found"
+    When I go to "/should_be_ignored8.html"
+    Then I should see "File Not Found"

data/features/feature_params.feature

@@ -0,0 +1,6 @@
+Feature: Be able to pass params to extensions
+  Scenario: Read some simple variables
+    Given the Server is running at "feature-params-app"
+    When I go to "/index.html"
+    Then I should see "hello: world"
+    And I should see "hola: mundo"

data/features/former_padrino_helpers.feature

@@ -0,0 +1,10 @@
+Feature: Built-in macro view helpers
+  In order to simplify generating HTML
+
+  Scenario: Using the link_to helper
+    Given the Server is running at "padrino-helpers-app"
+    When I go to "/former_padrino_test.html"
+    And I should see 'href="test2.com"'
+    And I should see 'src="/images/test2.png"'
+    Then I should see 'src="/javascripts/test1.js"'
+    Then I should see 'href="/stylesheets/test1.css"'

data/features/front-matter.feature

@@ -0,0 +1,35 @@
+Feature: YAML Front Matter
+  In order to specific options and data inline
+
+  Scenario: Rendering html
+    Given the Server is running at "frontmatter-app"
+    When I go to "/front-matter.html"
+    Then I should see "<h1>This is the title</h1>"
+    Then I should not see "---"
+    When I go to "/front-matter-2.php"
+    Then I should see "<h1>This is the title</h1>"
+    Then I should see "<?php"
+    Then I should not see "---"
+
+  Scenario: A template changes frontmatter during preview
+    Given the Server is running at "frontmatter-app"
+    And the file "source/front-matter-change.html.erb" has the contents
+      """
+      ---
+      title: Hello World
+      layout: false
+      ---
+      <%= data.page.title %>
+      """
+    When I go to "/front-matter-change.html"
+    Then I should see "Hello World"
+    And the file "source/front-matter-change.html.erb" has the contents
+      """
+      ---
+      title: Hola Mundo
+      layout: false
+      ---
+      <%= data.page.title %>
+      """
+    When I go to "/front-matter-change.html"
+    Then I should see "Hola Mundo"

data/features/helpers_auto_javascript_include_tag.feature

@@ -0,0 +1,27 @@
+Feature: Built-in auto_javascript_include_tag view helper
+  In order to simplify including javascript files
+
+  Scenario: Viewing the root path
+    Given the Server is running at "auto-js-app"
+    When I go to "/auto-js.html"
+    Then I should see "javascripts/auto-js.js"
+
+  Scenario: Viewing a tier-1 path
+    Given the Server is running at "auto-js-app"
+    When I go to "/auto-js/auto-js.html"
+    Then I should see "javascripts/auto-js/auto-js.js"
+
+  Scenario: Viewing the index file of a tier-1 path, without filename
+    Given the Server is running at "auto-js-app"
+    When I go to "/auto-js"
+    Then I should see "javascripts/auto-js/index.js"
+
+  Scenario: Viewing the index file of a tier-1 path, without filename, with a trailing slash
+    Given the Server is running at "auto-js-app"
+    When I go to "/auto-js/"
+    Then I should see "javascripts/auto-js/index.js"
+
+  Scenario: Viewing a tier-2 path
+    Given the Server is running at "auto-js-app"
+    When I go to "/auto-js/sub/auto-js.html"
+    Then I should see "javascripts/auto-js/sub/auto-js.js"

data/features/helpers_auto_stylesheet_link_tag.feature

@@ -0,0 +1,27 @@
+Feature: Built-in auto_stylesheet_link_tag view helper
+  In order to simplify including css files
+
+  Scenario: Viewing the root path
+    Given the Server is running at "auto-css-app"
+    When I go to "/auto-css.html"
+    Then I should see "stylesheets/auto-css.css"
+
+  Scenario: Viewing a tier-1 path
+    Given the Server is running at "auto-css-app"
+    When I go to "/auto-css/auto-css.html"
+    Then I should see "stylesheets/auto-css/auto-css.css"
+
+  Scenario: Viewing the index file of a tier-1 path, without filename
+    Given the Server is running at "auto-css-app"
+    When I go to "/auto-css"
+    Then I should see "stylesheets/auto-css/index.css"
+
+  Scenario: Viewing the index file of a tier-1 path, without filename, with a trailing slash
+    Given the Server is running at "auto-css-app"
+    When I go to "/auto-css/"
+    Then I should see "stylesheets/auto-css/index.css"
+
+  Scenario: Viewing a tier-2 path
+    Given the Server is running at "auto-css-app"
+    When I go to "/auto-css/sub/auto-css.html"
+    Then I should see "stylesheets/auto-css/sub/auto-css.css"

data/features/helpers_external.feature

@@ -0,0 +1,6 @@
+Feature: Helpers in external files
+
+  Scenario: Hello Helper
+    Given the Server is running at "external-helpers"
+    Then going to "/index.html" should not raise an exception
+    And I should see "Hello World"

data/features/helpers_lorem.feature

@@ -0,0 +1,6 @@
+Feature: Lorem generating helper
+
+  Scenario: Lorem Helper
+    Given the Server is running at "lorem-app"
+    Then going to "/lorem.html" should not raise an exception
+    And I should see "http://placekitten.com/100"

data/features/helpers_page_classes.feature

@@ -0,0 +1,17 @@
+Feature: Built-in page_classes view helper
+  In order to generate body classes for views
+  
+  Scenario: Viewing the root path
+    Given the Server is running at "page-classes-app"
+    When I go to "/page-classes.html"
+    Then I should see "page-classes"
+
+  Scenario: Viewing a tier-1 path
+    Given the Server is running at "page-classes-app"
+    When I go to "/sub1/page-classes.html"
+    Then I should see "sub1 sub1_page-classes"
+
+  Scenario: Viewing a tier-2 path
+    Given the Server is running at "page-classes-app"
+    When I go to "/sub1/sub2/page-classes.html"
+    Then I should see "sub1 sub1_sub2 sub1_sub2_page-classes"

data/features/instance_vars.feature

@@ -0,0 +1,20 @@
+Feature: Instance Vars
+  In order to share data with layouts and partials via instance variables
+
+  Scenario: Setting an instance var in a template should be visible in its layout
+    Given the Server is running at "instance-vars-app"
+    When I go to "/instance-var-set.html"
+    Then I should see "Var is 100"
+
+  Scenario: Setting an instance var in a template should be visible in a partial
+    Given the Server is running at "instance-vars-app"
+    When I go to "/instance-var-set.html"
+    Then I should see "My var is here!"
+
+  Scenario: Setting an instance var in one file should not be visible in another
+    Given the Server is running at "instance-vars-app"
+    When I go to "/instance-var-set.html"
+    When I go to "/no-instance-var.html"
+    Then I should see "No var..."
+  
+    

data/features/mount_rack.feature

@@ -0,0 +1,8 @@
+Feature: Support Rack apps mounted using map
+
+  Scenario: Mounted Rack App at /sinatra
+    Given the Server is running at "sinatra-app"
+    When I go to "/"
+    Then I should see "Hello World (Middleman)"
+    When I go to "/sinatra/"
+    Then I should see "Hello World (Sinatra)"

data/features/nested_layouts.feature

@@ -0,0 +1,24 @@
+Feature: Allow nesting of layouts
+
+  Scenario: A page uses an inner layout when uses an outer layout
+    Given the Server is running at "nested-layout-app"
+    When I go to "/index.html"
+    Then I should see "Template"
+    And I should see "Inner"
+    And I should see "Outer"
+    And I should see "Master"
+
+  Scenario: YAML Front Matter isn't clobbered with nested layouts
+    Given the Server is running at "nested-layout-app"
+    When I go to "/data-one.html"
+    Then I should see "Page Number One"
+    And I should see "Inner"
+    When I go to "/data-two.html"
+    Then I should see "Page Number Two"
+    And I should not see "Inner"
+    When I go to "/data-one.html"
+    Then I should see "Page Number One"
+    And I should see "Inner"
+    When I go to "/data-two.html"
+    Then I should see "Page Number Two"
+    And I should not see "Inner"

data/features/partials.feature

@@ -0,0 +1,41 @@
+Feature: Provide Sane Defaults for Partial Behavior
+
+  Scenario: Finds shared partials relative to the root
+    Given the Server is running at "partials-app"
+    When I go to "/index.html"
+    Then I should see "Header"
+    And I should see "Footer"
+    
+  Scenario: Finds shared partials relative to the root (sub)
+    Given the Server is running at "partials-app"
+    When I go to "/sub/index.html"
+    Then I should see "Header"
+    And I should see "Footer"
+
+  Scenario: Prefers partials of the same engine type
+    Given the Server is running at "partials-app"
+    When I go to "/index.html"
+    Then I should see "ERb Main"
+  
+  Scenario: Prefers partials of the same engine type
+    Given the Server is running at "partials-app"
+    When I go to "/second.html"
+    Then I should see "Str Main"
+    And I should see "Header"
+    And I should see "Footer"
+    
+  Scenario: Finds partial relative to template
+    Given the Server is running at "partials-app"
+    When I go to "/sub/index.html"
+    Then I should see "Local Partial"
+
+  Scenario: Partials can be passed locals
+    Given the Server is running at "partials-app"
+    When I go to "/locals.html"
+    Then I should see "Local var is bar"
+  
+  Scenario: Partial and Layout use different engines
+    Given the Server is running at "different-engine-partial"
+    When I go to "/index.html"
+    Then I should see "ERb Header"
+    And I should see "Str Footer"

data/features/preview_changes.feature

@@ -0,0 +1,18 @@
+Feature: Preview Changes
+  In order to run quickly, we should update internal caches on file changes
+  
+  Scenario: A template changes contents during preview
+    Given the Server is running at "preview-app"
+    And the file "source/content.html.erb" has the contents
+      """
+      Hello World
+      """
+    When I go to "/content.html"
+    Then I should see "Hello World"
+    And the file "source/content.html.erb" has the contents
+      """
+      Hola Mundo
+      """
+    When I go to "/content.html"
+    Then I should see "Hola Mundo"
+    

data/features/sitemap_traversal.features

@@ -0,0 +1,73 @@
+Feature: Step through sitemap as a tree
+
+  Scenario: Root
+    Given the Server is running at "traversal-app"
+    When I go to "/index.html"
+    Then I should not see "Parent: index.html"
+    Then I should see "Child: sub/index.html"
+    Then I should see "Child: root.html"
+    Then I should not see "Child: proxied.html"
+  
+  Scenario: Directories have children and a parent
+    Given the Server is running at "traversal-app"
+    When I go to "/sub/index.html"
+    Then I should see "Parent: index.html"
+    Then I should see "Child: sub/fake.html"
+    Then I should see "Child: sub/fake2.html"
+    Then I should see "Child: sub/sibling.html"
+    Then I should see "Child: sub/sibling2.html"
+    Then I should see "Child: sub/sub2/index.html"
+    Then I should see "Sibling: root.html"
+  
+  Scenario: Page has siblings
+    Given the Server is running at "traversal-app"
+    When I go to "/sub/sibling.html"
+    Then I should see "Sibling: sub/fake.html"
+    Then I should see "Sibling: sub/fake2.html"
+    Then I should see "Sibling: sub/sibling2.html"
+    Then I should see "Sibling: sub/sub2/index.html"
+  
+  Scenario: Proxied page has siblings
+    Given the Server is running at "traversal-app"
+    When I go to "/sub/fake.html"
+    Then I should see "Sibling: sub/fake2.html"
+    Then I should see "Sibling: sub/sibling.html"
+    Then I should see "Sibling: sub/sibling2.html"
+    Then I should see "Sibling: sub/sub2/index.html"
+  
+  Scenario: Page has parent
+    Given the Server is running at "traversal-app"
+    When I go to "/sub/sibling.html"
+    Then I should see "Parent: sub/index.html"
+  
+  Scenario: Proxied page has parent
+    Given the Server is running at "traversal-app"
+    When I go to "/sub/fake.html"
+    Then I should see "Parent: sub/index.html"
+  
+  Scenario: Page has source_file
+    Given the Server is running at "traversal-app"
+    When I go to "/sub/sibling.html"
+    Then I should see "Source: source/sub/sibling.html.erb"
+  
+  Scenario: Proxied page has source_file
+    Given the Server is running at "traversal-app"
+    When I go to "/sub/fake.html"
+    Then I should see "Source: source/proxied.html.erb"
+
+  Scenario: Child pages have data
+    Given the Server is running at "traversal-app"
+    When I go to "/directory-indexed"
+    Then I should see "Title of Sibling One"
+    Then I should see "Title of Sibling Two"
+
+  Scenario: When directory_index extension is active, child pages are found in named directory
+    Given the Server is running at "traversal-app"
+    When I go to "/directory-indexed"
+    Then I should see "Parent: index.html"
+    Then I should see "Child: directory-indexed/fake.html"
+    Then I should see "Child: directory-indexed/fake2.html"
+    Then I should see "Child: directory-indexed/sibling.html"
+    Then I should see "Child: directory-indexed/sibling2.html"
+    Then I should see "Child: directory-indexed/sub2/index.html"
+    Then I should see "Sibling: root.html"