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.

Sign up for GitHub

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: Add new test suite for context merging #293

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

feat: Add new test suite for context merging #293

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
49 changes: 49 additions & 0 deletions specification/assets/gherkin/contextMerging.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
Feature: Context merging precedence

Background:
Given a stable provider with retrievable context is registered

Scenario Outline: A context entry is added to a single level
Given A context entry with key "key" and value "value" is added to the "<level>" level
When Some flag was evaluated
Then The merged context contains an entry with key "key" and value "value"

Examples:
| level |
| API |
| Transaction |
| Client |
| Invocation |
| Before Hooks |

Scenario: A context entry is added to each level with different keys
Given A context entry with key "API" and value "API value" is added to the "API" level
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you prefer the same line with different values each time, or a data table for the Given and Then parts of this scenario?

And A context entry with key "Transaction" and value "Transaction value" is added to the "Transaction" level
And A context entry with key "Client" and value "Client value" is added to the "Client" level
And A context entry with key "Invocation" and value "Invocation value" is added to the "Invocation" level
And A context entry with key "Before Hooks" and value "Before Hooks value" is added to the "Before Hooks" level
When Some flag was evaluated
Then The merged context contains an entry with key "API" and value "API value"
And The merged context contains an entry with key "Transaction" and value "Transaction value"
And The merged context contains an entry with key "Client" and value "Client value"
And The merged context contains an entry with key "Invocation" and value "Invocation value"
And The merged context contains an entry with key "Before Hooks" and value "Before Hooks value"

Scenario Outline: A context entry in one level overwrites values with the same key from preceding levels
Given A table with levels of increasing precedence
| API |
| Transaction |
| Client |
| Invocation |
| Before Hooks |
And Context entries for each level from API level down to the "<level>" level with key "key" and value "<level>"
When Some flag was evaluated
Then The merged context contains an entry with key "key" and value "<level>"

Examples:
| level |
| API |
| Transaction |
| Client |
| Invocation |
| Before Hooks |
Loading