The autopilot tests execute code at the module level (at import time)

Installing messaging-app-autopilot on my desktop and listing the available autopilot tests causes some account setup code to be executed which appears to attempt to create a network connection too?

This code should not just blindly execute at the module level (as it gets run when imported i.e. listing the available tests.) and should definitely not get executed on the desktop if it's going to break things.

Below is this is the command that I used and the output that I saw.
On top of this output I saw a network manager popup stating that some connection had failed.
In my NetworkManager drop down I now have some option named '/246813579/context1' (I've attempted to show this in the attached screen shot but it's in the process of hiding the dropdown).

$ python -m autopilot.run list messaging_app
mc-tool: couldn't load account 'ofono/ofono/account0': Method "GetAll" with signature "s" on interface "org.freedesktop.DBus.Properties" doesn't exist

Try 'mc-tool list' to list known accounts.
creating ofono/ofono/account0
ofono/ofono/account0
enabling ofono/ofono/account0
ofono accounts initialized
initctl: Unknown job: maliit-server
Loading tests from: /usr/lib/python2.7/dist-packages
.. snip ...