Automatic driver re-activation on change of state of the DUT

[istepic]

Documentation states:

If the target reboots, e.g. through a hardware watchdog timeout, a power cycle, or by issuing a reboot command on the shell, the ShellDriver’s internal state becomes outdated, and the ShellDriver needs to be deactivated and re-activated.

My workaround for this is:

@pytest.fixture
def lazy_ssh(target, strategy):
    def f():
        strategy.transition("shell")
        target.activate("SSHDriver")
        return target.get_driver("SSHDriver")

    yield f
    target.deactivate("SSHDriver")

def test_invalidated_token_is_erased_from_the_partition(fastboot, lazy_ssh):
    fastboot.flash("token", "/tmp/token")
    cmd = lazy_ssh()
    _, _, ret = cmd.run("head /dev/sda6 | grep -q TOKEN")
    assert ret == 1

Activating fastboot requires a DUT reset, so I can't use a simple:

@pytest.fixture
def cmd(target):
    # strategy.transition("shell")
    return target.get_driver("CommandProtocol")

because SSH is not available when DUT is in fastboot mode.

My question is: would it be feasible to bind target driver re-activation to a change in state? Meaning, target would re-activate a driver once strategy.transition("shell") is detected.