Page History
...
One key thing that you must decide is: where do you want to manage the Cucumber scenarios? Preferably you will only have a single source of truth. Do you want to use Jira as the master of information (recommended)? Or do you want to use Git, for example, as the master for your features and corresponding scenarios?
...
Info | ||
---|---|---|
| ||
Having both Jira and the VCS (e.g. Git, SVN) as master of information for Cucumber Scenarios/Scenario Outlines can lead to synchronization synchronisation issues because the scenarios edited in JIRA won't be commited committed automatically to the VCS to the original feature files used. Thus, you can use a mix of the Standard and VCS workflows below but have in mind that the scenarios can be out of synch between what you have in Jira and what you have in the VCS. |
...
Jira based Cucumber workflow
In this workflow, Tests are created and managed in Jira, thus Jira will be the master for the Cucumber scenarios.
...
Info | ||
---|---|---|
| ||
This flow will work fine as long as:
Is any of the previous conditions is not satisfied then new and duplicated Tests, and Pre-Conditions, may be created. See an example in Importing Cucumber Tests - REST. |
Legacy Cucumber
...
migration workflow
The workflow below applies to legacy/existing projects that already have Cucumber tests in some version control system (e.g., GIT, SVN), possibly alongside the software's implementation.
...