发布

  • [NA] [QA] fix: wait for traces table to fully render before scanning Moderation header (#6743)

    frostbyte_neo 发布于 2026-05-18 09:34:52 +00:00

    The online-scoring moderation flow test polled table thead th with a fixed
    3s wait per reload. On production the traces table renders static columns
    first and appends dynamic feedback-score columns after a second API call,
    so the scan ran before the Moderation header was mounted and every retry
    re-raced the same too-short timer. All six provider/model variants were
    failing identically only on the prod sanity launches while local, staging,
    self-hosted, and post-merge stayed green.

    Switched each retry to use Playwright auto-retrying assertions:
    toHaveCount on tbody tr to confirm the rows are present, then
    toBeVisible on the Moderation header before reading the column index.
    Per-attempt budget is bounded so the 25-attempt loop still fits in the
    120s test timeout in the happy path.

    下载附件