-
Notifications
You must be signed in to change notification settings - Fork 47
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
🌱 Remove E2E test testing rukpak #946
Conversation
✅ Deploy Preview for olmv1 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #946 +/- ##
==========================================
- Coverage 80.41% 79.96% -0.46%
==========================================
Files 16 16
Lines 1103 1103
==========================================
- Hits 887 882 -5
- Misses 150 153 +3
- Partials 66 68 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Something wrong with code coverage report: it dropped to 0 for e2e tests. Even |
908e105
to
3719edf
Compare
We use rukpak as a library at the moment and want rukpak to have own tests covering limitations such not allowing to install content with webhooks. Signed-off-by: Mikalai Radchuk <mradchuk@redhat.com>
No longer can reproduce after rebased on top of |
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.
/lgtm
bfd4142
Description
We use rukpak as a library at the moment and want rukpak to have own tests covering limitations such not allowing to install content with webhooks.
This is a follow up for this discussion: #924 (comment)
Added extra coverage for rukpak: operator-framework/rukpak#922
Reviewer Checklist