This is vs #12059, which changes the semantics of Dogtail so that
nodes are searched for on Dogtail::* object creation.

Refs: #12059

This reverts commit 75449088.

I need the test suite working to release 3.0~beta2, and it's been quite broken
on feature/stretch since the merge of test/12059-dogtail-optimizations.

refs: #12305

Typing "Files" in the Activities overview (sometimes?) starts "Search files"
instead of Nautilus.

This reverts commit 920baa75.

Refs: #10498

This reverts commit 273dbe2e.

Refs: #10498

Refs: #10498

We'll get better output about the reason why the step failed.

Refs: #10498

Restarting fresh the whole Files application ensure no previous retry
messed up the interface, e.g after the first run, the "connect to
server" button color has changed.

Refs: #10498

Refs: #10498

Otherwise it sometimes succeeds to connect after a while, and then the
fingerprint verification window pops up while we're already retrying the
scenario and are at a different step.

Refs: #10498

Refs: #10498

Removed the fingerprint verification step by mistake, that's why I had
to add it back in the previous commit. Too bad for the new blob in the
repo.

Refs: #10498

Needs to confirm we don't care about the SFTP server fingerprint.

Refs: #10498

We only support running add_lan_host() at the top-level scope and not
from within some class' method since the `@lan_hosts` reference means
something very different then.

Also:
* Don't use class variables (@sshd) unnecessarily.
* Ruby does not support "keyword" style parameter assignment
  (sshd_host, sshd_port).

Any random number in the range can of course already be in use.

They try to do the same thing, but the former uses uglier parsing
(imho) and fails if the test suite is run as a non-root user since
ifconfig is in /sbin, which generally isn't in such users' PATH:s.

On a heavily loaded system, sikuli may try to acknowledge the SSH
fingerprint prompt before we're ready for it. Inserting the sleep here
will make sure that we wait to enough time to ensure that none of the
keystrokes are lost.

We'll force a new Tor circuit and retry connecting.

Will-fix: #10498

When we fail to make a connection via SSH, force a new Tor circuit and
retry.

Will-fix: #10498

... and pave the way for adding more options than the user to execute
the command as.

Will-fix: #9257

"Persistent" in the sense that it survives across scenarios. This is a
first step towards using a single Libvirt::Domain instance across the
full test suite run, which in turn is a step towards being able to use
Libvirt snapshots more easily (or at all, I think).

This was achieved with the following command:

    sed -i 's/@vm\>/$vm/g' -- features/step_definitions/*.rb \
                              features/support/*.rb \
                              features/support/helpers/*.rb

anonym++

At the same time, remove the LAN steps.