Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Feature Tags -- not always applied #332

Open
eyston opened this Issue · 4 comments

5 participants

Huey Petersen Ivan Ven Osdel Sian Lerk Lau Danielle Madeley Alexander Prudnikov
Huey Petersen
@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.

Ivan Ven Osdel

@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.

Sian Lerk Lau

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

Danielle Madeley
Collaborator

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?

Alexander Prudnikov

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
Something went wrong with that request. Please try again.