-
Notifications
You must be signed in to change notification settings - Fork 43
feat: loosen test instance interface to support various test frameworks #316 #319
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
Signed-off-by: ekarlso <endre.karlson@xait.com>
…ks (open-feature#317) Switch to `interface{ Name() string }` since testing.BB has `private` which blocks it from working. Signed-off-by: ekarlso <endre.karlson@xait.com>
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.
This looks good to me, my only small concern is that it is not obvious anymore what is the type of test
, this is why I think we can name this type as proposed in the comment.
Co-authored-by: Thomas Poignant <thomas.poignant@gmail.com> Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Signed-off-by: Michael Beemer <beeme1mr@users.noreply.github.com>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #319 +/- ##
=======================================
Coverage 88.13% 88.13%
=======================================
Files 14 14
Lines 1408 1408
=======================================
Hits 1241 1241
Misses 143 143
Partials 24 24
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
feat: loosen test instance interface to support various test frameworks (#317)
This PR
Use interface instead of testing.BB since it has private() that blocks use.
Related Issues
Fixes #316
Notes
Follow-up Tasks
How to test