TestSwarm with xtras: submodules QUnit, Pavlov, jQuery Mockjax
do
git clone [email protected]:jimmont/testswarm-x.git
git submodule update --init
or if using THIS project as a submodule:
git submodule add [email protected]:jimmont/testswarm-x.git path/to/it
git submodule update --init
cd path/to/it
git submodule update --init
TestSwarm provides distributed continuous integration testing for JavaScript.
The main instance monitoring jQuery core and related projects runs at swarm.jquery.org.
Clone the repo, git clone git:https://github.com/jquery/testswarm.git
, or
download the latest
release.
TestSwarm uses the Semantic Versioning guidelines as much as possible.
Releases will be numbered in the following format:
<major>.<minor>.<patch>
The -alpha
suffix is used to indicate unreleased versions in development.
For more information on SemVer, please visit https://semver.org/.
Found a bug? Please report it using our issue tracker!
To run TestSwarm you will need a web server, a database server and PHP. At the moment TestSwarm only supports Apache and MySQL.
- Apache 2.0+
- PHP 5.3.0+
- MySQL 4.0+
- Curl (for the cleanup action; see below)
-
Set up a MySQL database and create a user with read and write access.
-
Copy
./config/testswarm-sample.json
to./config/testswarm.json
and update the database settings. For other settings, check the wiki. -
Copy
./config/.htaccess-sample
to./.htaccess
.
Currently the only supported webserver is Apache (which uses a.htaccess
file).
To run TestSwarm from a non-root directory, setweb.contextpath
to the correct path from the web root and update RewriteBase in.htaccess
. Verify that.htaccess
is working properly by opening a page (e.g./testswarm/projects
) in your browser. If it doesn't work, make sure your.htaccess
is actually being read (e.g. by putting some jibberish into the.htaccess
file, which should result in a HTTP 500 Error). If it doesn't get loaded, verify thatAllowOverride
is set to "All
" (at least not to "None
") in your Apache configuration. -
Set
storage.cacheDir
to a writable directory that is not readable from the web. Either set it to a custom path outside the web document root, or use the defaultcache
directory (protected with .htaccess).
Chmod it:chmod 777 ./cache
. -
Install the TestSwarm database by running:
php ./scripts/dbInstall.php
-
Copy
./config/robots.txt
to./robots.txt
(or add similar rules to your mainrobots.txt
file if TestSwarm is not in the root directory). -
Create an entry in your crontab for action=cleanup. This performs various cleaning duties such as making timed-out runs available again.
* * * * * curl -s https://swarm.example.org/api.php?action=cleanup > /dev/null
You're welcome to use the GitHub issue tracker to start discussions.
Or post to the QUnit and Testing forum.
Most of us are also on IRC in the #jquery-dev channel at irc.freenode.net
Planning for TestSwarm and other projects related to testing of javascript applications based around jQuery happens on the jQuery Testing Team wiki
See MIT-LICENSE.
TestSwarm was originally created by John Resig as a basic tool to support unit testing of the jQuery JavaScript library. It was later moved to become an official Mozilla Labs and has since moved again to become a jQuery project.