When running a manual test that contains a command and a description with the $output placeholder, the test is skipped and shown in the results page as not being handled by any plugin. Looking into the logs, it seems that the problem is because the command takes too long to complete according to this error message:
DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
If the test is run with a timeout value added in the test suite, then a different error arises and the command is also aborted:
AttributeError: 'Frontend' object has no attribute 'test'
Please find attached the backtrace for both errors.
I forgot to ask, what is the default timeout value? I would have expected it to be infinite by default, but it seems it's not or maybe I'm mixing two different timeouts (the on for the test and the on for dbus).