rspec_junit 3.0.4 → 4.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: f729b0494c3aeecd11d3bf5a6df48052686c84ba
-  data.tar.gz: 264c0d89a7bf1f80679b00692e399d664cc6ccf1
+  metadata.gz: e43ef7ad781d8ba058f77fbced8755906da35d65
+  data.tar.gz: 03614b03d2423135aea6846c73e35d5d88adc733
 SHA512:
-  metadata.gz: ad33e37b9f91f2cf934efb758e8f9cb7182464f2775816f5dc7b9cf580e2291920a0beea2f9918ac269a96b1760a6e820030816cb3b01d09146f2c4c091e51e8
-  data.tar.gz: 2ad58ed53cd96daf6afa73f873a3f7b2dff05e68d65b9e74e4fd0e44f9ae5ebc2ffbaee77f6602a52739a928fb1dedf7f9087cfa3197712383cdb55851c45956
+  metadata.gz: f82b82195be87fbc8bc7d437cadd9285a6b2f288526c0c5e33783bb12c73302b74bb7616fbbf0956b3ebd2009f3b69e2ca597d05867ef8c4146367789821d3e3
+  data.tar.gz: ecc2a0602bbbff9437d1e419cea03a1310e927bc4a9f4ff8bda4c277e52ef6792bd4dd4dc25069d6271a8baa55209c0dce7ef2f92390f44444dde4eccc28f105

data/.rspec

@@ -1,5 +1,5 @@
 --color
 --require spec_helper
---format JUnit
+--format RSpecJUnit
 --out tmp.xml
 --format progress

data/README.md

