[adimoldovan]

Trac ticket: https://core.trac.wordpress.org/ticket/66392

applications-passwords.test.js failed in the parallel project when two copies of it ran at the same time. Each test used the admin user and revoked all of its application passwords, so each copy saw and deleted the passwords of the other.

Each test now starts logged out, creates its own subscriber with userFactory, and signs in as that user. The REST checks read that user's passwords by ID, not through /users/me. userFactory deletes the user, and so its passwords, when the test ends.

Testing Instructions

1. Run npm run test:e2e -- --project=parallel tests/e2e/specs/profile/applications-passwords.test.js --repeat-each=10 --retries=0. All 30 tests pass.
2. Run npm run test:e2e -- tests/e2e/specs/profile/applications-passwords.test.js. All 3 tests pass.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Code change, test runs and this description.

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[Copilot]

🟢 Approval recommended

No active review issues are recorded for the application-password test isolation changes.

No open issues 🎉

What changed in this PR

This PR isolates the application-password end-to-end tests so parallel runs no longer interfere with each other’s passwords.

Changes:

• Start each test logged out, create a dedicated subscriber with userFactory, and sign in.
• Query application passwords by the test user’s ID instead of /users/me.
• Rely on factory user cleanup instead of explicitly revoking passwords before and after each test.

File	Description
tests/​e2e/​specs/​profile/​applications-passwords.test.js	Use per-test users and user-specific REST queries to isolate parallel runs.

_{Review effort: Balanced}

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props adrianmoldovanwp.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[lancewillett]

Verified the isolation benefit using the existing spec with two workers, --repeat-each=10 --retries=0, and a clean database before each run: baseline had 7 failures and 23 passes; this revision passed all 30 cases with the same assertions.

Baseline failures included another concurrent copy’s password remaining after revocation, and a newly created password disappearing before its REST assertion. Per-test users isolate those records; final cleanup left no test users or application-password metadata. All four E2E CI jobs also passed.

No blocking findings remain.

_{AI review · gpt-6}

[lancewillett]

PR #15902 landed in https://core.trac.wordpress.org/changeset/65402