-
Notifications
You must be signed in to change notification settings - Fork 448
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
fix(test): use prime dir in some tests #4661
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## feature/craft-application #4661 +/- ##
=============================================================
+ Coverage 89.14% 89.32% +0.17%
=============================================================
Files 331 335 +4
Lines 22078 22288 +210
=============================================================
+ Hits 19682 19909 +227
+ Misses 2396 2379 -17 ☔ View full report in Codecov by Sentry. |
569c4fa
to
6ae98a5
Compare
4fb0323
to
a92e2d2
Compare
a92e2d2
to
d95c5ee
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.
having the same pattern as all the other tests helps with quick matching in the future
d95c5ee
to
29e7bd4
Compare
29e7bd4
to
c8e131e
Compare
There are 2 bugs: First, the current fixture `snapcraft_yaml` may create 2 `snapcraft.yaml` in `/` and `/snap/` due to it used in different places and it is default to `/snap/snapcraft.yaml`. When both `snapcraft.yaml` exists, the `/snapcraft.yaml` is used without any error / warning. The second bug is when `/snap/snapcraft.yaml` exists, `/build-aux/snap` will be ignored even if it had hooks in it. This is probably expected behavior since these are two different versions of the structure. Needs #4661
Add prime dir in some tests.