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

Already on GitHub? Sign in to your account

Feature Tags -- not always applied #332

Open
eyston opened this Issue Mar 6, 2013 · 4 comments

Comments

Projects
None yet
5 participants

eyston commented Mar 6, 2013

@login
Feature: I want to be able to login

  Scenario: Logging in as admin
    Given I am on the login page
    When I login as an administrator
    Then I should be on the dashboard page

  Scenario: Logging in as reviewer
    Given I am on the login page
    When I login as a reviewer
    Then I should be on the dashboard page

lettuce -t login will only run the first scenario.

@login
Feature: I want to be able to login

  @foo
  Scenario: Logging in as admin
    Given I am on the login page
    When I login as an administrator
    Then I should be on the dashboard page

  @foo
  Scenario: Logging in as reviewer
    Given I am on the login page
    When I login as a reviewer
    Then I should be on the dashboard page

lettuce -t login will run both scenarios.

So the scenarios themselves seem to require tags for the feature tag to work. But that is just in this case at least.

@eyston We haven't been able to get tags to match at all. See #274. I have tried using your exact tags with our scenarios and no scenarios ever fire. Or conversly, if I tell lettuce to exclude with lettuce -t -login, all of the scenarios fire.

kiawin commented Dec 11, 2013

An interesting observation that I see as I try to recreate the bug is:

  1. If feature is tagged, while scenarios are not tagged - zero scenario under the feature is detected/passed
  2. If feature is tagged, while one of the scenarios is tagged - all scenarios under the feature are detected/passed
Collaborator

danni commented Feb 12, 2014

Interesting to know if this is fixed with the new parser (#429). Can you turn this into a test case and put it in a pull request?

brusco commented Oct 6, 2014

Apparently, this issue was fixed by this commit:
503fe2d

And it can no longer be reproduced in version 0.2.20

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