We can improve the robustness, maintainability, and developer experience of asynchronous assertions in end-to-end tests by adhering to a couple rules:

• Bounded Lifecycle: every asynchronous assertion should have an explicit bound for when we expect it to have passed
• Explain What You're Doing: every major code-path should log what it's doing - a user waiting on an assertion should never be left wondering what's going on
• Terse Output: "don't say the same thing twice" - only output when something has changed
• Keep Track Of Time: at a minimum, output how long the assertion took to run its course; if it's useful, output the durations between state deltas