Here you find details about what has changed with each release of Buster.JS.

v0.6.12 (formerly: v0.6.3)

Released 2012-12-22.

Update capture-server and use new implementation, “ramp”. This should vastly improve the stability of the server as well as print proper error messages (and use correct exit codes) when the server is not running or has no connected slaves.

This release also introduces a few of the 1.0-ready modules slated for 0.7, but few user-facing updates.

Breaking changes

No breaking changes in this release.


No additions in this release.

v0.6.11 (formerly: v0.6.2)

Released 2012-12-22.

Minor fix.

Breaking changes

No breaking changes in this release.


No additions in this release.

Bug fixes

  • Exit code was always 1 (#221)

v0.6.2 - v.0.6.10

To be ignored.


Released 2012-07-09.

Buster.JS 0.6.1 is a fairly small maintenance release, mostly correcting a bunch of bugs of minor/medium significance.

Breaking changes

No breaking changes in this release.


Buster.JS 0.6.1 ships with Sinon.JS 1.4.0, a significant update with lots of interesting new features, see Sinon.JS changelog.

Bug fixes

  • Cyclic objects in buster-format (#215)
  • Exit code 1 for wrong arguments (#210)
  • assert.equals and Prototype.js arrays (#206)
  • Focus rocket on test case name (#200)
  • Configure this.timeout in setUp and prepare (#199)
  • Red status line when there are timeouts (#196)
  • Exit code 1 when no tests are run (#195)
  • assert.match with empty strings now passes (#178)
  • Autotest and symlinks (#168)
  • “Too much recursion” when combining stubs and cyclical data structures (#124 and #201)
  • Clean up dangling proxy requests when test run completes (#117)
  • Acknowledge Sinon mock expectations as assertions (#62)
  • posix-argv-parser: Unknown short options “with extras” (i.e. -node) fails with a humanized error message.

v0.6.0 - Buster.JS Beta 4

Released 2012-06-20.

Beta 4 packs a lot of changes, increased stability and new features. Tests written for older versions do not need any syntactical updates, while extensions and other “general API consumers” may.

Documentation is currently lacking. There will be a documentation sprint prior to 1.0, but probably not before the next beta. For planned progress, refer to Roadmap.

Breaking changes

This is a list of breaking changes in this release. Since we haven’t reached 1.0 stable yet, we’re taking the freedom to change APIs without making them backwards compatible in the hope of making them better. There are a few more breaking changes planned for the next (last) beta, see Roadmap.

Naming changes

In an effort to improve navigation in the many Buster.JS modules, we have started renaming some of them, as discussed on the mailing list. These naming changes will only affect you if you are depending on either of these modules in your own projects.

  • buster-resources is now ramp-resources (the capture server will eventually become “ramp”)
  • buster-args is now posix-argv-parser
  • buster-stdio-logger is now stream-logger
  • sinon-buster is now buster-sinon

Command line interface buster-test

--log-all is gone. In Beta 3, Buster.JS would silence log messages for passing tests and this option would show all messages. In Beta 4, Buster.JS shows all messages by default, and silences those from passing tests with --quiet-log.

Deprecated modules

Some modules are no longer needed and will not receive further upgrades:

  • buster-client
  • buster-bayeux-emitter

Extension hooks

Hooks fire in a given order. The beforeRun no longer comes with any arguments. To get hold of the analyzer and configuration objects that used to be passed to it, implement analyze(analyzer) and configure(configuration) (called in that order) in addition.

New features

The main theme of this release is a rewritten and vastly more stable capture server. Significant work has also been put into making it easy to use the server and the related command-line interfaces with any test framework (e.g. it should now be possible to use these tools to create a qunit-test binary that runs QUnit tests over the server).

Command-line interface buster-test

  • --full-stacks disables the stack filter that’s used to hide Buster.JS internals from stack traces.
  • Implementation and API-wise, the buster-test-cli module is now completely test framework-agnostic. The framework sources are injected as an extension in the “binary” script that uses. In other words, the Buster.JS test framework is now just a regular extension to the Buster.JS CLI tools. For an example, see buster-test.

Command-line interface buster-server

This CLI is now backed by a dedicated module that supports skinning and customization.

npm test

All modules now have a working npm test. All modules are also configured with continuous integration on Travis CI, but will need further love to make the setups work nicely on Travis (basically we have some ugly circular dependencies that needs to be done away with).

Analyzer improvements

The analyzer is the object that is used for quality assurance metrics, such as the lint extension.

  • Errors can be objects with either a content or a message property for the error message. Support for message is new.
  • In addition to “OK” and “failed”, the analyzer can now have an “unclean” state, which means it’s passing, but did receive non-fatal warnings or errors.

Autotest improvements

The autotest module has seen significant improvements through Magnar Sveen’s work on fs-watch-tree. The autotest command-line interface itself also received some usability upgrades. Autotest should now work flawlessly on Linux and OSX (Windows unconfirmed at this point).

  • Re-run all tests by tapping Ctrl-C. Hit Ctrl-C twice to stop. Currently only works for buster-autotest, not buster autotest.
  • Screen is cleared between each run.

Ramp resources improvements

  • Don’t put duplicate objects in the cache
  • Individual resources have cacheable: true|false. This means extensions can control cacheability (i.e. repeatability for warnings etc) on a very fine-grained level.
  • Resource Etag changes when adding processors. Avoids caching issues: If an extension is added in a configuration file, the cache manifest would not update. With this change, any extension that adds processors will cause the cache manifest for affected resources to update, avoiding any stale cache lookups.
  • Propagate resource content processor exceptions.
  • Root resources can specify where to insert scripts by adding {{scripts}} to the template contents.
  • Improve error message for missing paths.
  • Path normalization now accounts for Windows paths.
  • Only globbing once for appendLoad and prependLoad.

buster-test improvements (focus rocket!)

  • Focus rocket: Sort of the opposite of a deferred test. Prepend any test name with the focus rocket “=>” and only tests with the rocket will run. See this short screencast on it.

  • The dots reporter tracks elapsed time.

  • buster.testContext is now an event emitter, and:

    buster.testContext.on("create", function () {});

    takes over for:

    buster.testCase.onCreate(function () {});


    buster.spec.onCreate(function () {});


The buster.js configuration file you put in your projects has a strict focus on project-related settings. This means that it intentionally does not support personal preferences like --color dim. This is where ~/.buster.js (or ~/.buster.d/index.js if you prefer) enters. Currently the following settings can be provided:

  • test.releaseConsole. If true, never capture the console.
  • test.quietLog. If true, never print log messages for passing tests.
  • test.color. One of “dim”, “bright” (default) or “none”.

To specify preferences, ~/.buster.js (or (~/.buster.d/index.js) should look like this:

module.exports = {
    "test.color": "dim"
    // More settings as needed

Partial Windows support

Windows support work is ongoing. In this version, Node tests with the buster-test command-line interface is working, while the server and browser automation part is still not quite there. If you need Windows support, please consider chipping in.

Argv parsing

buster-args is now posix-argv-parser and has an overhauled API. Highlights:

  • Support for transforms
  • Support for types
  • New, close-to-stateless API

Various additions

  • buster-core Event emitter: it is now safe to remove a listener inside a listener.
  • buster-core Event emitter: It is now possible to subscribe to all events with one call, obj.on(function (event, data) {});
  • buster-core: Extracted tmpFile method from buster-configuration.
  • buster-format Bug fix: hasOwnProperty issue on IE9.
  • buster-lint: Prevent caching of files containing lint.
  • buster-sinon: callOrder accepts array of spies.


Released 2012-05-04.

Breaking changes

  • TODO Fill out


  • TODO Fill out


  • TODO Fill out


Released 2012-05-02.

Breaking changes

No breaking changes in this release.


  • Allow --config/-c for buster test to accept a comma separated list of configuration files. (#171)
  • Capture browser page displays how many browsers in total are captured.


  • buster-glob requires a newer glob, which solves a problem with same glob patterns in different working directories.
  • Use path.join for cross-platform paths (only partially solved)


Released 2012-04-26.

Breaking changes

No breaking changes in this release.


  • Only log messages (buster.log) for failed tests by default log all with --log-all/-L (#163)
  • Added more detailed information about OS (Sasha Depold, buster-user-agent-parser #1, buster-test-cli #1)


  • assert.same now is compatible with ES Harmony “egal”. assert.equals recognizes NaN as equal to NaN. (#162)

v0.5.0 - Buster.JS Beta 3

Released 2012-04-17.

Breaking changes

This is a list of breaking changes in this release. Since we haven’t reached 1.0 stable yet, we’re taking the freedom to change APIs without making them backwards compatible in the hope of making them better.

  • testLibs removed, testHelpers added (#95)

    This is a simple change of words. testHelpers resonates better with most uses of the property than testLibs. It behaves like before, meaning that e.g. when you run single tests with buster test -t test/my-test.js, everything in testHelpers will still be loaded.

  • Some expectations changed names (#91)

    We’re renaming some expectations, basically to match the expectations in Jasmine. We were already pretty close to their API, and being 1:1 means way easier migration. Some expectations have also been added, you can find them in the “Changes” section below.

    • toBeSameAs is now toBe. Example: expect(true).toBeTruthy()
    • toBeInDelta is now toBeNear, aliased to toBeCloseTo. Example: expect(4.5).toBeCloseTo(4, 0.5)
    • not() is now a property, not a function. Example: expect(false).not.toBeTruthy()
  • Removed assertion

    assert.typeOf was removed in favor of the more specific ones (e.g. assert.isString)

  • buster.env.path is removed

    Use buster.env.contextPath (was also available before beta 3) instead. Note that buster.env.contextPath does not include a trailing slash.


  • buster-autotest works on all platforms where is supported. Autotest is also slightly clever, only running affected tests on each save and running the entire suite when going from red to green.
  • Adding support for JsTestDriver style /*:DOC+=<div>test</div>*/ with the new extension buster-html-doc. This extension can be used both in vanilla buster tests and alongside buster-jstestdriver. (#47)
  • The body of the testbed HTML in browser tests will now reset between each test run. It will not be cleared out entirely, it will be set to what it was initially. Note: this is not yet fixed in buster-static. (#74)
  • Added new expectations toContain, toBeTruthy and toBeFalsy. (#91)
  • Added new assertion contains (#91)
  • Added new CLI option, --release-console, to buster test. Buster now proxies all console loggings to buster.log by default, and you can use this setting to disable it. (#96)
  • Highlighting uncaught exceptions with colors to make them stand out. (#105)
  • The reporters now let you know if a timeout happened in setUp, tearDown or in the test itself. (#12)
  • Proper exit codes for failing tests and other error situations (buster test) (#81)


  • Fixed some bugs in server proxying for browser tests (#57)
  • Browser tests now fail when a test times out when there are successful tests in the same test run. (#77)
  • Browser tests now fail when there’s no assertions in a test. (#69)
  • buster.log(function(){}); would log undefined, as it called the function because of internals in buster-evented-logger. It no longer calls the function, and logs what you’d expect it to log. (#94)
  • Asserts are now counted properly in the JsTestDriver extension. (#49, #31)
  • At some point in time, an unknown change fixed a small problem with assert.calledOnce. Nobody knows what, where and why. (#70)
  • No longer running setUp/tearDown for deferred tests. (#107)
  • Chrome no longer periodically reloads the entire slave frameset when the tab is in the background. (#84)
  • Browser tests fail properly when there’s no assertions in a test. (#69)
  • buster-static now properly made available when installing buster (#43)
  • Supporting "// deferred tests" in the BDD syntax as well. (#55)
  • Removing the use of Array.some and Object.create in browser code, for old browser compat. (#121, #120)
  • extends on config groups now also copy extensions and other custom configurations. (#100)
  • Failing assertions are counted as assertions by the test runner. (#87)
  • Only installing one version of Sinon. (#14)
  • toBeCalledWith expectation now works when the stub/spy is called multiple times. (#82)
  • Properly counting assertions in buster-jstestdriver. (#49)
  • Making jstestdirver.jQuery available in buster-jstestdriver. (#48)
  • Now failing for non-existant files in the config file. (#78)
  • Status code is now non-zero when buster test fails with test errors etc. (#81)
  • Dot reporter wraps lines. (#32)
  • No longer warning with syntax error for files where the last line is a comment. (#144)
  • Fixing assert.exception failures causing stack overflows. (#63)
  • Logging a function no longer logs "undefined". (#94)
  • XML reporter now reports uncaught exceptions. (#134)
  • Dots reporter wraps lines when they become too long
  • Uncaught exceptions does not print overlapping with dots
  • Proper support for asynchronous test cases/specs (#15)

v0.4.0 - Buster.JS Beta 2

Released 2012-02-21.

This is a brief (i.e. not exhaustive) overview of changes from Beta 1. Beta 2 introduces quite a few fundamental refactorings and rewrites, and is significantly closer to a stable 1.0 release than its predecessor.

With Beta 2, we’ve entered a more rapid iterative development and release cycle. In the four days since the initial release, three patch updates have already been shipped. “Beta 2” refers to Buster.JS version 0.4.1 or newer, until we decide to do a release candidate (or another major beta, if necessary).


Please report as many issues as you can, and consider contributing docs or file feature requests so we can improve documentation. Docs are behind on some things, but we’re working on it.

Breaking change: Config files can no longer read files outside of rootPath

Since we haven’t reached 1.0 stable yet, we’re changing APIs without making them backwards compatible.

Configuration file loading is revamped (most importantly, buster-resources was completely rewritten).

sources, tests, etc can no longer contain paths outside the root path. The root path defaults to the path the configuration file is in. You can also provide the rootPath property in the configuration file to base the project outside the directory where the configuration file is located.

config["My tests"] = {
    sources: ["../src/**/*.js"], // Will not work!
    tests: ["**/*-test.js"]
config["My tests"] = {
    rootPath: "../", // Will work (or just move the config file up one folder)
    sources: ["src/**/*.js"],
    tests: ["tests/**/*-test.js"]


  • Stronger Node.JS inferences across the board.
  • Capture server: significant refactor. “Clients” are now “slaves” and several URLs have changed.
  • Configuration file can now load extensions. A few are already availble, and others, like buster-amd (#15) and coverage is right around the corner.
  • buster-promise is now deprecated and will not receive further updates. We recommend the wonderful when.js instead-it’s what we use.
  • Buster now syntax checks files before attempting to run tests in browsers. This ensures a stable environment with good feedback, regardless of target browser.
  • The test runner was rewritten. It now supports per-test timeouts, the done callback can be used to wrap functions (“we’re done when this function is called”), asynchronous testCase and describe, and TeamCity reporter.
  • The test runner now has a system for including other measures in a test run, issuing warnings, or even preventing tests from running at all. The first external tool included in this system is buster-lint. Expect more thorough documentation of this system as it evolves.

v0.3.0 - Buster.JS Beta 1

The beta is upon us!

See getting started and the overview for usage, installation, features, etc.

So far we have QUnit style static html page testing, JsTestDriver style browser automation, and node testing. We have stubbing and mocking, setUp and tearDown, asynchronous tests, hybrid browser/Node tests, and much more.

We don’t have a super stable 1.0 that you can connect to a zillion old browsers to and have it run in a stable fashion in your CI environment. Getting there requires field testing, and that’s where you come in.

You will run into issues, and when you do, we want to know about them. Please don’t hesitate posting issues in the issue tracker.

See also mailing list, #buster.js at, and @buster_js at Twitter.

Known issues

IE7 and lower, and Safari, doesn’t work with buster server. You can still use buster static to run your tests in these browsers.


  • Running browser tests without a browser and a server via PhantomJS
  • Stability for CI environments etc.
  • ...and more. This list is incomplete.