Documentation & guides live here: http://pivotal.github.com/jasmine/
- Search past discussions: http://groups.google.com/group/jasmine-js
- Send an email to the list: firstname.lastname@example.org
- Check the current build status: ci.pivotallabs.com
- View the project backlog at Pivotal Tracker: http://www.pivotaltracker.com/projects/10606
- Follow us on Twitter: @JasmineBDD
We welcome your contributions - Thanks for helping make Jasmine a better project for everyone. Please review the backlog and discussion lists (the main group - http://groups.google.com/group/jasmine-js and the developer's list - http://groups.google.com/group/jasmine-js-dev) before starting work - what you're looking for may already have been done. If it hasn't, the community can help make your contribution better.
Jasmine Core relies on Ruby for executing the test suite and building the project for release. The spec suite runs in any major, modern browser (Firefox, Safari, Chrome, and yes various IE's) and in Node.js. While you probably have browsers installed, you want to make sure that Ruby and Node are present.
- Write specs
- Make them pass in a browser (or three):
spec/runner.htmlin your browsers
rake spec:browserwill run in the default browser on MacOS
- Make them pass in Node:
- Fix any warnings or errors from JSHint:
rake spec will run the browser tests, then run specs in Node, then run JSHint. But this will only run in the default browser and only on MacOS (for now).
- Include specs for your work - it helps us understand your intent and makes sure that future development doesn't break your work
- Ensure the full test suite is green in all the big browsers, Node, and JSHint - your contribution shouldn't break Jasmine for other users
Do these things and we'll take a look.
Copyright (c) 2008-2011 Pivotal Labs. This software is licensed under the MIT License.