open-feature / open-feature/cpp-sdk-contrib
[flagd] Verify implementation against flagd gherkin test suite
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2
- Forks
- 3
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 5
Description
Flagd have it's own test suite in flagd-testbed. We should test our provider against it, similarily to cpp-sdk using cwt-cucumber
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the flagd-testbed Gherkin suite and the cpp-sdk issue 58 for a comparable integration. Read the cwt-cucumber project to determine how the C++ provider should run against the suite; done means the provider is tested against the flagd scenarios and the integration passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100