Fixed flaky staff password acceptance tests

[9larsons]

What changed

• wait for the password form's intended field to receive focus before filling either password path
• reuse the password field locators throughout the current-user scenario

Why

The password form applies focus 100 ms after it opens. Playwright fills password inputs in separate focus/select and text-insertion steps, so the delayed focus could land between those steps and redirect text into a different field. That caused the self-password validation assertion to intermittently observe the wrong validation state on main.

Failed run: https://github.com/TryGhost/Ghost/actions/runs/29460895269/job/87504062007

Validation

• focused password acceptance spec: 6 consecutive passes, 12/12 tests
• full Admin acceptance suite: 174/174 tests

[coderabbitai]

Walkthrough

The staff password acceptance tests now verify that the new-password field is focused when opening another staff member’s password form. The own-password flow captures password and save controls, asserts focus on the old-password field, fills the new and confirmation passwords, verifies the validation message, and then fills the old password.

Possibly related PRs

• TryGhost/Ghost#29374: Updates related staff-password acceptance test focus assertions in the same file.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the main change: fixing flaky staff password acceptance tests.
Description check	✅ Passed	The description is directly related to the test flakiness fix and explains the focus-timing issue.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/fix-staff-password-test-focus

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[nx-cloud]

🤖 Nx Cloud AI Fix

Ensure the fix-ci command is configured to always run in your CI pipeline to get automatic fixes in future runs. For more information, please see https://nx.dev/ci/features/self-healing-ci

---

View your CI Pipeline Execution ↗ for commit 2cd3bcd

Command	Status	Duration	Result
nx run @tryghost/admin:test:acceptance	✅ Succeeded	2m 38s	View ↗
nx run-many -t test:unit -p @tryghost/admin	✅ Succeeded	2m 17s	View ↗
nx run ghost-monorepo:lint:boundaries	✅ Succeeded	20s	View ↗
nx run-many -t lint -p @tryghost/admin,ghost-mo...	✅ Succeeded	53s	View ↗
nx run @tryghost/admin:build	✅ Succeeded	36s	View ↗
nx run-many --target=build --projects=tag:publi...	✅ Succeeded	<1s	View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗

---

☁️ Nx Cloud last updated this comment at 2026-07-16 12:31:40 UTC