Sha256: 072c05a9dc7035270d91b2331fd8f31a6a2cc7ea50e98ea2e79b335c603b33bd
Contents?: true
Size: 1.87 KB
Versions: 6
Compression:
Stored size: 1.87 KB
Contents
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 the root path (build mode)
Given a successfully built app at "auto-js-app"
When I cd to "build"
Then the following files should exist:
| auto-js.html |
And the file "auto-js.html" should contain "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 a tier-1 path (build mode)
Given a successfully built app at "auto-js-app"
When I cd to "build"
Then the following files should exist:
| auto-js/auto-js.html |
And the file "auto-js/auto-js.html" should contain "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"
Scenario: Viewing a tier-2 path (build mode)
Given a successfully built app at "auto-js-app"
When I cd to "build"
Then the following files should exist:
| auto-js/sub/auto-js.html |
And the file "auto-js/sub/auto-js.html" should contain "javascripts/auto-js/sub/auto-js.js"
Version data entries
6 entries across 6 versions & 1 rubygems