[shail-mehta]

Trac ticket: #52895

Adds Comments e2e coverage from ticket #52895.

What

• Creates a published post with comments open
• Views the post on the front end
• Submits a comment through the comment form
• Asserts the comment appears on the Comments admin screen

Why

Ticket #52895 says for Comments: create a post, view it, add a comment, and check that it displays on the comments page.

How

New Playwright spec: tests/e2e/specs/comments.test.js. Post creation and cleanup use the REST API; the comment is submitted through the front-end form while logged in as admin.

Testing instructions

1. Start the local environment if needed: npm run env:start
2. Run: npm run test:e2e -- tests/e2e/specs/comments.test.js
3. Confirm the test passes and the fixture post is removed afterward

Use of AI Tools

• Cursor

[Copilot]

🟡 Changes recommended

The comment textarea locator expects the exact label Comment, but the form uses Comment *, causing the test to time out before submitting a comment.

1 open issue

• Match the required marker in the comment textarea label · New

What changed in this PR

Adds Playwright coverage for front-end comment submission and verification in the Comments admin screen, addressing the Comments workflow described in ticket #52895.

Changes:

• Creates a published post with comments enabled and removes it after the test.
• Submits a unique comment through the front-end form as an administrator.
• Checks the saved comment through REST and verifies its content in the admin list.

File	Description
tests/​e2e/​specs/​comments.test.js	Adds the comment submission workflow, persistence checks, admin verification, and fixture cleanup.

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

No active review issues are reported for the added end-to-end comment submission coverage.

No open issues 🎉

1 resolved since last review

• Match the required marker in the comment textarea label

_{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 shailu25.

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]

Looks good. Posting a comment from the front end is not covered yet (moderate-comments.test.js creates its comments through REST), and the test checks both the saved comment and its row in Comments.

_{AI review · claude-opus-5-5}

[lancewillett]

PR #15729 landed in https://core.trac.wordpress.org/changeset/65323