Incorrect number in the Eclipse junit summary #276

Closed
weejulius opened this Issue Mar 27, 2012 · 9 comments

Comments

Projects
None yet
3 participants

Hi,

I have a feature which includes background segment, and as a result the result summary of feature is not correct.

The result should be Runs: 35/35 however what we see is Runs:35/29 and the missed 6 background scenarios go to the Unrooted Tests.

The version is 1.0.0.RC24 and the junit xml is

<?xml version="1.0" encoding="UTF-8"?>
<testrun tests="29" started="35" failures="0" errors="0" ignored="0">
  <testsuite  time="1.123">
    <testsuite name="Feature: crop images" time="1.123">
      <testsuite name="Scenario: crop jpeg" time="0.802">
       ...
      </testsuite>
      <testsuite name="Scenario: invalid parameters" time="0.197">
       ...
      </testsuite>
      <testsuite name="Scenario: crop png" time="0.1">
        ...
      </testsuite>
    </testsuite>
  </testsuite>
  <testsuite name="Unrooted Tests" time="0.131">
   ...
  </testsuite>
</testrun>
Owner

aslakhellesoy commented Mar 27, 2012

You are not saying what version you are using, and your code is unreadable. Please use GFM

I will reopen when you have fixed those 2 problems.

Please reopen it. I have fixed the problems
Also I can reproduce it in the version 1.0.0, you can reproduce if you have background in the feature

Owner

aslakhellesoy commented Mar 27, 2012

Looks like the bug you are mentioning was fixed in 1.0.0. How does that work for you?

https://github.com/cucumber/cucumber-jvm/blob/master/History.md

The issue only happens when there is background in the feature, and it is not resolved using the 1.0.0 as I test

@aslakhellesoy aslakhellesoy reopened this Mar 27, 2012

Owner

aslakhellesoy commented Mar 27, 2012

Thanks for checking. Reopening.

Owner

aslakhellesoy commented Mar 28, 2012

@weejulius can you let me know how the fix in 43ee9c8 works for you? It did fix incorrect reporting in IntelliJ, but I don't have Eclipse handy to verify.

Owner

aslakhellesoy commented Mar 29, 2012

I just tried this fix in Eclipse, and it seems to be working fine there too.

aslakhellesoy added a commit that referenced this issue Mar 29, 2012

Member

dkowis commented Mar 29, 2012

Ah cool. I just ran into this issue today :) I'll be able to verify it in a bit.

I wonder if it's causing a different issue I'm running into, which I'm trying to isolate and debug. (will file if I find it)

awesome, it is fixed

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment