A set of API for handling HTML, CSS, JSON, XML and plain text fixtures in your Jasmine specs
Heavily inspired by jasmine-jquery it provides a simple, lean alternative for a smaller set of features jasmineFixtures is designed to work in IE11+ and most recent versions of Chrome, FireFox, Edge and Safari
Either:
- Simply download jasmineFixtures.min.js from here and include it in your Jasmine's test runner file.
- Use Bower
bower install jasmineFixtures
Allows you to read content from the file system to be used by your tests:
In myfixture.txt:
Whatever hereInside your test:
var fixtureStr = jasmineFixtures.read("myfixture.txt");
runMyCodeHere();
expect(myVar).toEqual(fixtureStr);By default, fixtures are loaded from fixtures/.
You can change configuration using: jasmineFixtures.setup({basePath: "newPath/"});.
Note: If you are running your test with Karma, remember that your files are served from a
base/directory, so your path should be configured to:jasmineFixtures.setup({basePath: "base/newPath/"});.
Fixtures are internally cached, so you can load the same fixture file multiple times without affecting your test suite's speed.
The following methods are provided:
-
jasmineFixtures.read(path)Returns the content of the given fixture- CSS fixtures are returned as String
- HTML fixtures are returned as String
- JSON fixtures are returned as Object
- Plain text fixtures are returned as String
- XML fixtures are returned as XMLDocument
-
jasmineFixtures.preload(path[, path, ...])- Pre-loads fixture(s) from one or more files and stores them into cache, without returning them or appending them to the DOM. All subsequent calls will then get fixtures content from cache, without making any XHR calls (unless cache is manually purged by using
jasmineFixtures.clearCache()method).
- Pre-loads fixture(s) from one or more files and stores them into cache, without returning them or appending them to the DOM. All subsequent calls will then get fixtures content from cache, without making any XHR calls (unless cache is manually purged by using
-
jasmineFixtures.clearCache()- Flush/clear the cache
Allows you to load HTML content to be used by your tests:
In myfixture.htm:
<div id="my-fixture">whatever here</div>Inside your test:
jasmineFixtures.loadHTML("myfixture.htm");
runMyCodeHere();
expect($("#my-fixture")).to...The fixture will be loaded into the <div id="jasmine-fixtures"></div> container that is automatically added to the DOM (you can change the configured id using: jasmineFixtures.setup({containerId: "newId"});). The fixtures container is automatically cleaned-up between tests, so you don't have to worry about left-overs from fixtures loaded in preceeding test.
The following methods are provided:
-
jasmineFixtures.appendHTML(path)- Append the content of the given fixture inside the container. Already existing content, if any, is left untouched
-
jasmineFixtures.loadHTML(path)- Load the content of the given fixture inside the container. Already existing content, if any, is removed
-
jasmineFixtures.setHTML(html)- Load the the given HTML, passed as string, inside the container. Without any XHR call. Already existing content, if any, is removed
Allows you to load CSS content on the page while testing.
The fixture will be loaded into the <head></head>
The following methods are provided:
-
jasmineFixtures.appendCSS(path)- Append the content of the given fixture inside the
<head>. Already existing content, if any, is left untouched
- Append the content of the given fixture inside the
-
jasmineFixtures.loadCSS(path)- Load the content of the given fixture inside the
<head>. Already existing content, if any, is removed
- Load the content of the given fixture inside the
-
jasmineFixtures.setCSS(css)- Load the content of the given CSS, passed as string, inside the
<head>. Already existing content, if any, is removed
- Load the content of the given CSS, passed as string, inside the
jasmine-ajax library overrides XMLHttpRequest automatically when jasmine.Ajax.install() is called.
This breaks jasmineFixtures, as its fixture loading mechanism uses XMLHttpRequest, that stops working once the mock is installed.
A workaround for this may be to invoke jasmineFixtures.preload function (specifying all required fixtures) before jasmine-ajax is loaded.
This way subsequent calls to load or read methods will retrieve fixtures content from cache, without need to use XMLHttpRequest and thus will work correctly even after jasmine-ajax is loaded.
As an alternative you can call jasmineFixtures before jasmine.Ajax.install() is invoked.
jasmineFixtures will not load any subresources contained inside the fixtures such as scripts, stylesheets, or iframes.
Take a look at jasmineMatchers