From cf6d26d25fcc530c121b1229f09c316ab6caef19 Mon Sep 17 00:00:00 2001 From: ragaskar Date: Thu, 29 Oct 2009 19:30:31 -0700 Subject: [PATCH] Removing outdated info from README --- README.markdown | 52 ------------------------------------------------- 1 file changed, 52 deletions(-) diff --git a/README.markdown b/README.markdown index 6b7ec68..a6cc6f4 100644 --- a/README.markdown +++ b/README.markdown @@ -458,58 +458,10 @@ Spies have some useful properties: Spies are automatically removed after each spec. They may be set in the beforeEach function. -### Runner - -You don't need a DOM to run your tests, but you do need a page on which to load & execute your JS. Include the `jasmine.js` file in a script tag as well as the JS file with your specs. You can also use this page for reporting. More on that in a moment. - -Here's the example HTML file (in `jasmine/example`): - - - - - Jasmine Example - - - - - -

- Running Jasmine Example Specs -

-
- - - - -It's the call to `jasmine.execute()` that runs all of the defined specs, gathering reports of each expectation. - -### Reports - -If a reporter exists on the Jasmine instance (named `jasmine`), it will be called when each spec, suite and the overall runner complete. If you're at the single-spec result level, you'll get a spec description, whether it passed or failed, and what the failure message was. At the suite & runner report level, you'll get the total specs run so far, the passed counts, failed counts, and a description (of the suite or runner). - -There is a `Jasmine.Reporters` namespace for you to see how to handle reporting. See the file `json_reporter.js`, which takes the results objects and turns them into JSON strings, for two examples of how to make the results callbacks work for you. - - ### Disabling Tests & Suites Specs may be disabled by calling `xit()` instead of `it()`. Suites may be disabled by calling `xdescribe()` instead of `describe()`. A simple find/replace in your editor of choice will allow you to run a subset of your specs. -Contributing and Tests ----------------------- - -Sometimes it's hard to test a framework with the framework itself. Either the framework isn't mature enough or it just hurts your head. Jasmine is affected by both. - -So we made a little bootstrappy test reporter that lets us test Jasmine's pieces in isolation. See test/bootstrap.js. Feel free to use the bootstrap test suite to test your custom Matchers or extensions/changes to Jasmine. - -Your contributions are welcome. Please submit tests with your pull request. - ## Support We now have a Google Group for support & discussion. @@ -525,7 +477,3 @@ We now have a Google Group for support & discussion. * A big shout out to the various JavaScript test framework authors, especially TJ for [JSpec](http://github.com/visionmedia/jspec/tree/master) - we played with it a bit before deciding that we really needed to roll our own. * Thanks to Pivot [Jessica Miller](http://www.jessicamillerworks.com/) for our fancy pass/fail/pending icons * Huge contributions have been made by [Christian Williams](mailto:xian@pivotallabs.com) (the master "spy" coder), [Erik Hanson](mailto:erik@pivotallabs.com), [Adam Abrons](mailto:adam@pivotallabs.com) and [Carl Jackson](mailto:carl@pivotallabs.com), and many other Pivots. - -## TODO List - -* Pending & Disabled counts should be included in results