can actually light up a browser ... and use it inside a spec. oh, and the browser is configured by the config file
chemistry kit wrapper around webdriver
changing the name of the driver facade
run specs in a random order
logging ... logs are created in logs/timestamped_dir and at the end a symlink from logs/latest to the timestamped dir is recreated. its the latest symlink that you point jenkins etc at. also, for windows support it has the side effect of requiring ruby 1.9.2 or newer on that platform. which i dont think is a bad thing really.
ckit will exit with a 0 if everything passed or 1 if something didnt. useful for integration with things like buildbot
Merge remote-tracking branch 'upstream/master'
Merge pull request #4 from adamgoucher/master

Logging, exit status, run specs in random order, ckit wrapper around webdriver, use a real browswer