Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

A way to automate the running of your Screw.Unit specs.

branch: master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 bin
Octocat-spinner-32 js
Octocat-spinner-32 lib
Octocat-spinner-32 spec
Octocat-spinner-32 .gemified
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .manifest
Octocat-spinner-32 LICENSE
Octocat-spinner-32 README.textile
Octocat-spinner-32 Rakefile
Octocat-spinner-32 screw-driver.gemspec
README.textile

Screw.Driver

Another way to run your Screw.Unit tests.

INSTALL

To build the gem, run this:

gemify -I

View the CI build

ABOUT

Still really early. To try it, run this:

./bin/screwdriver spec/fixtures/suite.html

You can specify a browser like so:

screwdriver spec/fixtures/suite.html —browser Safari

By default, Screw.Driver uses Firefox.

If you don’t want the server to automatically quit after
your suite runs, you can use the “—server” option:

screwdriver spec/fixtures/suite.html —server

Screw.Driver will generate urls for each of the external
scripts and CSS links you include in your suite.html file,
and will serve them from the directory that contains the
suite.html file.

To specify additional load paths for your JavaScripts, you can
use the “—load-paths” option:

screwdriver spec/fixtures/suite.html —load-paths src/

Using with Rails

If you’re using Rails, run screwdriver from the root directory
of your app, and specify the “—rails” option. This will cause
the Screw.Driver server to serve the JavaScript files in your
public/javascripts directory. Example:

screwdriver spec/fixtures/suite.html —rails

REQUIREMENTS
- sinatra
- hpricot
- gemify (to build)

TODO
- Inject base tag into DOM at Hpricot parsing stage
- Convert script src attributes to absolute paths at Hpricot parsing stage
- Don’t kill all Firefox tabs when complete
- Use #load_paths for Rails functionality

Something went wrong with that request. Please try again.