Module Expr Str ImportFrom alias ImportFrom alias alias alias ImportFrom alias alias ImportFrom alias alias ImportFrom alias alias FunctionDef arguments args NameParam defaults body Expr Str Assert AttributeLoad NameLoad attr Str Expr Call AttributeLoad AttributeLoad NameLoad attr attr AttributeLoad NameLoad attr Assign NameStore Call NameLoad Assign AttributeStore NameLoad attr Call AttributeLoad NameLoad attr AttributeLoad NameLoad attr decorator_list Call NameLoad Str FunctionDef arguments args NameParam NameParam defaults body Pass decorator_list Call NameLoad Str FunctionDef arguments args NameParam defaults body Expr Str Assert AttributeLoad NameLoad attr Str Assert AttributeLoad NameLoad attr Str Expr Call AttributeLoad AttributeLoad NameLoad attr attr ListLoad Str Str Assign NameStore AttributeLoad NameLoad attr For TupleStore NameStore NameStore Call NameLoad AttributeLoad AttributeLoad NameLoad attr attr body Assign NameStore SubscriptLoad NameLoad Index Str Assign NameStore Call NameLoad SubscriptLoad NameLoad Index Str Expr Call NameLoad NameLoad NameLoad Assign TupleStore NameStore NameStore Call NameLoad NameLoad Assign NameStore ListComp AttributeLoad NameLoad attr comprehension NameStore NameLoad Expr Call NameLoad NameLoad Call NameLoad NameLoad BinOpMod Str TupleLoad NameLoad NameLoad decorator_list Call NameLoad Str
N/A N/A 
Provides step definitions that test tag logic for selected features, scenarios.

.. code-block:: Gherkin

    # -- Scenario: Select scenarios with tags
    Given I use the behave model builder with:
        | statement  | name   | tags      | Comment |
        | Scenario   | A1     | @foo      |          |
        | Scenario   | A3     | @foo @bar |          |
        | Scenario   | B3     |           | Untagged |
    When I run the behave with tags
    Then the following scenarios are selected with cmdline:
        | cmdline                    | selected           | Logic comment |
        | --tags=@foo                | A1, A3, B2         | @foo          |
        | --tags=-@foo               | A1, A3, B2         | @foo          |

.. code-block:: Gherkin

    # IDEA:
    # -- Scenario: Select scenarios with tags
    Given I use the behave model builder with:
        | statement  | name   | tags      | Comment |
        | Feature    | Alice  | @alice    |          |
        | Scenario   | A1     | @foo      |          |
        | Scenario   | A2     | @bar      |          |
        | Scenario   | A3     | @foo @bar |          |
        | Feature    | Bob    | @bob      |          |
        | Scenario   | B1     | @bar      |          |
        | Scenario   | B2     | @foo      |          |
        | Scenario   | B3     |           | Untagged |
    When I run the behave with options "--tags=@foo"
    Then the following scenarios are selected:
        | statement  | name   | selected  |
        | Scenario   | A1     | yes       |
        | Scenario   | A2     | no        |
        | Scenario   | A3     | yes       |
        | Scenario   | B1     | no        |
        | Scenario   | B2     | yes       |
        | Scenario   | B3     | no        |
 __future__ absolute_import behave given when then behave_model_util BehaveModelBuilder convert_comma_list behave_model_util run_model_with_cmdline collect_selected_and_skipped_scenarios hamcrest assert_that equal_to step_given_a_behave_model_with_table N/A N/A context N/A N/A N/A 
    Build a behave feature model from a tabular description.

    .. code-block:: gherkin

        # -- Scenario: Select scenarios with tags
        Given I use the behave model builder with:
            | statement  | name   | tags      | Comment |
            | Scenario   | S0     |           | Untagged |
            | Scenario   | S1     | @foo      |          |
            | Scenario   | S3     | @foo @bar |          |
     N/A N/A context table REQUIRE: context.table N/A N/A N/A N/A context table require_columns N/A BehaveModelBuilder REQUIRED_COLUMNS N/A model_builder N/A BehaveModelBuilder N/A N/A context behave_model N/A N/A model_builder build_model_from_table N/A context table N/A N/A given a behave model with step_when_run_behave_model_with_hint N/A N/A context hint N/A N/A N/A N/A N/A when I run the behave model with "{hint}" step_then_scenarios_are_selected_with_cmdline N/A N/A context N/A N/A N/A 
    .. code-block:: Gherkin

        Then the following scenarios are selected with cmdline:
            | cmdline      | selected?    | Logic comment |
            | --tags=@foo  | A1, A3, B2   | @foo          |
     N/A N/A context behave_model REQUIRE: context attribute N/A N/A context table REQUIRE: context.table N/A N/A N/A N/A context table require_columns N/A cmdline selected? N/A model N/A context behave_model N/A N/A row_index row N/A enumerate N/A N/A context table rows N/A N/A cmdline N/A row N/A cmdline N/A expected_selected_names N/A convert_comma_list N/A row N/A selected? N/A N/A run_model_with_cmdline model cmdline N/A N/A selected skipped N/A collect_selected_and_skipped_scenarios model N/A actual_selected N/A N/A scenario name N/A scenario selected N/A N/A assert_that actual_selected N/A equal_to expected_selected_names N/A cmdline=%s (row=%s) N/A cmdline row_index N/A N/A then the following scenarios are selected with cmdline