Uploaded image for project: 'OpenShift Hosted Control Plane'
  1. OpenShift Hosted Control Plane
  2. HOSTEDCP-1709

Improve Asynchronous Assertions In E2E


    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None
    • Hypershift Sprint 254, Hypershift Sprint 255, Hypershift Sprint 256
    • 0
    • 0
    • 0

      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

            skuznets@redhat.com Steve Kuznetsov
            skuznets@redhat.com Steve Kuznetsov
            0 Vote for this issue
            1 Start watching this issue