open-feature / open-feature/cpp-sdk-contrib
[flagd] Add Gherkin tests to CI once all the features are implemented
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2
- Forks
- 3
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 5
Description
Currently the whole Gherkin suite is tagged as manual due to the fact, that we don't have implemented all of the features yet. When the suite turns green and we fix all of the issues, we should add the Gherkin suite to the CI, to verify that new changes won't break the flagd contract.
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 locating the Gherkin suite, its manual tag configuration, and the repository's CI workflow. Verify which unimplemented features or failing scenarios still block a green run. Done means the full Gherkin suite passes and CI runs it automatically to catch flagd contract regressions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100