github-migration/jasmine
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
DOM-less simple JavaScript testing framework
485 Commits 6 Branches 14 Tags 2.3 MiB
JavaScript 96.9%
CSS 1.2%
Ruby 1.1%
HTML 0.8%
222dda4e06
Go to file
John Bintz 222dda4e06 if a spec description is given a function as the description, use its name as the displayed description
2011-06-07 09:50:05 -04:00
example jshint passes - run 'node jshint/run.js'. running jshint with a couple jshint options and workarounds to allow certain jasmine-specific styles. many actual style problems are fixed. the jshint run is integrated into rake jasmine:lint. 2011-02-26 15:07:59 -08:00
images Add png suitable for favicon 2011-05-06 22:40:53 -04:00
jsdoc-template Drop in jsdoc template (from jsdoc-toolkit 2.1.0). 2010-10-05 13:11:04 -07:00
jshint Move all core files into src/core. 2011-06-05 21:28:26 -07:00
lib Revert back to the old jasmine.css 2011-06-05 21:55:51 -07:00
pages@d08ce2de24 How to for release 2011-02-27 14:22:53 -08:00
spec if a spec description is given a function as the description, use its name as the displayed description 2011-06-07 09:50:05 -04:00
src if a spec description is given a function as the description, use its name as the displayed description 2011-06-07 09:50:05 -04:00
.gitignore ignore rvmrc 2011-05-06 18:32:58 -04:00
.gitmodules adding latest pages 2011-02-27 14:00:45 -08:00
cruise_config.rb making jasmine know about ci 2009-12-28 16:45:01 -08:00
Gemfile updating for new pages 2011-02-27 10:36:13 -08:00
Gemfile.lock updating for new pages 2011-02-27 10:36:13 -08:00
HowToRelease.markdown Move all core files into src/core. 2011-06-05 21:28:26 -07:00
MIT.LICENSE README changes 2011-03-09 08:16:47 -08:00
Rakefile Move building single-file JS to use a JSON file with initial priority files 2011-06-05 21:55:32 -07:00
README.markdown More README edits for the Contributor guide 2011-03-09 13:31:03 -08:00

README.markdown

Jasmine

A JavaScript Testing Framework

Jasmine is a Behavior Driven Development testing framework for JavaScript. It does not rely on browsers, DOM, or any JavaScript framework. Thus it's suited for websites, Node.js projects, or anywhere that JavaScript can run.

Documentation & guides live here: http://pivotal.github.com/jasmine/

Support

How to Contribute

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.

Development Environment

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.

How to Develop for Jasmine Core

  • Write specs
  • Make them pass in a browser (or three):
    • open spec/runner.html in your browsers
    • rake spec:browser will run in the default browser on MacOS
  • Make them pass in Node: rake spec:node
  • Fix any warnings or errors from JSHint: rake jasmine:lint

Running 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).

Making a Successful Pull Request

  • 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.

Maintainers

Copyright (c) 2008-2011 Pivotal Labs. This software is licensed under the MIT License.