Closed DVAlexHiggs closed 2 years ago
To force a scenario/feature file to only run on a specific platform, you can now tag it with the platform name.
e.g.
Feature: [BQ-HUB] Hubs @bigquery # <----- @fixture.single_source_hub Scenario: [BQ-HUB-01] Simple load of stage data into an empty hub Given the HUB table does not exist And the RAW_STAGE table contains data | CUSTOMER_ID | CUSTOMER_NAME | LOAD_DATE | SOURCE | | 1001 | Alice | 1993-01-01 | TPCH | | 1001 | Alice | 1993-01-01 | TPCH | | 1002 | Bob | 1993-01-01 | TPCH | | 1002 | Bob | 1993-01-01 | TPCH | | 1002 | Bob | 1993-01-01 | TPCH | | 1003 | Chad | 1993-01-01 | TPCH | | 1004 | Dom | 1993-01-01 | TPCH | And I stage the STG_CUSTOMER data When I load the HUB hub Then the HUB table should contain expected data | CUSTOMER_PK | CUSTOMER_ID | LOAD_DATE | SOURCE | | md5('1001') | 1001 | 1993-01-01 | TPCH | | md5('1002') | 1002 | 1993-01-01 | TPCH | | md5('1003') | 1003 | 1993-01-01 | TPCH | | md5('1004') | 1004 | 1993-01-01 | TPCH |
Ignore failure on last commit. Cancelled because it was an unnecessary execution (only changed one character in a scenario name)
To force a scenario/feature file to only run on a specific platform, you can now tag it with the platform name.
e.g.