Actually waiting for 'not' something here is a bit risky. We're afraid that the Marketplace may not load properly so 'waiting for not' here could match if the app launched and then crashed 1 second later and it would also match if the app did launch correctly.

I think it would be better to wait `for` something that appears after the loading fragment has cleared. Then we can be very sure that the app has launched, loaded properly and stayed loaded.

We'll never be 100% perfect but if we're wise about how we write the tests we can get closer to 100%.