An add-on for the Jasmine Javascript test framework
Switch branches/tags
Nothing to show
Pull request Compare This branch is 4 commits behind jeffwatkins:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.



jasmine-dom was inspired by the jasmine-jquery add-on for Jasmine JavaScript Testing Framework. This add-on provides a set of custom matchers for working with DOM nodes and an API for handling HTML fixtures in your spec.


This add-on has been separated into two parts: HTML fixtures in jasmine-dom-fixtures.js and the custom DOM matchers in jasmine-dom-matchers.js.

Simply download these files from the downloads page and include them in your Jasmine's test runner file (or add it to jasmine.yml file if you're using Ruby with jasmine-gem).

You can use one or both of these files, depending on your needs.


Fixture module of jasmine-dom allows you to load HTML content to be used by your tests. The overall workflow is like follows:

In myfixture.html file:

some complex content here

Inside your test:

var node=document.getElementById('my-fixture');
// ... call your code with node

Your fixture is being loaded into <div id="jasmine-fixtures"></div> container that is automatically added to the DOM by the Fixture module (If you REALLY must change id of this container, try: jasmine.getFixtures().containerId = 'my-new-id'; in your test runner). To make tests fully independent, fixtures container is automatically cleaned-up between tests, so you don't have to worry about left-overs from fixtures loaded in preceeding test. Also, fixtures are internally cached by the Fixture module, so you can load the same fixture file in several tests without penalty to your test suite's speed.

To invoke fixture related methods, obtain Fixtures singleton through a factory and invoke a method on it:


There are also global short cut functions available for the most used methods, so the above example can be rewritten to just:


Several methods for loading fixtures are provided:

  • load(fixtureUrl[, fixtureUrl, ...])

    Loads fixture(s) from one or more files and automatically appends them to the DOM (to the fixtures container).

  • read(fixtureUrl[, fixtureUrl, ...])

    Loads fixture(s) from one or more files but instead of appending them to the DOM returns them as a string (useful if you want to process fixture's content directly in your test).

  • set(html)

    Doesn't load fixture from file, but instead gets it directly as a parameter. Automatically appends fixture to the DOM (to the fixtures container). It is useful if your fixture is too simple to keep it in an external file or is constructed procedurally, but you still want Fixture module to automatically handle DOM insertion and clean-up between tests for you.

All of above methods have matching global short cuts:

  • loadFixtures(fixtureUrl[, fixtureUrl, ...])
  • readFixtures(fixtureUrl[, fixtureUrl, ...])
  • setFixtures(html)

Also, a helper method for creating HTML elements for your tests is provided:

  • sandbox([{attributeName: value[, attributeName: value, ...]}])

It creates an empty DIV element with a default id="sandbox". If a hash of attributes is provided, they will be set for this DIV tag. If a hash of attributes contains id attribute it will override the default value. Custom attributes can also be set. So e.g.:


Will return:

<div id="sandbox"></div>    


  id: 'my-id',
  class: 'my-class',
  myattr: 'my-attr'

Will return:

<div id="my-id" class="my-class" myattr="my-attr"></div>

Sandbox method is useful if you want to quickly create simple fixtures in your tests without polluting them with HTML strings:

setFixtures(sandbox({class: 'my-class'}));
//  .. run your code

You may also pass a string to sandbox to define your DOM nodes. For example:

var node= sandbox("<span>This is my span...</span>");

When called with a string containing only a single node, sandbox will remove the wrapping DIV it normally creates and just return the inner node. While passing a string with multiple nodes will keep the wrapper.

This method also has a global short cut available:

  • sandbox([{attributeName: value[, attributeName: value, ...]}])

Additionally, two clean up methods are provided:

  • clearCache()

    purges Fixture module internal cache (you should need it only in very special cases; typically, if you need to use it, it may indicate a smell in your test code)

  • cleanUp()

    cleans-up fixtures container (this is done automatically between tests by Fixtures module, so there is no need to ever invoke this manually, unless you're testing a really fancy special case and need to clean-up fixtures in the middle of your test)

These two methods do not have global short cut functions.

Some browsers (Chrome) have difficulty loading fixtures from file:// URLs. It's best to avoid using file URLs and use a web server instead. See Issue 1 for more information.

DOM matchers

jasmine-dom provides following custom matchers (in alphabetical order):

  • toBeChecked(): Tests whether the node has a checked attribute set to true.

      var node= sandbox('<input type="checkbox" checked="checked">');
  • toBeEmpty(): Tests whether the node is empty. A node is only empty if it has no child nodes.

  • toBeHidden(): Tests whether the node is hidden. A node is considered hidden if both its offsetWidth and offsetHeight are 0. This may be caused by a display value of none either on the node or an ancestor node, or because the size of this node has been explicitly set to 0x0.

  • toBeSelected(): For nodes with a selected attribute, this matcher tests whether the attribute is set to true.

      var node= sandbox('<option selected="selected"></option>');
  • toBeVisible(): This matcher is the inverse of toBeHidden. If a node has a dimensions other than 0, it is visible.

  • toContain(selector): Tests whether this node contains nodes that match the selector.

      var node= sandbox("<div><span class="some-class"></span></div>");
  • toExist(): This test is essentially the equivalent to not.toBeNull().

  • toHaveAttr(attributeName, attributeValue): Tests whether the node has an attribute and if specified, whether the attribute has the given value.

  • toHaveClass(className): Test whether the node has the given class name.

      var node= sandbox('<div class="some-class"></div>');
  • toHaveHtml(string): Tests whether the node contains the given HTML. This should work regardless of whether your tags are uppercase or lowercase.

      var node= sandbox('<div><span></span></div>');
  • toHaveId(id): Validates that a node has the specified ID.

      var node= sandbox('<div id="some-id"></div>');
  • toHaveText(string): Like the toHaveHtml matcher, this matcher confirms that the node contains the exact text specified.

      var node= sandbox('<div>some text</div>');
      expect(node).toHaveText('some text')
  • toHaveValue(value): For nodes with a value attribute, this matcher will confirm the node has the given value.

      var node= sandbox('<input type="text" value="some text">');
      expect(node).toHaveValue('some text')
  • toMatchSelector(selector): Test whether the node matches a given CSS selector. This matcher requires a selector engine, however, it will work with the engines present in jQuery, Prototype, and Coherent. In addition, it will work if your browser supports a native implementation of querySelectorAll.

      var node= sandbox('<div id="some-id" class="zebra"></div>');

The same as with standard Jasmine matchers, all of above custom matchers may be inverted by using .not prefix, e.g.:

expect(node).not.toHaveText('other text')