-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat!: rework gherkin files and structure (#161)
Signed-off-by: Simon Schrottner <[email protected]>
- Loading branch information
Showing
14 changed files
with
401 additions
and
276 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -50,8 +50,8 @@ | |
{ | ||
"steps-length": { | ||
"Background": 3, | ||
"Scenario": 15 | ||
"Scenario": 16 | ||
} | ||
} | ||
] | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
@rpc @in-process | ||
Feature: flagd provider disconnect and reconnect functionality | ||
|
||
Scenario Outline: Connection | ||
Given a <name> flagd provider | ||
And a Boolean-flag with key "boolean-flag" and a default value "true" | ||
When the flag was evaluated with details | ||
Then the resolved details value should be "true" | ||
|
||
Scenarios: Stable | ||
| name | | ||
| stable | | ||
@targetURI | ||
Scenarios: Target URI | ||
| name | | ||
| target | | ||
@customCert | ||
Scenarios: Certificates | ||
| name | | ||
| ssl | | ||
@unixsocket @os.linux | ||
Scenarios: Unixsocket | ||
| name | | ||
| socket | | ||
|
||
@reconnect | ||
# This test suite tests the reconnection functionality of flagd providers | ||
Scenario Outline: Provider reconnection | ||
Given a <name> flagd provider | ||
And a ready event handler | ||
And a error event handler | ||
When a ready event was fired | ||
When the connection is lost for 4s | ||
Then the error event handler should have been executed | ||
Then the ready event handler should have been executed | ||
|
||
Scenarios: Stable | ||
| name | | ||
| stable | | ||
@targetURI | ||
Scenarios: Target URI | ||
| name | | ||
| socket | | ||
@customCert | ||
Scenarios: Certificates | ||
| name | | ||
| ssl | | ||
@unixsocket @os.linux | ||
Scenarios: Unixsocket | ||
| name | | ||
| socket | | ||
|
||
Scenario: Provider unavailable | ||
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 1000ms |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
@rpc @in-process | ||
Feature: flagd evaluations | ||
|
||
# This test suite contains scenarios to test flagd providers. | ||
# It's associated with the flags configured in flags. | ||
# It should be used in conjunction with the suites supplied by the OpenFeature specification. | ||
|
||
Background: | ||
Given an option "cache" of type "CacheType" with value "disabled" | ||
And a stable flagd provider | ||
|
||
Scenario Outline: Resolve values | ||
Given a <type>-flag with key "<key>" and a default value "<default>" | ||
When the flag was evaluated with details | ||
Then the resolved details value should be "<resolved_value>" | ||
|
||
Examples: | ||
| key | type | default | resolved_value | | ||
| boolean-flag | Boolean | false | true | | ||
| string-flag | String | bye | hi | | ||
| integer-flag | Integer | 1 | 10 | | ||
| float-flag | Float | 0.1 | 0.5 | | ||
|
||
Scenario Outline: Resolves zero value | ||
Given a <type>-flag with key "<key>" and a default value "<default>" | ||
When the flag was evaluated with details | ||
Then the resolved details value should be "<resolved_value>" | ||
|
||
Examples: | ||
| key | type | default | resolved_value | | ||
| boolean-zero-flag | Boolean | true | false | | ||
| string-zero-flag | String | hi | | | ||
| integer-zero-flag | Integer | 1 | 0 | | ||
| float-zero-flag | Float | 0.1 | 0.0 | |
Oops, something went wrong.