Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IDEA test results tree #181

Closed
trnl opened this issue Jan 27, 2012 · 5 comments
Closed

IDEA test results tree #181

trnl opened this issue Jan 27, 2012 · 5 comments

Comments

@trnl
Copy link
Contributor

trnl commented Jan 27, 2012

If running tests with cucumber-junit via idea, background steps results have invalid locations in tree

A.feature

Feature: Feature A
  Some text

  Scenario: A.Scenario 1
    When a
    Then c

  Scenario: A.Scenario 2
    When c
    Then a

B.feature

Feature: Feature B
  Some text

  Background:
    Given a
    When b
    Then c

  Scenario: B.Scenario 1
    When a
    Then c

  Scenario: B.Scenario 2
    When c
    Then a

screenshot

@aslakhellesoy
Copy link
Contributor

Although #211 was reported after this ticket it contains more info to fix this bug, so I'm closing this as a dupe. Thanks for the detailed report!

@gisode
Copy link
Contributor

gisode commented Feb 21, 2012

Maybe I'm mistaken, but isn't the problem here that the background steps appear outside the Feature/Scenario/Step hierarchy? I have the same phenomenon in Eclipse, but I'm not sure what the expected behaviour is here.

I would like background steps to appear within each scenario to which they apply, before any of the scenario-specific steps. If this is indeed the expected behaviour then this issue constitues a bug (independent from #211) because even though steps in a CucumberBackground are not reported to JUnit via the Runner.getChildren() method, they are reported on via the JUnitReporter, creating "unrooted test" reports in Eclipse and presumably the report as shown above in IDEA.

If background steps are not supposed to appear in the report at all (as was the case in previous versions of cucumber-jvm), then the bug is that they get reported on via the JUnitReporter. In that case I'd also ask why they should not appear, since hiding them confuses the user because they are executed after all.

I hope I made myself clear. So what is the expected behaviour here?

@maximilian-novikov-db
Copy link

the original bug is reproduced in cucumber-jvm 1.1.5

@gkushang
Copy link

I face the same issue in cucumber-jvm 1.1.5

@lock
Copy link

lock bot commented Oct 25, 2018

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.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants