Junit reporter loses report files

[bayandin]

I use cucumber 2.3.2.
For following examples I took cucumber from the latest master (b781bbf) and features from cucumber-ruby/examples/i18n/en

I run 3 scenario, 1st and 3rd from one feature, 2nd from another one:

features/addition.feature:15 # Add two numbers (outline example : | 20 | 30 | add | 50 |)
features/division.feature      # Regular numbers
features/addition.feature:16 # Add two numbers (outline example : | 2 | 5 | add | 7 |)

Let's go:

bundle exec cucumber --format junit --out junit features/addition.feature:15 features/division.feature features/addition.feature:16
DEPRECATION: Using `should` from rspec-expectations' old `:should` syntax without explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax = :should }` instead. Called from /Volumes/Second/repos/cucumber-ruby/examples/i18n/en/features/step_definitions/calculator_steps.rb:23:in `block in <top (required)>'.

I have 2 reports, it's ok.

$ ls junit/
TEST-features-addition.xml  TEST-features-division.xml

but ...

$ cat junit/*.xml
<?xml version="1.0" encoding="UTF-8"?>
<testsuite failures="0" errors="0" skipped="0" tests="1" time="0.001463" name="Addition">
<testcase classname="Addition" name="Add two numbers (outline example : | 2 | 5 | add | 7 |)" time="0.001463">
  <system-out>
    <![CDATA[]]>
  </system-out>
  <system-err>
    <![CDATA[]]>
  </system-err>
</testcase>
</testsuite>
<?xml version="1.0" encoding="UTF-8"?>
<testsuite failures="0" errors="0" skipped="0" tests="1" time="0.002515" name="Division">
<testcase classname="Division" name="Regular numbers" time="0.002515">
  <system-out>
    <![CDATA[]]>
  </system-out>
  <system-err>
    <![CDATA[]]>
  </system-err>
</testcase>
</testsuite>

... I don't have results for the first one scenario Add two numbers (outline example : | 20 | 30 | add | 50 |) it was overwritten by last one scenario.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.