fix(ui): fix flaky selectNamespace race condition in cypress test

[jonburdo]

Wait for the namespace dropdown button to be enabled before clicking, removing force:true which bypassed actionability checks and caused intermittent failures when the namespace API response hadn't arrived yet.

Description

selectNamespace and shouldHaveNamespaceOptions use click({ force: true }), which bypasses Cypress's actionability checks. When the namespace API response hasn't arrived yet, the dropdown button is disabled (isDisabled={namespaces.length === 0}), but force: true clicks it anyway — no options render, and the test times out looking for role="option" elements.

This is timing-dependent: it only fails when the page takes slightly longer to load (e.g., after a preceding test navigates away from the register page).

All four failures produce the same error:

AssertionError: Timed out retrying after 10000ms: Unable to find an accessible element
with the role "option" and name "namespace-1"
  at RegisterAndStoreFields.selectNamespace (registerAndStoreFields.ts:52:7)

failures

Three failures across unrelated commits spanning a month:

Date	Run	Commit	Branch
Mar 31	23800808381	3088da28	main
Apr 10	24249576848	8f5d7803	main
Apr 27	24991865315	6eb25cfb	main

evidence this is a flaky test

Run 25053512145 on commit d911da74 — identical code, identical CI, different results:

Attempt	Result	Details
2	failure	selectNamespace — 1 failing, 381 passing
3	success	All 382 tests pass

Fix

1. Wait for the dropdown to be enabled before interacting (.should('not.be.disabled'))
2. Remove force: true so Cypress respects normal actionability checks
3. Verify the listbox is visible after clicking before selecting an option

Tested locally

To ensure it doesn't break anything, I made sure this still passes:

cd clients/ui/frontend
npm run test:cypress-ci -- --spec "src/__tests__/cypress/cypress/tests/mocked/modelRegistry/registerAndStoreFields.cy.ts"

How Has This Been Tested?

Merge criteria:

• All the commits have been signed-off (To pass the DCO check)

• The commits have meaningful messages
• Automated tests are provided as part of the PR for major new functionalities; testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has manually tested the changes and verified that the changes work.
• Code changes follow the kubeflow contribution guidelines.
• For first time contributors: Please reach out to the Reviewers to ensure all tests are being run, ensuring the label ok-to-test has been added to the PR.

If you have UI changes

• The developer has added tests or explained why testing cannot be added.
• Included any necessary screenshots or gifs if it was a UI change.
• Verify that UI/UX changes conform the UX guidelines for Kubeflow.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from jonburdo. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• clients/ui/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Copilot]

Pull request overview

This PR hardens the Cypress page-object helpers around the namespace dropdown in the Model Registry “Register model” flow to eliminate timing-related flakiness when namespaces haven’t loaded yet.

Changes:

• Wait for the namespace select control to be enabled before interacting with it.
• Remove click({ force: true }) so Cypress actionability checks are respected.
• Add an explicit assertion that the dropdown listbox is visible before selecting an option.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[jonburdo]

/cc @manaswinidas @ppadti

Does this seem reasonable?