Do you like writing jasmine specs, but find the TrivialReporter underwhelming to look at? I took the standalone runner at https://github.com/jasmine/jasmine/releases and Twitter's bootstrap css at http://twitter.github.com/bootstrap to create jasmine-bootstrap. Here's what it looks like:
Here's what the default jasmine-html.js looks like for comparison:
I kept all the TrivialReporter's css classes and most all of its html structure intact. That way jasmine-bootstrap should work with whatever ci you may have already built around the TrivialReporter.
Does the jasmine-bootstrap reporter change anything else?
- showSkipped and showPassed are now url parameters that persist on suite re-run.
- the spec url parameter is respected by the entire suite, not just by the total number of specs run.
Grab everything in src/ and link to them in your html file:
You could also grab the minified version of bootstrap.css from http://twitter.github.com/bootstrap if you want. Starting the BootstrapReporter is just like starting the TrivialReporter:
Full example is in the test/ directory
Pivotal Labs (jasmine-standalone)
Mark Otto and Jacob Thorton (bootstrap)
Copyright (c) 2012, Sarah Brown
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.