Skip to content

Latest commit

 

History

History
130 lines (105 loc) · 6.14 KB

TESTING.md

File metadata and controls

130 lines (105 loc) · 6.14 KB

Testing

There are currently three folders for tests, tests-qunit, tests-mocha and tests-polyfill (the latter are also Mocha-based tests, but at present its W3C tests only work in Node).

They can be run through a variety of means as described below.

To properly build the files (lint, browserify, and minify), use npm start or to also keep a web server, run npm run dev (or grunt dev). If you wish to do testing which only rebuilds the browser files, run npm run dev-browser and if only testing Node, run npm run dev-node. But before release, one should run npm run build (or npm run dev).

The tests produce various database files. These are avoided in .gitignore and should be cleaned up if the tests pass, but if you wish to delete them all manually, run npm run clean.

Browser testing

All QUnit-based tests should pass in modern browsers.

All Mocha-based browser tests should pass except for one test having a problem in Firefox.

Automated browser unit testing

Follow all of the steps above to build the project, then run npm test or npm run sauce-qunit (or npm run phantom-qunit or grunt phantom-qunit to avoid using Saucelabs when you have credentials set up as environmental variables) to run the unit tests.

Note that when not running Saucelabs, the tests are run in PhantomJS, which is a headless WebKit browser.

The older PhantomJS version has problems with two tests, however: index.openCursor(range) and IDBObjectStore.openKeyCursor due apparently to a bug with the WebKit browser used in the older PhantomJS implementation (but the tests themselves report as having such problems).

Although it is possible to get the W3C web-platform-tests runner working via patches as per indexeddbshim#249, allowing tests to be run from the runner without obtrusive changes to the repository is not yet refined (see also web-platform-tests/wpt#5133 (comment)).

Manual browser testing

If you want to run the tests in a normal web browser, you'll need to spin-up a local web server and then open tests-qunit/index.html?noglobals and/or tests-mocha/index.html in your browser. You can also run npm run dev and point your browser to http://localhost:9999/tests-qunit/index.html or http://localhost:9999/tests-mocha/index.html.

Note that, for the Mocha tests, you probably wish to "Switch to IndexedDBShim" when doing the testing since otherwise, it will only test the native implementation.

For the W3C web-platform-tests tests, individual tests can be run in two ways.

  1. The first way currently adds files within web-platform-tests but does not modify files. To do this you must run a grunt dev task or another such test that connects (to port 9999) and also follow the instructions to install and run the server at https://github.com/w3c/web-platform-tests. If you run npm run w3c-add-wrap (or npm run w3c-remove-wrap to undo), you will be able to add ".any.html" to an IndexedDB file, e.g., http://web-platform.test:8000/IndexedDB/historical.html becomes http://web-platform.test:8000/IndexedDB/historical.html.any.html.
  2. The second way, unlike the first, allows files to be run from the W3C test runner at http://web-platform.test:8000/tools/runner/index.html, but it involves modifying files within web-platform-tests (you can use git reset to undo, however). You can then run npm run w3c-wrap and run files in the runner or individually. As above, you must also keep the grunt dev task (or the like) running on port 9999 and install web-platform-tests.

Node Testing

To run the Node tests, run the following:

  1. npm run node-qunit - The full test suite sometimes does not complete execution.
  2. npm run mocha
  3. npm run tests-polyfill (or its components npm run fake, npm run mock, npm run w3c-old). Note that only fake is currently passing in full, however.
  4. npm run w3c (you must first run git submodule update --init --recursive (possibly without init too if using an older version of Git), git submodule foreach --recursive git fetch, and git submodule foreach git merge origin master or within Windows git submodule foreach git pull --ff-only origin master). Note that some of these tests may not be passing because of the test environment not being completely configured for Node. We are working on fixing this. There are some older and less complete W3C tests that can be run with npm run w3c-old, but the goal is to remove these once the new ones are configured properly and working in the browser as do the old tests. The W3C Python browser server also ought to be running due to requirements with the URL having permissions.

If you need to rebuild SQLite, you can run npm install inside of the node_modules/sqlite3 directory.

To run a specific Mocha test (which includes the tests-polyfill tests), run npm --test=... run mocha.

Testing in a Cordova/PhoneGap app

(Note that the repository as is might no longer be compatible with Cordova/PhoneGap support. Please let us know if you can try or supply any needed fixes.)

If you want to run the tests in a Cordova or PhoneGap app, then you'll need to create a new Cordova/PhoneGap project, and add the IndexedDB plug-in. Then copy the contents of our tests directory into your project's www directory. Delete our index.html file and rename cordova.html to index.html.