I noticed that most of the existing tests are waiting for the `body` element after launching, so I included that here. We often wait for something more specific to the app in question in our tests. I suppose sometimes the body is loaded and visible before all of the elements on the page.

I think that using `waitForElement` any time you need to interact with an element, assuming that it is going to be visible, is a good practice. We have found ourselves continually having to add waits into tests where they were not thought to be required.