zotero/test/content/runtests.html

<!DOCTYPE html>
<html>
<head>
	<meta charset="utf-8"></meta>
	<title>Zotero Unit Tests</title>
</head>
<body>
	<script src="chrome://zotero/content/include.js"></script>
	<script src="resource://zotero-unit/chai.js"></script>
	<script src="resource://zotero-unit/chai-as-promised.js"></script>
	<script src="resource://zotero-unit/mocha.js"></script>
	<script src="resource://zotero-unit/co-mocha.js"></script>
	<script src="resource://zotero-unit/sinon.js"></script>
	<script src="resource://zotero-unit/pako_inflate.js"></script>
	<script src="support.js" type="application/javascript"></script>
	<script src="runtests.js" type="application/javascript"></script>
</body>
</html>
Switch back to @mozilla.org/browser/clh;1 and fix tests In Firefox 102, `-file` was being swallowed by `nsBrowserContentHandler` in BrowserContentHandler.jsm, so ab7d916e0 overrode that by using the same contract id for our main nsICommandLineHandler in zotero-service.js. But `nsBrowserContentHandler` also handles `-chrome`, which we were using in tests to pass runtests.html. There's no need to pass in dynamically though -- we can just hard-code that and open the window ourselves. 2023-05-24 06:50:34 -04:00			`<!DOCTYPE html>`
Unit testing infrastructure Implements the beginnings of unit testing infrastructure using mocha/chai. The unit tests can be run locally using test/runtests.sh, although this will need tweaks to run on Windows. They should also run on commit using Travis-CI. The unit tests themselves live in test/tests. The index.js file specifies separate test sets, which can be run individually by calling test/runtests.sh <testsets>. Right now there is only a single unit test, but hopefully we'll have more soon... 2015-03-07 12:18:27 -05:00			`<html>`
			`<head>`
			`<meta charset="utf-8"></meta>`
			`<title>Zotero Unit Tests</title>`
			`</head>`
			`<body>`
			`<script src="chrome://zotero/content/include.js"></script>`
Fixes and tweaks to make tests work with babelized code * Use mocha, chai & sinon from the npm. As of sinon 2.0 sinon-as-promised is no longer required so it is removed * Tweak code to re-use the same loader with the same environment throghout the code * Introduce browserify step for testing tools that only provide node-compatible libraries (sinon, chai-as-promised) * Introduce copy step for test data to resolve multiple issues with tests depending on files not being symlinks * Re-introduce custom implementation of setTimeout to resolve issues with few tests * Re-introduce custom Bluebird Promises config & monkey patch 2017-05-31 16:28:47 +01:00			`<script src="resource://zotero-unit/chai.js"></script>`
			`<script src="resource://zotero-unit/chai-as-promised.js"></script>`
			`<script src="resource://zotero-unit/mocha.js"></script>`
Support generators in tests via coMocha, instead of custom code * coMocha offers better error stack trace 2017-05-31 16:30:56 +01:00			`<script src="resource://zotero-unit/co-mocha.js"></script>`
Add Sinon mock framework for tests 2015-05-07 14:15:55 -04:00			`<script src="resource://zotero-unit/sinon.js"></script>`
Gzip-compress API uploads larger than 1000 characters 2016-03-28 02:35:27 -04:00			`<script src="resource://zotero-unit/pako_inflate.js"></script>`
Fx60: Remove versioned JavaScript 2018-02-24 04:50:37 -05:00			`<script src="support.js" type="application/javascript"></script>`
			`<script src="runtests.js" type="application/javascript"></script>`
Unit testing infrastructure Implements the beginnings of unit testing infrastructure using mocha/chai. The unit tests can be run locally using test/runtests.sh, although this will need tweaks to run on Windows. They should also run on commit using Travis-CI. The unit tests themselves live in test/tests. The index.js file specifies separate test sets, which can be run individually by calling test/runtests.sh <testsets>. Right now there is only a single unit test, but hopefully we'll have more soon... 2015-03-07 12:18:27 -05:00			`</body>`
			`</html>`