-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add manifest gate for obex tests (bugfix) #1585
Conversation
This also removes the test from the exclusion list this way once we have the hardware to do sru obex tests we just need to enable it via the manifest without changing the tests
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1585 +/- ##
=======================================
Coverage 48.00% 48.00%
=======================================
Files 371 371
Lines 39833 39833
Branches 6730 6730
=======================================
Hits 19121 19121
Misses 19994 19994
Partials 718 718
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
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.
I think the problem is not the DUT support of OBEX feature, it's an infrastructure problem, so the naming of the manifest is incorrect, and anyway we need it to be very clear that this should be set to True
when doing QA/ODM enablement testing.
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.
After discussing with Max, agreed to the proposed change with a little change in the name.
Co-authored-by: Pierre Equoy <pierre.equoy@canonical.com>
* Add manifest gate for obex tests This also removes the test from the exclusion list this way once we have the hardware to do sru obex tests we just need to enable it via the manifest without changing the tests * Better description Co-authored-by: Pierre Equoy <pierre.equoy@canonical.com> --------- Co-authored-by: Pierre Equoy <pierre.equoy@canonical.com>
Description
The obex test was introduced with the only gate being the presence of the software to test it. This is problematic because the software will always be installed in the snap, but not all platforms support this extension. Additionally one needs the hardware to test this capability as well. For this reason we have decided to introduce a new manifest to gate the execution of this test because it is currently failing in sru (we had to manually exclude it) and in snap testing (where it is non-trivial to exclude).
This also removes the test from the exclusion list, this way once we have the hardware to do sru obex tests we just need to enable it via the manifest without changing the test plans
Resolved issues
Fixes: https://warthogs.atlassian.net/browse/CHECKBOX-1646
Documentation
N/A
Tests
N/A
WARNING: This modifies com.canonical.certification::sru-server