open-feature / open-feature/flagd
[CHORE] Extend provider-specific Gherkin tests for complete coverage of e2e scenarios
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
Especially focusing on un-happy paths and corner cases
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 provider-specific Gherkin tests and the existing end-to-end scenarios. Review which unhappy paths and corner cases are already covered, then extend the relevant scenarios until provider-specific coverage is complete; the issue provides no file or test path to begin from.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100