Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Update test harness with metadata assertions #1467 #289

Merged
merged 5 commits into from
Jan 27, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions specification/assets/gherkin/metadata.feature
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
@Metadata
Feature: Metadata

Background:
Given a stable provider

Scenario: Returns metadata
Given a Boolean-flag with key "metadata-flag" and a default value "true"
When the flag was evaluated with details
beeme1mr marked this conversation as resolved.
Show resolved Hide resolved
Then the resolved metadata should contain
| key | metadata_type | value |
| string | String | 1.0.2 |
| integer | Integer | 2 |
| float | Float | 0.1 |
| boolean | Boolean | true |

Scenario Outline: Returns no metadata
Given a <flag_type>-flag with key "<key>" and a default value "<default_value>"
When the flag was evaluated with details
Then the resolved metadata is empty

Examples: Flags
| key | flag_type | default_value |
| boolean-flag | Boolean | true |
| integer-flag | Integer | 23 |
| float-flag | Float | 2.3 |
| string-flag | String | value |
Loading