You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The precompiler would separate elements of a feature file into different ones based on a specific tag and its value, i.e., generating suites.
Use cases
Scenarios are marked with @suite(X) tags, where X can be smoke, regression or sanity, indicating in which test suite (by purpose) the scenario is executed. A scenario can have multiple of such tags, but at least one.
To clarify, separate folders might be generated containing feature files and elements matching the given suite tag.
Example
Take the following (example) feature file:
# src/login.featureFeature: Login@suite(sanity)@suite(smoke)@suite(regression)Scenario: Login passGiven the login page is opened
When the username is typed
And the password is typed
And the login button is clicked
Then the user should be logged in
@suite(smoke)@suite(regression)Scenario: Login failGiven the login page is opened
When the username is typed
And the wrong password is typed
And the login button is clicked
Then the error should be visible
And the user should not be logged in
Running the precompiler would result in the following feature files:
# dist/suite-sanity/login.featureFeature: Login@suite(sanity)Scenario: Login passGiven the login page is opened
When the username is typed
And the password is typed
And the login button is clicked
Then the user should be logged in
# dist/suite-smoke/login.featureFeature: Login@suite(smoke)Scenario: Login passGiven the login page is opened
When the username is typed
And the password is typed
And the login button is clicked
Then the user should be logged in
@suite(smoke)Scenario: Login failGiven the login page is opened
When the username is typed
And the wrong password is typed
And the login button is clicked
Then the error should be visible
And the user should not be logged in
# dist/suite-regression/login.featureFeature: Login@suite(regression)Scenario: Login passGiven the login page is opened
When the username is typed
And the password is typed
And the login button is clicked
Then the user should be logged in
@suite(regression)Scenario: Login failGiven the login page is opened
When the username is typed
And the wrong password is typed
And the login button is clicked
Then the error should be visible
And the user should not be logged in
Options/Variants
Separating feature files either into folders or feature files.
Keeping/Removing suite tags from the result.
Considering a default tag for an element where it is missing.
Additional context
The text was updated successfully, but these errors were encountered:
szikszail
changed the title
gpc-suite-generator
[GPC] Suite Generator
Feb 2, 2022
Summary
The precompiler would separate elements of a feature file into different ones based on a specific tag and its value, i.e., generating suites.
Use cases
Scenarios are marked with
@suite(X)
tags, whereX
can besmoke
,regression
orsanity
, indicating in which test suite (by purpose) the scenario is executed. A scenario can have multiple of such tags, but at least one.To clarify, separate folders might be generated containing feature files and elements matching the given suite tag.
Example
Take the following (example) feature file:
Running the precompiler would result in the following feature files:
Options/Variants
Additional context
The text was updated successfully, but these errors were encountered: