-
Notifications
You must be signed in to change notification settings - Fork 458
test: Segment matching for sub rules and conditions #4776
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Skipped Deployments
|
Docker builds report
|
|
Uffizzi Preview |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like the tests are failing in CI — can't approve the PR yet.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4776 +/- ##
=======================================
Coverage 97.38% 97.38%
=======================================
Files 1189 1189
Lines 41379 41409 +30
=======================================
+ Hits 40297 40327 +30
Misses 1082 1082 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Changes
This adds a test for the related PR in the Flagsmith commons repo. This PR will not be merged until the related PR has been merged into commons and a new tag is released for it.
How did you test this code?
Test both conditions and rules to match. For sub rules we rely on matching to a parent rule, which itself must match to the segment rule.