Connect a wireless AP first.
After running the wireless jobs below:
job 'com.canonical.certification::dock/wireless-connection-after-suspend-wpa-bg'
job 'com.canonical.certification::dock/wireless-connection-after-suspend-open-bg'
job 'com.canonical.certification::dock/wireless-connection-after-suspend-wpa-n'
job 'com.canonical.certification::dock/wireless-connection-after-suspend-open-n'
job 'com.canonical.certification::dock/wireless-connection-after-suspend-wpa-ac'
job 'com.canonical.certification::dock/wireless-connection-after-suspend-open-ac'
It won't reconnect to the wireless AP which connected before.
This will impact the test which need network.
||/ Name Version Architecture Description
+++-======================================-========================-============-==============================================================
ii checkbox-ng 1.0.0~ppa~ubuntu18.04.1 all CheckBoxNG test runner
un checkbox-oem <none> <none> (no description available)
ii checkbox-oem-bug 1.14-1-ubuntu1 all Checkbox OEM bug
un plainbox <none> <none> (no description available)
ii plainbox-insecure-policy 1.0.0~ppa~ubuntu18.04.1 all policykit policy required to use CheckBoxNG (insecure version)
ii plainbox-provider-certification-client 0.33.0~ppa~ubuntu18.04.1 all Client Certification provider for Plainbox
ii plainbox-provider-checkbox 0.43.0~ppa~ubuntu18.04.1 amd64 CheckBox provider for PlainBox
ii plainbox-provider-oem 0.54 all plainbox oem provider
un plainbox-provider-oem-kittyhawk <none> <none> (no description available)
un plainbox-provider-oem-somerville <none> <none> (no description available)
ii plainbox-provider-oem-stella 0.54 all plainbox oem provider for stella
un plainbox-provider-oem-sutton <none> <none> (no description available)
ii plainbox-provider-resource-generic 0.36.0~ppa~ubuntu18.04.1 amd64 CheckBox generic resource jobs provider
ii plainbox-provider-tpm2 1.7.0~ppa~ubuntu18.04.1 all TPM 2.0 provider for PlainBox
un plainbox-secure-policy <none> <none> (no description available)
ii python3-checkbox-ng 1.0.0~ppa~ubuntu18.04.1 all CheckBoxNG test runner (Python 3 library)
ii python3-checkbox-support 0.37.0~ppa~ubuntu18.04.1 all collection of Python modules used by PlainBox providers
un python3-plainbox <none> <none> (no description available)
The python rewrite of the nm wireless connection script does indeed delete all connections before exiting.
Existing connections are all cleanup up.
https:/ /git.launchpad. net/plainbox- provider- checkbox/ tree/bin/ connect_ wireless (a legacy script) did no deleted connections, just disconnected them (which could lead to unexpected reconnections and mask real issues).
I'd suggest to have a look at https:/ /git.launchpad. net/plainbox- provider- checkbox/ tree/bin/ create_ connection, connection files are recorded in /etc/NetworkMan ager/system- connections.
We could backup this directory and restore it after all wireless tests. The only problem is that backup and `nmcli c reload` have to be run as root and the current connection tests run well as a normal user and I don't want to change that.
Then my recommendation would be to have a setup and teardown sort of jobs (run as root) to backup/restore existing connections. And update the wireless NM nested part accordingly.