middleman-more 3.1.0.beta.3 → 3.1.0.rc.2

data/features/minify_javascript.feature

@@ -1,225 +0,0 @@
-Feature: Minify Javascript
-  In order reduce bytes sent to client and appease YSlow
-
-  Scenario: Rendering inline js with the feature disabled
-    Given a fixture app "minify-js-app"
-    And a file named "config.rb" with:
-      """
-      """
-    And the Server is running at "minify-js-app"
-    When I go to "/inline-js.html"
-    Then I should see:
-    """
-    <script>
-      ;(function() {
-        this;
-        should();
-        all.be();
-        on = { one: line };
-      })();
-    </script>
-    <script>
-      ;(function() {
-        this;
-        should();
-        too();
-      })();
-    </script>
-    <script type='text/javascript'>
-      //<!--
-      ;(function() {
-        one;
-        line();
-        here();
-      })();
-      //-->
-    </script>
-    <script type='text/html'>
-      I'm a jQuery {{template}}.
-    </script>
-    """
-    
-  Scenario: Rendering inline js with a passthrough minifier
-    Given a fixture app "passthrough-app"
-    And a file named "config.rb" with:
-      """
-      module ::PassThrough
-        def self.compress(data)
-          data
-        end
-      end
-
-      activate :minify_javascript, :inline => true
-
-      set :js_compressor, ::PassThrough
-
-      page "/inline-js.html", :layout => false
-      """
-    And the Server is running at "passthrough-app"
-    When I go to "/inline-js.html"
-    Then I should see:
-    """
-    <script>
-      ;(function() {
-        this;
-        should();
-        all.be();
-        on = { one: line };
-      })();
-    </script>
-    <script>
-      ;(function() {
-        this;
-        should();
-        too();
-      })();
-    </script>
-    <script type='text/javascript'>
-      //<!--
-      ;(function() {
-        one;
-        line();
-        here();
-      })();
-      //-->
-    </script>
-    <script type='text/html'>
-      I'm a jQuery {{template}}.
-    </script>
-    """
-
-  Scenario: Rendering inline css with a passthrough minifier using activate-style compressor
-    Given a fixture app "passthrough-app"
-    And a file named "config.rb" with:
-      """
-      module ::HelloCompressor
-        def self.compress(data)
-          "Hello"
-        end
-      end
-
-      activate :minify_javascript, :inline => true, :compressor => ::HelloCompressor
-
-      page "/inline-js.html", :layout => false
-      """
-    And the Server is running at "passthrough-app"
-    When I go to "/inline-js.html"
-    Then I should see:
-    """
-    <script>
-      Hello
-    </script>
-    <script>
-      Hello
-    </script>
-    <script type='text/javascript'>
-      //<!--
-    Hello
-      //-->
-    </script>
-    <script type='text/html'>
-      I'm a jQuery {{template}}.
-    </script>
-    """
-    
-  Scenario: Rendering inline js with the feature enabled
-    Given a fixture app "minify-js-app"
-    And a file named "config.rb" with:
-      """
-      activate :minify_javascript, :inline => true
-      """
-    And the Server is running at "minify-js-app"
-    When I go to "/inline-js.html"
-    Then I should see:
-    """
-    <script>
-      (function(){should(),all.be(),on={one:line}})();
-    </script>
-    <script>
-      (function(){should(),too()})();
-    </script>
-    <script type='text/javascript'>
-      //<!--
-    (function(){line(),here()})();
-      //-->
-    </script>
-    <script type='text/html'>
-      I'm a jQuery {{template}}.
-    </script>
-    """
-    
-  Scenario: Rendering external js with the feature enabled
-    Given a fixture app "minify-js-app"
-    And a file named "config.rb" with:
-      """
-      activate :minify_javascript
-      """
-    And the Server is running at "minify-js-app"
-    When I go to "/javascripts/js_test.js"
-    Then I should see "1" lines
-    When I go to "/more-js/other.js"
-    Then I should see "1" lines
-    
-  Scenario: Rendering external js with a passthrough minifier
-    And the Server is running at "passthrough-app"
-    When I go to "/javascripts/js_test.js"
-    Then I should see "8" lines
-
-  Scenario: Rendering inline js (coffeescript) with the feature enabled
-    Given a fixture app "minify-js-app"
-    And a file named "config.rb" with:
-      """
-      activate :minify_javascript, :inline => true
-      """
-    And the Server is running at "minify-js-app"
-    When I go to "/inline-coffeescript.html"
-    Then I should see "3" lines
-  
-  Scenario: Rendering external js (coffeescript) with the feature enabled
-    Given a fixture app "minify-js-app"
-    And a file named "config.rb" with:
-      """
-      activate :minify_javascript
-      """
-    And the Server is running at "minify-js-app"
-    When I go to "/javascripts/coffee_test.js"
-    Then I should see "1" lines
-    
-  Scenario: Rendering inline js (coffeescript) with a passthrough minifier
-    Given a fixture app "passthrough-app"
-    And a file named "config.rb" with:
-      """
-      module ::PassThrough
-        def self.compress(data)
-          data
-        end
-      end
-
-      activate :minify_javascript, :inline => true
-
-      set :js_compressor, ::PassThrough
-
-      page "/inline-coffeescript.html", :layout => false
-      """
-    And the Server is running at "passthrough-app"
-    When I go to "/inline-coffeescript.html"
-    Then I should see "14" lines
-    
-  Scenario: Rendering external js (coffeescript) with a passthrough minifier
-    Given a fixture app "passthrough-app"
-    And a file named "config.rb" with:
-      """
-      module ::PassThrough
-        def self.compress(data)
-          data
-        end
-      end
-
-      activate :minify_javascript
-
-      set :js_compressor, ::PassThrough
-      """
-    And the Server is running at "passthrough-app"
-    When I go to "/javascripts/coffee_test.js"
-    Then I should see "12" lines
-    

