-
Notifications
You must be signed in to change notification settings - Fork 12
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
Use reusable integration test workflow #354
Conversation
69f7e35
to
be2678c
Compare
needs #355 |
04b755c
to
d4dc431
Compare
6e9dd85
to
5899116
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #354 +/- ##
=======================================
Coverage ? 65.43%
=======================================
Files ? 17
Lines ? 3127
Branches ? 415
=======================================
Hits ? 2046
Misses ? 950
Partials ? 131 ☔ 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.
Wow, this is way nicer now.
Q: why did we run unit test for Juju 2.9 and 3.1 earlier (no neither Juju nor libjuju used in unit tests)? I am confused here...
@juditnovak can probably explain it better than I can tl;dr a quick solution to get unit tests with & without secrets working, I think |
Use pytest.mark.skipif to skip at collection time instead of runtime
Instead of juju CLI version So that version is accessible during test collection without installing juju
This reverts commit fef462e.
d754f48
to
133c6a5
Compare
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.
🚀
No description provided.