Skip to content

Commit

Permalink
cover more default branch switching scenarios
Browse files Browse the repository at this point in the history
Signed-off-by: Gary Lockett <[email protected]>
  • Loading branch information
Gary Lockett committed Sep 16, 2022
1 parent 45e0195 commit 3cdb9f8
Showing 1 changed file with 43 additions and 1 deletion.
44 changes: 43 additions & 1 deletion feature/default-branch-switching.feature
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,49 @@ Feature: Default branch switching
| 1.3.x |
And the default branch should be "1.3.x"

Scenario: A pre-existing branch of a greater major release is set as default branch on release
Scenario: A new minor branch on a pre-existing major branch is created and set as default branch on release
Given following existing branches:
| branch |
| 1.0.x |
| 1.1.x |
| 1.2.x |
| 2.0.x |
And following open milestones:
| name |
| 2.0.0 |
And the default branch is "1.0.x"
When I close milestone "2.0.0"
Then these should be the existing branches:
| branch |
| 1.0.x |
| 1.1.x |
| 1.2.x |
| 2.0.x |
| 2.1.x |
And the default branch should be "2.1.x"

Scenario: A pre-existing branch of a new major release is not set as default branch on release
Given following existing branches:
| branch |
| 1.0.x |
| 1.1.x |
| 1.2.x |
| 2.0.x |
And following open milestones:
| name |
| 1.2.0 |
And the default branch is "1.0.x"
When I close milestone "1.2.0"
Then these should be the existing branches:
| branch |
| 1.0.x |
| 1.1.x |
| 1.2.x |
| 1.3.x |
| 2.0.x |
And the default branch should be "1.3.x"

Scenario: A pre-existing minor branch of a greater major release is set as default branch on release
Given following existing branches:
| branch |
| 1.0.x |
Expand Down

0 comments on commit 3cdb9f8

Please sign in to comment.