passionworkeer commented on issue #63429: URL: https://github.com/apache/airflow/issues/63429#issuecomment-4045895444
I’d approach this by making PluginsPage the single place that knows when the page is “ready”. Concrete pattern: - add locators for the plugin table, loading indicator, and empty/error states - replace timeout/network-idle waits with web-first assertions such as wait expect(table).toBeVisible() and wait expect(rows).toHaveCount(...) when the data is expected - if there is any DOM manipulation through evaluate(), prefer asserting the rendered plugin metadata from the UI instead of inspecting the DOM manually This keeps the spec focused on behavior and usually makes retries much more stable. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
