open-feature / open-feature/flagd
[CHORE] Review and improve unit/integration coverage for core functionalities
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 997
- Forks
- 136
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 11
Description
Review flagd test coverage, especially of core components lik:
- anything in flagd/core, but specifically:
- store.go
- json.go
- all custom ops (
fractional,semver,string_comparison, in the eval package: https://github.com/open-feature/flagd/tree/main/core/pkg/evaluator - sync implementations: https://github.com/open-feature/flagd/tree/main/core/pkg/sync
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 existing tests for the components under core, especially core/pkg/store/store.go and core/pkg/evaluator/json.go. Then inspect coverage for the fractional, semver, and string_comparison custom operations and the sync implementations. Done means the core functionality has improved unit or integration coverage across the named areas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100