-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
- Loading branch information
Showing
1 changed file
with
29 additions
and
0 deletions.
There are no files selected for viewing
29 changes: 29 additions & 0 deletions
29
providers/openfeature-provider-flagd/tests/e2e/events.feature
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,29 @@ | ||
Feature: flagd providers | ||
|
||
# This test suite contains scenarios to test flagd providers. | ||
# It's associated with the flags configured in flags/changing-flag.json and flags/zero-flags.json. | ||
# It should be used in conjunction with the suites supplied by the OpenFeature specification. | ||
|
||
Background: | ||
Given a flagd provider is set | ||
|
||
# events | ||
Scenario Outline: Provider events | ||
When a <event> handler is added | ||
Then the <event> handler must run | ||
Examples: | ||
| event | | ||
| PROVIDER_ERROR | | ||
| PROVIDER_STALE | | ||
| PROVIDER_READY | | ||
|
||
# events | ||
Scenario: Provider events chain ready -> stale -> error -> ready | ||
When a PROVIDER_READY handler is added | ||
Then the PROVIDER_READY handler must run | ||
When a PROVIDER_STALE handler is added | ||
Then the PROVIDER_STALE handler must run | ||
When a PROVIDER_ERROR handler is added | ||
Then the PROVIDER_ERROR handler must run | ||
When a PROVIDER_READY handler is added | ||
Then the PROVIDER_READY handler must run |