Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Format jasmine results as junit compatible XML so CI servers, like Hudson/Jenkins can parse it
Ruby
branch: master
Failed to load latest commit information.
lib bump version to 0.2.1
spec Allow custom config path as environment variable JASMINE_JUNIT_XML_CO…
.gitignore Pull the JUnit XML formatter code out of jasmine-gem.
Gemfile Pull the JUnit XML formatter code out of jasmine-gem.
LICENSE Use Pivotal Labs, not Jasmine for copyright holder
README.md Make output path customizable
Rakefile Pull the JUnit XML formatter code out of jasmine-gem.
jasmine_junitxml_formatter.gemspec

README.md

Jasmine JUnit Xml Formatter Build Status

Format jasmine results as junit compatible XML so CI servers, like Hudson/Jenkins can parse it

Installation

Add this line to your application's Gemfile:

gem 'jasmine_junitxml_formatter'

And then execute:

$ bundle

Or install it yourself as:

$ gem install jasmine_junitxml_formatter

Usage

  • In rails, simply run rake jasmine:ci, tests should generate a JUnit XML file
  • Outside of rails, you may need to add require 'jasmine_junitxml_formatter' to your Rakefile after jasmine is required.

Configuring the output location:

Create a jasmine_junitxml_formatter.yml in spec/javascripts/support with something like this:

---
junit_xml_path: /absolute/path/to/output

The config file will be processed with ERB if you want to make the destination dynamic. e.g.

---
junit_xml_path: <%= File.join(Dir.pwd, 'some', 'relative', 'path')

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request
Something went wrong with that request. Please try again.