data/features/nested_layouts.feature

@@ -1,55 +0,0 @@
-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:
-    """
-    Master
-    <h1>Index Title</h1>
-      Outer
-        Inner
-      Template
-    
-    """
-    When I go to "/another.html"
-    Then I should see:
-    """
-    Master
-    <h1>New Article Title</h1>
-      Outer
-        Inner
-      <p>The Article Content</p>
-    """
-    
-  Scenario: A page uses an inner layout when uses an outer layout (slim)
-    Given the Server is running at "nested-layout-app"
-    When I go to "/slim-test.html"
-    Then I should see "<h1>Master</h1><p>New Article Title</p><div><h2>Outer</h2><h3>Inner</h3><p>The Article Content</p>"
-    
-  Scenario: A page uses an inner layout when uses an outer layout (haml)
-    Given the Server is running at "nested-layout-app"
-    When I go to "/haml-test.html"
-    Then I should see:
-    """
-    Master
-    <h1>New Article Title</h1>
-    Outer
-    Inner
-    <p>The Article Content</p>
-    """
-
-  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

@@ -1,46 +0,0 @@
-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: Finds shared partials without _ prefix
-    Given the Server is running at "partials-app"
-    When I go to "/using_snippet.html"
-    Then I should see "Snippet"
-    
-  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/partials_dir.feature

@@ -1,30 +0,0 @@
-Feature: Partials dir
-  Scenario: Find partials in a custom partials dir
-    Given a fixture app "partials-dir-app"
-    And a file named "config.rb" with:
-    """
-    set :partials_dir, 'partials'
-    """
-    And the Server is running
-    When I go to "/index.html"
-    Then I should see "contents of the partial"
-
-  Scenario: Find partials in a nested custom partials dir
-    Given a fixture app "partials-dir-app"
-    And a file named "config.rb" with:
-    """
-    set :partials_dir, 'nested/partials'
-    """
-    And the Server is running
-    When I go to "/index.html"
-    Then I should see "contents of the nested partial"
-
-  Scenario: Find partials in the default partials dir
-    Given a fixture app "default-partials-dir-app"
-    And a file named "config.rb" with:
-    """
-    """
-    And the Server is running
-    When I go to "/index.html"
-    Then I should see "contents of the partial"
-

data/features/relative_assets.feature

