Iridium test now uses phantom as the secondary tool instead of primary tool. The asset pipeline compiles your tests for you. Enable this by setting `config.pipeline.compile_tests = true` in the environment file. This will create `site/tests.html`, `site/tests.js` and `site/tests.css`. You can open these files either through the dev server or simply via the file system. These test files are designed to run in the browser or via phnatom. This is different than before since the tests could only run (easily) via phantom. The phantom runner was needlessly complex and prone to problems in complex suites. This change also makes Iridium test framework agnostic. A new directory is added. `test/framework` contains all the js/css/html needed to load up your tests. So dump qunit/jasmine what have you in this directory. The support directory works the same. Here's the current directory structure: test/framework: holds all the files to run tests test/framework/loader.html.erb: The template to generate tests.html from test/support: JS/CS files here are compiled and loaded after files in test/framework This commit also introduces the `--test-framework` option to `$ iridium g app`. You can use `jasmine` or `qunit`. `$ iridium test` will fire up phantom and open `site/tests.html` in the brwoser. It will detect if you're using qunit or jasmine and act accordingly.