rspec_junit_formatter
rspec_junit_formatter copied to clipboard
RSpec results that your CI can read
Fixes #56 ## Example ### Before ### After ## Note There is a minor change to how backtraces are formatted. It’s now the same as what `rspec` shows when ran...
Fix https://github.com/sj26/rspec_junit_formatter/issues/56
My test suite fails with error when trying to encode hostname: ``` .../rspec_junit_formatter-0.4.1/lib/rspec_junit_formatter.rb:173:in `encode': "\\xE2" from ASCII-8BIT to UTF-8 (Encoding::UndefinedConversionError) ``` ``` irb(main):003:0> Socket.gethostname => "timofei.kovalev\xE2\x80\x99s-MacBook-Pro" irb(main):004:0> Socket.gethostname.encoding => #...
Given a file: spec/units/test.rb: RSpec.describe TestTests do describe 'Test1' do sleep(30) end describe 'Test2' do sleep(45) end end and spec/units/test3.rb: RSpec.describe TestTests3 do describe 'Test3' do sleep(57) end end Jenkins...
RSpec 3.3 allows to group multiple failures using aggregrate_failures, but formatter doesn't not handle it. It just puts ``` ./spec/sample_test.rb:4:in `block (2 levels) in <top (required)>' ``` when RSpec output...
Hey, here's [a nice thing I found in other open-sourced gem `knapsack`](https://github.com/KnapsackPro/knapsack/blob/master/lib/knapsack/config/env.rb#L13-L15) ``` def ci_node_index gitlab_ci_node_index || ENV['CI_NODE_INDEX'] || ENV['CIRCLE_NODE_INDEX'] || semaphore_job_index || semaphore_current_thread || ENV['BUILDKITE_PARALLEL_JOB'] || snap_ci_worker_index || ENV['BITBUCKET_PARALLEL_STEP']...
This is just TimAle's PR https://github.com/sj26/rspec_junit_formatter/pull/58 on top of latest code. --- Noting that the test suite fails with interesting breaks _for some versions_.
This PR adds a configuration to tell Dependabot to update the versions used for some well-known GitHub Actions, such as `checkout`, in order to avoid deprecation warnings when those get...
It seems that when tests print an emoji in the failure reason rspec_junit_formatter fails and prints the xml its already generated to that point which ends up being invalid because...
This will fix Issue #56 and was heavily inspired by #74 and all credit for the specs go to @jasoncodes It outputs the `exception.message` in the case of a `RSpec::Expectations::MultipleExpectationsNotMetError`....