Closed zephyr-dev closed 11 years ago
We are in the process of removing dependencies from the Jasmine gem. RSpec is one of those dependencies.
For CI, you'll probably want to use the JUnit XML Formatter we added.
To be clear, it's intended that rake jasmine:ci returns a proper exit code, it's just that we'll no longer depend on rspec to help us generate that code. We have a bug for this issue here: https://www.pivotaltracker.com/story/show/54005119.
In the meantime, if you need Jenkins or Teamcity to fail, as JR suggests it sounds like you can configure jasmine to use the JUnit XML formatter by updating your jasmine_helper.rb such that it reads:
Jasmine.configure do |config|
config.formatters = [Jasmine::Formatters::JUnitXml]
end
Local rake tasks won't return proper exit codes until the bug is fixed.
We are using 56ca703 of jasmine-gem with 18c3056 of jasmine (core) with our Rails 4 application.
Jasmine reports failures, and we see them in the output, but they do not get propagated to the RSpec layer, which always reports zero failures out of zero examples.
We noticed that this commit stops calling into RspecFormatter: cdcb1a9
And that this commit removes RspecFormatter entirely: 2b240c4
When we run
rake jasmine:ci
in our Rails project, we get this output:What are the plans for
rake jasmine:ci
? For now, it doesn't return a useful status code.