open-feature / open-feature/flagd

[CHORE] Review gherkin suite and test-harness for missing test coverage

Open
#1,774 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
998
Forks
136
Avg merge
4d 8h
Merged PRs (30d)
11

Description

Our testbed covers all our operators, and some behavior around connection and re-connection. The goal of this issue is to identify and enumerate shortcomings in this suite which can be tackled in other issue(s).

For example (not sure if any of these are ACTUALLY missing or not):

  • missing edge cases for custom operations (fraction, sem_ver, etc)
  • missing tests for built-in JsonLogic operators
  • missing test cases for provider misconfiguration
  • missing test cases for error scenarios

Tips:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the flagd-testbed flags directory, then inspect its gherkin directory and assertions. Compare the covered operators, connection and reconnection behavior, provider configuration, and error scenarios against the stated examples. Done means producing an enumeration of missing or weak coverage that can be addressed in follow-up issues.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.