I did this because I knew there were going to be latency issues and I was happy with 0.5 seconds of implied wait, especially when you are explicitly declaring a wait  ( the name of these methods being `wait_` ). I'd much rather lose some time here at this point and save the test writer problems. Fixing the difficulty with latency high up in the tree saves time in **writing** the tests which is even more valuable than saving time when running the tests. I would prefer to normalise the latency even further up in the stack, eg at the Marionette level, but the devs have rejected that.
 
Really speed is not important in this test suite, we'll always trade speed for reliability.