@@ -1,102 +0,0 @@
-Feature: Relative Assets
-  In order easily switch between relative and absolute paths
-    
-  Scenario: Previewing css with the feature disabled
-    Given "relative_assets" feature is "disabled"
-    And the Server is running at "relative-assets-app"
-    When I go to "/stylesheets/relative_assets.css"
-    Then I should not see "url('../"
-    And I should see "/images/blank.gif')"
-    
-  Scenario: Building css with the feature disabled
-    Given a fixture app "relative-assets-app"
-    And a file named "config.rb" with:
-      """
-      """
-    Given a successfully built app at "relative-assets-app"
-    When I cd to "build"
-    Then the file "stylesheets/relative_assets.css" should contain "url('/images/blank.gif')"
-    
-  Scenario: Rendering html with the feature disabled
-    Given "relative_assets" feature is "disabled"
-    And the Server is running at "relative-assets-app"
-    When I go to "/relative_image.html"
-    Then I should see "/images/blank.gif"
-
-  Scenario: Rendering css with the feature enabled
-    Given "relative_assets" feature is "enabled"
-    And the Server is running at "relative-assets-app"
-    When I go to "/stylesheets/relative_assets.css"
-    Then I should see "url('../images/blank.gif"
-    
-  Scenario: Building css with the feature enabled
-    Given a fixture app "relative-assets-app"
-    And a file named "config.rb" with:
-      """
-      activate :relative_assets
-      """
-    Given a successfully built app at "relative-assets-app"
-    When I cd to "build"
-    Then the file "stylesheets/relative_assets.css" should contain "url('../images/blank.gif')"
-    
-  Scenario: Relative css reference with directory indexes
-    Given a fixture app "relative-assets-app"
-    And a file named "config.rb" with:
-      """
-      activate :directory_indexes
-      activate :relative_assets
-      """
-    Given a successfully built app at "relative-assets-app"
-    When I cd to "build"
-    Then the file "relative_image/index.html" should contain "../stylesheets/relative_assets.css"
-    
-  Scenario: Rendering html with the feature enabled
-    Given "relative_assets" feature is "enabled"
-    And the Server is running at "relative-assets-app"
-    When I go to "/relative_image.html"
-    Then I should not see "/images/blank.gif"
-    And I should see "images/blank.gif"
-    
-  Scenario: Rendering css with a custom images_dir
-    Given "relative_assets" feature is "enabled"
-    And "images_dir" is set to "img"
-    And the Server is running at "relative-assets-app"
-    When I go to "/stylesheets/relative_assets.css"
-    Then I should see "url('../img/blank.gif')"
-    
-  Scenario: Building css with a custom images_dir
-    Given a fixture app "relative-assets-app"
-    And a file named "config.rb" with:
-      """
-      set :images_dir, "img"
-      activate :relative_assets
-      """
-    Given a successfully built app at "relative-assets-app"
-    When I cd to "build"
-    Then the file "stylesheets/relative_assets.css" should contain "url('../img/blank.gif')"
-    
-  Scenario: Rendering html with a custom images_dir
-    Given "relative_assets" feature is "enabled"
-    And "images_dir" is set to "img"
-    And the Server is running at "relative-assets-app"
-    When I go to "/relative_image.html"
-    Then I should not see "/images/blank.gif"
-    Then I should not see "/img/blank.gif"
-    And I should see "img/blank.gif"
-    
-  Scenario: Rendering scss with the feature enabled
-    Given "relative_assets" feature is "enabled"
-    And the Server is running at "fonts-app"
-    When I go to "/stylesheets/fonts.css"
-    Then I should see "url('../fonts/StMarie-Thin.otf"
-
-  Scenario: Relative assets via image_tag
-    Given a fixture app "relative-assets-app"
-    Given "relative_assets" feature is "enabled"
-    And a file named "source/sub/image_tag.html.erb" with:
-      """
-      <%= image_tag '/img/blank.gif' %>
-      """
-    And the Server is running at "relative-assets-app"
-    When I go to "/sub/image_tag.html"
-    Then I should see '<img src="../img/blank.gif" />'

data/features/sass-assets-paths.feature

