Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

Changed the plugin name from 'javascript_testing' to 'blue-ridge'.

  • Loading branch information...
commit 1eb329da91074455ab21fea3a1565a3507fca58f 1 parent 94dc867
Larry Karnowski authored
View
22 README.markdown
@@ -1,7 +1,7 @@
-JavaScript Testing Rails Plugin
-===============================
+Blue Ridge JavaScript Testing Rails Plugin
+==========================================
-The JavaScript Testing Rails Plugin adds support for command-line and in-browser JavaScript unit tests to your Rails app. It bundles several great tools together in a convention-over-configuration, Rails-like way. These tools include:
+The Blue Ridge JavaScript Testing Rails Plugin adds support for command-line and in-browser JavaScript unit tests to your Rails app. It bundles several great tools together in a convention-over-configuration, Rails-like way. These tools include:
* `Rhino` - a Java-based JavaScript interpreter
* `Screw.Unit` - a behaviour-driven development syntax for JavaScript similar to RSpec
@@ -13,7 +13,7 @@ Installing and Running
To install:
- ./script/plugin install git://github.com/relevance/javascript_testing.git
+ ./script/plugin install git://github.com/relevance/blue-ridge.git
./script/generate javascript_testing
To run all of the specs:
@@ -38,7 +38,7 @@ Directory Layout: Specs and Fixtures
### JavaScript Spec Directories
-The plugin creates a directory for your JavaScript specs in one of the following directories, depending on which tool you use to test your Ruby code:
+Blue Ridge creates a directory for your JavaScript specs in one of the following directories, depending on which tool you use to test your Ruby code:
* examples/javascripts: if you're using [Micronaut](http://github.com/spicycode/micronaut)
* spec/javascripts: if you're using [RSpec](http://rspec.info/)
@@ -57,14 +57,14 @@ The layout of the JavaScript spec directories looks like this (assuming you crea
* screw.css: stylesheet for Screw.Unit output when running specs in-browser
### Why We Need Fixtures
-The plugin relies on the convention that each spec file will have a similarly named HTML file in the `fixtures` directory. We create one fixture per spec file so that env.js has a base DOM to emulate when running specs from the command line and so that we have an HTML launch-pad to run our specs in-browser.
+Blue Ridge relies on the convention that each spec file will have a similarly named HTML file in the `fixtures` directory. We create one fixture per spec file so that env.js has a base DOM to emulate when running specs from the command line and so that we have an HTML launch-pad to run our specs in-browser.
If you want to have specific HTML for a suite of specs, put it in the HTML fixture for that suite. If you want to run a specific suite of tests in Firefox or Internet Explorer, open the HTML fixture file with the same name and Screw.Unit automatically runs the specs associated with the fixture.
Example Using jQuery
---------------------------------------
-The plugin is opinionated and assumes you're using jQuery by default. The plugin itself actually uses jQuery under the covers to run Screw.Unit.
+Blue Ridge is opinionated and assumes you're using jQuery by default. The plugin itself actually uses jQuery under the covers to run Screw.Unit.
require("spec_helper.js");
require("../../public/javascripts/application.js");
@@ -116,7 +116,7 @@ Note that you must do the following:
JavaScript API
--------------
-The JavaScript Testing Rails Plugin provides a handful of functions that help you write specs that run correctly inside a web browser as well from the Rhino command-line test runner.
+The Blue Ridge plugin provides a handful of functions that help you write specs that run correctly inside a web browser as well from the Rhino command-line test runner.
### require(fileName, [{onload:function}])
When running from the command line, `require` becomes a Rhino call to `load`. In a web browser, `require` dynamically creates a JavaScript `script` tag and loads the given file for you. It takes an optional `onload` callback function that runs immediately after the given JavaScript file is loaded. This helps you chain dependencies. This is especially useful when running in-browser where each JavaScript file is loaded asynchronously in a separate thread.
@@ -176,15 +176,15 @@ Tips & Tricks
Caveats
----------
-env.js and jQuery 1.3.x do not currently get along well (as of 2009-04-14), so the JavaScript Testing Rails Plugin currently runs command line specs using jQuery 1.2.6. This is currently in active development, and any help is very appreciated!
+env.js and jQuery 1.3.x do not currently get along well (as of 2009-04-14), so Blue Ridge currently runs command line specs using jQuery 1.2.6. This is currently in active development, and any help is very appreciated!
Contributing
------------
-Fork the [Relevance repo on GitHub](http://www.github.com/relevance/javascript_testing) and start hacking! If you have patches, send us pull requests. Also, [env.js](http://github.com/thatcher/env-js), [Smoke](http://github.com/andykent/smoke), and [Screw.Unit](http://github.com/nkallen/screw-unit) could use your love too!
+Fork the [Relevance repo on GitHub](http://www.github.com/relevance/blue-ridge) and start hacking! If you have patches, send us pull requests. Also, [env.js](http://github.com/thatcher/env-js), [Smoke](http://github.com/andykent/smoke), and [Screw.Unit](http://github.com/nkallen/screw-unit) could use your love too!
Links
-------------
-* [JavaScript Testing Rails Plugin](http://github.com/relevance/javascript_testing)
+* [Blue Ridge JavaScript Testing Rails Plugin](http://github.com/relevance/blue-ridge)
* [Justin Gehtland's "Fully Headless JSSpec" Blog Post](http://blog.thinkrelevance.com/2008/7/31/fully-headless-jsspec)
* [Screw.Unit](http://github.com/nkallen/screw-unit)
* [Screw.Unit Mailing List](http://groups.google.com/group/screw-unit)
View
8 TODO.taskpaper
@@ -23,10 +23,10 @@ Release 1:
- add examples of mocking to README @done
- improve mocking example in README - show code under test
- caveat re stubbing in README
-- change name of plugin
- - change the relevance github fork's name
- - create a "javascript_testing" github project with a README that points folks to the new name
- - what is the new name? "blueridge"? "blue-ridge"? something else?
+- change name of plugin @done
+ - change the relevance github fork's name @done
+ - create a "javascript_testing" github project with a README that points folks to the new name @done
+ - what is the new name? --> "blue-ridge" @done
Release 2:
- Document TextMate support
- fork the screw.unit text mate bundle
View
2  generators/javascript_testing/templates/application.html
@@ -4,7 +4,7 @@
<head>
<title>Application | JavaScript Testing Results</title>
<link rel="stylesheet" href="screw.css" type="text/css" charset="utf-8" />
- <script type="text/javascript" src="../../../vendor/plugins/javascript_testing/lib/javascript_testing.js"></script>
+ <script type="text/javascript" src="../../../vendor/plugins/blue-ridge/lib/javascript_testing.js"></script>
</head>
<body>
View
24 lib/javascript_testing.js
@@ -26,18 +26,18 @@ function derive_spec_name_from_current_file() {
return file_prefix + "_spec.js";
}
-// require("../../vendor/plugins/javascript_testing/lib/jquery-1.2.6.js");
-require("../../vendor/plugins/javascript_testing/lib/jquery-1.3.2.js");
+// require("../../vendor/plugins/blue-ridge/lib/jquery-1.2.6.js");
+require("../../vendor/plugins/blue-ridge/lib/jquery-1.3.2.js");
-require("../../vendor/plugins/javascript_testing/lib/jquery.fn.js");
-require("../../vendor/plugins/javascript_testing/lib/jquery.print.js");
-require("../../vendor/plugins/javascript_testing/lib/screw.builder.js");
-require("../../vendor/plugins/javascript_testing/lib/screw.matchers.js");
-require("../../vendor/plugins/javascript_testing/lib/screw.events.js");
-require("../../vendor/plugins/javascript_testing/lib/screw.behaviors.js");
-require("../../vendor/plugins/javascript_testing/lib/smoke.core.js");
-require("../../vendor/plugins/javascript_testing/lib/smoke.mock.js");
-require("../../vendor/plugins/javascript_testing/lib/smoke.stub.js");
-require("../../vendor/plugins/javascript_testing/lib/screw.mocking.js");
+require("../../vendor/plugins/blue-ridge/lib/jquery.fn.js");
+require("../../vendor/plugins/blue-ridge/lib/jquery.print.js");
+require("../../vendor/plugins/blue-ridge/lib/screw.builder.js");
+require("../../vendor/plugins/blue-ridge/lib/screw.matchers.js");
+require("../../vendor/plugins/blue-ridge/lib/screw.events.js");
+require("../../vendor/plugins/blue-ridge/lib/screw.behaviors.js");
+require("../../vendor/plugins/blue-ridge/lib/smoke.core.js");
+require("../../vendor/plugins/blue-ridge/lib/smoke.mock.js");
+require("../../vendor/plugins/blue-ridge/lib/smoke.stub.js");
+require("../../vendor/plugins/blue-ridge/lib/screw.mocking.js");
require(derive_spec_name_from_current_file());
View
4 lib/shell.js
@@ -8,8 +8,8 @@
print(" To exit type 'exit', 'quit', or 'quit()'.");
print("=================================================");
- var plugin_prefix = "vendor/plugins/javascript_testing/";
- var fixture_file = plugin_prefix + "generators/javascript_testing/templates/application.html";
+ var plugin_prefix = "vendor/plugins/blue-ridge/";
+ var fixture_file = plugin_prefix + "generators/blue-ridge/templates/application.html";
load(plugin_prefix + "lib/env.rhino.js");
print(" - loaded env.js");
View
2  lib/test_runner.js
@@ -26,7 +26,7 @@ var fixture = "fixtures/" + spec_file.replace(/^(.*?)_spec\.js$/, "$1.html");
print("Running " + spec_file + " with fixture '" + fixture + "'...");
var RAILS_ROOT_PREFIX = "../../";
-var PLUGIN_PREFIX = RAILS_ROOT_PREFIX + "/vendor/plugins/javascript_testing/";
+var PLUGIN_PREFIX = RAILS_ROOT_PREFIX + "/vendor/plugins/blue-ridge/";
load(PLUGIN_PREFIX + "lib/env.rhino.js");
window.location = fixture;
Please sign in to comment.
Something went wrong with that request. Please try again.