Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Jan 4, 2013
  1. Don't force using rubyracer

Commits on Dec 27, 2012
  1. Merge pull request #34 from eckardt/feature/port_option_for_dev_server

    Adam Hawkins authored
    Add --port option for 'iridium server' command
  2. Merge pull request #35 from tchak/templates-namespacing

    Adam Hawkins authored
    configurable templates namespace
Commits on Dec 26, 2012
  1. @tchak

    configurable templates namespace

    tchak authored
Commits on Dec 20, 2012
  1. Copy HTML files in test/framework

    twinturbo authored
  2. @eckardt
  3. Add app/config/

    twinturbo authored
Commits on Dec 13, 2012
  1. Rewrite requires in config files

    twinturbo authored
Commits on Dec 9, 2012
  1. Add /lib to the pipeline

    twinturbo authored
Commits on Dec 7, 2012
  1. Add regression test for env files

    twinturbo authored
  2. Completely rewrite $ iridium test

    twinturbo authored
    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
    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
    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
Commits on Dec 5, 2012
  1. Test loaders works over http:// or file://

    twinturbo authored
  2. Fix mocha deprecation warnings

    twinturbo authored
  3. Regression test for #33

    twinturbo authored
  4. Merge pull request #33 from eckardt/patch-1

    Adam Hawkins authored
    Fix #32: Running iridium compile with default config/production.rb fails
  5. @eckardt
  6. Generate proper test directory

    twinturbo authored
  7. Fix rake test:pipeline

    twinturbo authored
  8. Optionally compile tests.html and tests.js

    twinturbo authored
  9. Skip rack option parsing

    twinturbo authored
  10. iridium server -e

    twinturbo authored
Commits on Dec 4, 2012
  1. Move internal logging to debug level

    twinturbo authored
  2. Update readme

    twinturbo authored
  3. Document log levels

    twinturbo authored
  4. Remote console log levels

    twinturbo authored
  5. Move logging to console

    twinturbo authored
  6. Include active test name in log

    twinturbo authored
  7. Simple log formatting

    twinturbo authored
  8. OOP-ize logging implementation

    twinturbo authored
  9. Fix tests

    twinturbo authored
  10. Things essentially working

    twinturbo authored
  11. Report file names of bad coffeescript

    twinturbo authored
  12. Refactor logging inside casper

    twinturbo authored
Commits on Nov 26, 2012
  1. Set default task correctly

    twinturbo authored
Something went wrong with that request. Please try again.