@@ -1,11 +0,0 @@
-Feature: Support SASS assets paths
- In order to import common shared assets when writing Sass
-
- Scenario: Importing assets from 'assets/stylesheets/' directory in app root
-   Given the Server is running at "sass-assets-path-app"
-   When I go to "/stylesheets/plain.css"
-   Then I should see "color: green;"
-   Then I should see "/* Works with shared SCSS assets from APPROOT/assets/stylesheets/_shared-asset.scss */"
-   Then I should see "/* Works with shared SASS assets from APPROOT/assets/stylesheets/_shared-asset-sass.sass */"
-   Then I should see "font-size: 18px"
-   Then I should see "/* Works with shared SASS assets from external source directory */"

data/features/sass_cache_path.feature

@@ -1,22 +0,0 @@
-Feature: SASS .sass-cache custom location
-
-  Scenario: Using the default location for .sass-cache folder
-    Given the Server is running at "sass-cache-path-default-app"
-
-    When I go to "/stylesheets/plain.css"
-    Then I should see "color: blue;"
-
-    #  TODO:: 
-    #  Not sure how to test this location, as the directory is stored outside of the app root
-    #  during testing, but inside app root in "production"
-
-    # Then a directory named ".sass-cache" should exist
-
-
-  Scenario: Using a custom location for .sass-cache folder
-    Given the Server is running at "sass-cache-path-custom-app"
-
-    When I go to "/stylesheets/plain.css"
-    Then I should see "html, body, div, span, applet, object, iframe,"
-
-    Then a directory named "/tmp/middleman-more-custom-sass_cache_path" should exist

data/features/sass_partials.feature

@@ -1,54 +0,0 @@
-Feature: Sass Updates and Partials
-  Scenario: The preview server should update stylesheets when Sass changes
-    Given the Server is running at "preview-app"
-    And the file "source/stylesheets/plain.css.sass" has the contents
-      """
-      red
-        color: red
-      """
-    When I go to "/stylesheets/plain.css"
-    Then I should see "color: red;"
-    And the file "source/stylesheets/plain.css.sass" has the contents
-      """
-      red
-        color: blue
-      """
-    When I go to "/stylesheets/plain.css"
-    Then I should see "color: blue;"
-
-  Scenario: The preview server should update stylesheets when Sass partials change
-    Given the Server is running at "preview-app"
-    And the file "source/stylesheets/main.css.sass" has the contents
-      """
-      @import partial.sass
-
-      red
-        color: red
-      """
-    And the file "source/stylesheets/_partial.sass" has the contents
-      """
-      body
-        font-size: 14px
-      """
-    When I go to "/stylesheets/main.css"
-    Then I should see "color: red;"
-    And I should see "font-size: 14px;"
-    And the file "source/stylesheets/main.css.sass" has the contents
-      """
-      @import partial.sass
-
-      red
-        color: blue
-      """
-    And the file "source/stylesheets/_partial.sass" has the contents
-      """
-      body
-        font-size: 18px
-      """
-    When I go to "/stylesheets/main.css"
-    Then I should see "color: blue;"
-    And I should see "font-size: 18px"
-
-  Scenario: Sass partials should work when building
-    Given a successfully built app at "preview-app"
-    Then the file "build/stylesheets/main.css" should contain "font-size: 18px"

data/features/scss-support.feature

@@ -1,12 +0,0 @@
-Feature: Support SCSS Syntax
- In order to offer an alternative when writing Sass
-
- Scenario: Rendering scss
-   Given the Server is running at "scss-app"
-   When I go to "/stylesheets/site_scss.css"
-   Then I should see "html"
-
- Scenario: Rendering scss
-   Given the Server is running at "scss-app"
-   When I go to "/stylesheets/layout.css"
-   Then I should see "html"

data/features/sitemap_traversal.feature

@@ -1,73 +0,0 @@
-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 see "Path: 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 "Path: 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: Directory accessed without index.html
-    Given the Server is running at "traversal-app"
-    When I go to "/sub/"
-    Then I should see "Path: 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, parent, and source file
-    Given the Server is running at "traversal-app"
-    When I go to "/sub/sibling/"
-    Then I should see "Parent: sub/index.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"
-    Then I should see "Source: source/sub/sibling.html.erb"
-  
-  Scenario: Proxied page has siblings, parent, and source file
-    Given the Server is running at "traversal-app"
-    When I go to "/sub/fake/"
-    Then I should see "Path: sub/fake.html"
-    Then I should see "Parent: sub/index.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"
-    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 "Path: directory-indexed.html"
-    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"