Skip to content

feat(evaluator): port new test scenarios from PRs #341-345 into evaluator testkit#348

Closed
aepfli wants to merge 1 commit intomainfrom
feat/evaluator-testkut-update
Closed

feat(evaluator): port new test scenarios from PRs #341-345 into evaluator testkit#348
aepfli wants to merge 1 commit intomainfrom
feat/evaluator-testkut-update

Conversation

@aepfli
Copy link
Copy Markdown
Member

@aepfli aepfli commented Mar 18, 2026

Summary

Ports all new test scenarios introduced in PRs #341, #342, #343, and #345 into the evaluator/ testkit added by #344. These tests were not included in the original #344 branch.

Changes

evaluator/flags/testkit-flags.json — 11 new flags + 1 evaluator

Source Additions
#340 (main) fractional-hash-edge-flag
#341 semver-v-prefix-flag, semver-partial-version-flag, semver-build-metadata-flag
#342 semver-invalid-version-flag, semver-invalid-operator-flag, fractional-null-bucket-key-flag
#343 nested-ref-targeted-flag + is_privileged evaluator
#345 fractional-nested-if-flag, fractional-nested-var-flag

evaluator/gherkin/fractional.feature

  • @fractional-v2 — hash edge cases (boundary values for MurmurHash3 precision)
  • @fractional-nested — nested if and var expressions as bucket variant names
  • @operator-errors — null bucket key falls back to default variant

evaluator/gherkin/semver.feature

  • @semver-edge-cases — v-prefix handling, partial version, build metadata ignored
  • @operator-errors — unparseable version and unknown operator both return null → fallback

evaluator/gherkin/evaluator-refs.feature

  • @evaluator-ref-edge-cases — nested $ref resolution (is_privilegedis_ballmer)

Related

@aepfli aepfli requested a review from a team as a code owner March 18, 2026 10:06
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates a substantial collection of new test scenarios into the evaluator testkit, enhancing the robustness and reliability of the flag evaluation system. By covering a wider array of conditions, including complex operators, error handling, and edge cases, these changes ensure that the evaluator behaves as expected across diverse configurations and inputs. This expansion of test coverage is crucial for maintaining the quality and predictability of feature flag evaluations.

Highlights

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request successfully ports new test scenarios from several previous PRs into the evaluator testkit. The new flag definitions in evaluator/flags/testkit-flags.json are well-structured and consistent with existing patterns. The accompanying Gherkin feature files (evaluator/gherkin/*.feature) clearly define the new test cases for error handling, basic evaluation, evaluator references, fractional operators, metadata, no-default variants, semantic versioning, string comparisons, targeting, and zero values. The updates to flags/custom-ops.json and gherkin/targeting.feature also integrate smoothly, enhancing the test coverage for fractional operator edge cases and versioning. Overall, the changes significantly improve the robustness of the evaluator test suite.

@aepfli aepfli force-pushed the feat/evaluator-testkut-update branch from 42c60d2 to 457811b Compare March 18, 2026 10:11
Base automatically changed from feat/evaluator-testkut to main March 18, 2026 10:17
@aepfli aepfli force-pushed the feat/evaluator-testkut-update branch 2 times, most recently from 2479355 to 7ef3b9e Compare March 18, 2026 12:54
- semver edge cases: v-prefix, partial version, build metadata (@semver-edge-cases)
- operator error null-return fallback (@operator-errors): semver invalid version/operator, fractional null bucket key
- nested $ref resolution via is_privileged (@evaluator-ref-edge-cases)
- nested fractional expressions: if/var as bucket variant names (@fractional-nested)
- fractional hash edge cases (@fractional-v2)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
@aepfli aepfli force-pushed the feat/evaluator-testkut-update branch from 7ef3b9e to c94dd14 Compare March 18, 2026 13:28
@aepfli
Copy link
Copy Markdown
Member Author

aepfli commented Mar 30, 2026

Closing as superseded. The evaluator testkit backfill has been distributed into the individual feature branches:

This approach keeps each feature self-contained and avoids a single large backfill PR that becomes hard to review and prone to merge conflicts.

@aepfli aepfli closed this Mar 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant