-
Notifications
You must be signed in to change notification settings - Fork 43
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
[checkbox-ce-oem] Add timedatectl test in strict-confinement mode (New) #1232
Conversation
I think we need to have post-suspend for timedate control tests as well. Another point I would like to raise here is, is the interface connection will be connected automatically? If not, the confinement related tests will be skipped. |
No the interfaces connect won't be automatically. It's rely on manually or via a setup script. And yes, if the interfaces are not connected before the test, than the test will be skipped. And this is the reason which I put the requires of slot and plug. |
7bf1465
to
2fc0e01
Compare
list-bootstrapped of timedatectl: list-bootstrapped of mediacare: |
@stanley31huang |
LGTM for now, but I would like to separate those jobs and test plans into following structure and also consistent naming rule.
|
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, but we need another PR to structure the test plan and job.
Description
Add timedatectl test for testing if timezone and NTP time sync can be configured in strict-confinement mode. This test rely on test snap.
Resolved issues
Documentation
Tests
Test result pass:
https://certification.canonical.com/hardware/202304-31486/submission/368054/
Test result failed without connect interface:
https://certification.canonical.com/hardware/202304-31486/submission/368057/