@@ -6,26 +6,31 @@
 A fork of [yarjuf](https://github.com/natritmeyer/yarjuf) containing additional features and bug fixes.
 Another popular junit formatter is [rspec_junit_formatter](https://github.com/sj26/rspec_junit_formatter).
 
---
-
-Changes from upstream:
+## Usage
 
-- [Record location information](https://github.com/natritmeyer/yarjuf/pull/18) for per file performance measurement
-- Coveralls setup on Travis CI (100% coverage)
-- Renamed to rspec_junit instead of yarjuf               
-               
-Usage:
+```ruby
+# spec_helper.rb
+require 'rspec_junit'
 
-- `require 'rspec_junit'`
+RSpec.configure do |config|
+  config.before(:suite) do
+    # Must register the formatter here and not in an options file. The options
+    # file uses the master process pid and globs all the xml files into one
+    # instead of the worker pids which output to individual files.
+    config.add_formatter RSpecJUnit, "junit_#{Process.pid}.xml"
+  end
+end
+```
 
+## Sauce Labs Jenkins notes
 
-```
-$ cat .rspec
---require rspec_junit
---format documentation
---format JUnit
---out ./junit/junit_<%= Process.pid %>.xml
-```
+- If the values for `Job Name	OS/Browser	Pass/Fail	Job Links` aren't autopopulated, ensure that
+  the Sauce username and API key have been provided to the Sauce Plugin. Under
+  **Sauce Labs Options** in the job configure menu check `Override default authentication`
+  and then provide the user and access key.
+- If the JUnit results report doesn't auto link to Sauce Labs jobs, ensure that
+  the **Post-build Actions** lists **Publish JUnit test results report** as the first action
+  and that **Run Sauce Labs Test Publisher** is after the JUnit action.
 
 --
 

data/features/basic.feature

@@ -14,11 +14,11 @@ Feature: Basic use of Yarjuf
       """
 
   Scenario: Requiring Yarjuf
-    When I run `rspec spec/basic_spec.rb -r ../../lib/rspec_junit -f JUnit`
+    When I run `rspec spec/basic_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit`
     Then the exit status should be 0
 
   Scenario: Writing output to a file
-    When I run `rspec spec/basic_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/basic_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the exit status should be 0
     And a file named "results.xml" should exist
 

data/features/individual_suites.feature

@@ -20,7 +20,7 @@ Feature: Individual suites
         end
       end
       """
-    When I run `rspec spec/suite_one_spec.rb spec/suite_two_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/suite_one_spec.rb spec/suite_two_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output file contains two testsuite elements named 'suite one' and 'suite two'
     And the junit output file has one test against each suite
 
@@ -76,7 +76,7 @@ Feature: Individual suites
         end
       end
       """
-    When I run `rspec spec/suite_one_spec.rb spec/suite_two_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/suite_one_spec.rb spec/suite_two_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output file contains two testsuite elements named 'suite one' and 'suite two'
     And the junit output file has the correct test counts against each suite
 

data/features/individual_tests.feature

@@ -12,7 +12,7 @@ Feature: Individual Tests
         end
       end
       """
-    When I run `rspec spec/simple_test_name_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/simple_test_name_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output file contains a test result with a simple name
 
   Scenario: Nested tests
@@ -32,7 +32,7 @@ Feature: Individual Tests
         end
       end
       """
-    When I run `rspec spec/nested_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/nested_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output file has a nicely rendered nested test name
 
   Scenario: Test duration
@@ -44,7 +44,7 @@ Feature: Individual Tests
         end
       end
       """
-    When I run `rspec spec/test_duration_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/test_duration_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output file contains a test with a duration
 
   Scenario: Pending test
@@ -57,7 +57,7 @@ Feature: Individual Tests
         end
       end
       """
-    When I run `rspec spec/pending_test_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/pending_test_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output file contains a pending test
 
   Scenario: Failing test
@@ -69,6 +69,6 @@ Feature: Individual Tests
         end
       end
       """
-    When I run `rspec spec/failing_test_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/failing_test_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output file contains a failing test
 

data/features/suite_level_details.feature

@@ -12,7 +12,7 @@ Feature: Suite Summary
         end
       end
       """
-    When I run `rspec spec/suite_element_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/suite_element_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output contains the testsuite element
 
   Scenario: One passing test
@@ -24,7 +24,7 @@ Feature: Suite Summary
         end
       end
       """
-    When I run `rspec spec/one_passing_test_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/one_passing_test_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output reports one passing test
 
   Scenario: One failing test
@@ -36,7 +36,7 @@ Feature: Suite Summary
         end
       end
       """
-    When I run `rspec spec/one_failing_test_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/one_failing_test_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output reports one failing test
 
   Scenario: One pending test
@@ -49,7 +49,7 @@ Feature: Suite Summary
         end
       end
       """
-    When I run `rspec spec/one_pending_test_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/one_pending_test_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output reports one pending test
 
   Scenario: Test suite duration
@@ -61,7 +61,7 @@ Feature: Suite Summary
         end
       end
       """
-    When I run `rspec spec/suite_duration_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/suite_duration_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output testsuite element contains a duration
 
   Scenario: Test suite time stamp
@@ -73,6 +73,6 @@ Feature: Suite Summary
         end
       end
       """
-    When I run `rspec spec/suite_timestamp_spec.rb -r ../../lib/rspec_junit -f JUnit -o results.xml`
+    When I run `rspec spec/suite_timestamp_spec.rb -r ../../lib/rspec_junit -f RSpecJUnit -o results.xml`
     Then the junit output testsuite element contains a timestamp
 

data/lib/rspec_junit.rb

@@ -7,5 +7,5 @@ require 'rspec/core/formatters'
 require 'rspec/core/formatters/base_formatter'
 
 # internal dependencies
-require 'rspec_junit/junit'
+require 'rspec_junit/rspec_junit'
 require 'rspec_junit/version'

data/lib/rspec_junit/{junit.rb → rspec_junit.rb}

@@ -1,6 +1,6 @@
 # RSpec formatter for generating results in JUnit format
 # Inherit from BaseFormatter like the JSON rspec-core formatter.
-class JUnit < RSpec::Core::Formatters::BaseFormatter
+class RSpecJUnit < RSpec::Core::Formatters::BaseFormatter
   RSpec::Core::Formatters.register self, :example_passed, :example_failed,
                                    :example_pending, :dump_summary,
                                    :close
@@ -42,7 +42,7 @@ class JUnit < RSpec::Core::Formatters::BaseFormatter
   protected
 
   def add_to_test_suite_results(example_notification)
-    suite_name                      = JUnit.root_group_name_for example_notification
+    suite_name                      = RSpecJUnit.root_group_name_for example_notification
     @test_suite_results[suite_name] = [] unless @test_suite_results.keys.include? suite_name
     @test_suite_results[suite_name] << example_notification.example
   end
@@ -55,7 +55,11 @@ class JUnit < RSpec::Core::Formatters::BaseFormatter
       backtrace = RSpec::Core::BacktraceFormatter.new.format_backtrace exception.backtrace
       backtrace = "\n#{backtrace.join("\n")}"
     end
-    "\n#{exception.class.name}\n#{exception.message}#{backtrace}"
+    sauce_test_link = example.metadata[:sauce_test_link]
+
+    result = "\n#{exception.class.name}\n#{exception.message}#{backtrace}"
+    result += "\n\n#{sauce_test_link}" if sauce_test_link
+    result
   end
 
   # utility methods
@@ -90,8 +94,8 @@ class JUnit < RSpec::Core::Formatters::BaseFormatter
   end
 
   def build_test_suite(suite_name, tests)
-    failure_count = JUnit.count_in_suite_of_type(tests, :failed)
-    skipped_count = JUnit.count_in_suite_of_type(tests, :pending)
+    failure_count = RSpecJUnit.count_in_suite_of_type(tests, :failed)
+    skipped_count = RSpecJUnit.count_in_suite_of_type(tests, :pending)
 
     @builder.testsuite(
       location: tests.first.example_group.location,

data/lib/rspec_junit/version.rb

@@ -1,4 +1,4 @@
 module RspecJunit
-  VERSION = '3.0.4' unless defined? ::RspecJunit::VERSION
-  DATE    = '2015-10-15' unless defined? ::RspecJunit::DATE
+  VERSION = '4.0.0' unless defined? ::RspecJunit::VERSION
+  DATE    = '2015-10-16' unless defined? ::RspecJunit::DATE
 end

data/spec/formatter_conformity_spec.rb

@@ -1,9 +1,9 @@
 require_relative 'spec_helper'
 
-describe JUnit do
+describe RSpecJUnit do
   context 'interface conformity' do
 
-    subject { JUnit.new 'some output' }
+    subject { RSpecJUnit.new 'some output' }
 
     it 'should respond to example passed' do
       should respond_to :example_passed

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: rspec_junit
 version: !ruby/object:Gem::Version
-  version: 3.0.4
+  version: 4.0.0
 platform: ruby
 authors:
 - Nat Ritmeyer
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-10-15 00:00:00.000000000 Z
+date: 2015-10-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -221,8 +221,8 @@ files:
 - features/suite_level_details.feature
 - features/support/env.rb
 - lib/rspec_junit.rb
-- lib/rspec_junit/junit.rb
 - lib/rspec_junit/merged_xml.rb
+- lib/rspec_junit/rspec_junit.rb
 - lib/rspec_junit/version.rb
 - rspec_junit.gemspec
 - spec/fake_foreach_patch.rb