Skip to content

Commit

Permalink
fix(launchpad): improve gherkin file for new launchpad (#205)
Browse files Browse the repository at this point in the history
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
  • Loading branch information
aepfli authored Jan 21, 2025
1 parent 53d0e3f commit 73ec93a
Show file tree
Hide file tree
Showing 2 changed files with 16 additions and 6 deletions.
4 changes: 2 additions & 2 deletions gherkin/connection.feature
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Feature: flagd provider disconnect and reconnect functionality
And a ready event handler
And a error event handler
When a ready event was fired
When the connection is lost for 4s
When the connection is lost for 3s
Then the error event handler should have been executed
Then the ready event handler should have been executed

Expand All @@ -55,4 +55,4 @@ Feature: flagd provider disconnect and reconnect functionality
Given an option "deadlineMs" of type "Integer" with value "1000"
And a unavailable flagd provider
And a error event handler
Then the error event handler should have been executed within 2000ms
Then the error event handler should have been executed within 3000ms
18 changes: 14 additions & 4 deletions gherkin/events.feature
Original file line number Diff line number Diff line change
Expand Up @@ -17,23 +17,33 @@ Feature: Flagd Provider State Changes
| event |
| stale |

Scenario: Provider events chain ready -> error -> ready
Given a ready event handler
And a error event handler
Then the ready event handler should have been executed
When the connection is lost for 3s
Then the error event handler should have been executed
Then the ready event handler should have been executed

@grace
Scenario: Provider events chain ready -> stale -> error -> ready
Given a ready event handler
And a error event handler
And a stale event handler
Then the ready event handler should have been executed
When the connection is lost for 6s
When the connection is lost for 3s
Then the stale event handler should have been executed
Then the error event handler should have been executed
Then the ready event handler should have been executed

Scenario: Provider events chain ready -> error -> ready
@grace
Scenario: Provider events chain ready -> stale -> ready
Given a ready event handler
And a error event handler
And a stale event handler
Then the ready event handler should have been executed
When the connection is lost for 6s
Then the error event handler should have been executed
When the connection is lost for 1s
Then the stale event handler should have been executed
Then the ready event handler should have been executed

Scenario: Flag change event
Expand Down

0 comments on commit 73ec93a

Please sign in to comment.