docs: draft call for testing for Make/Test by devmuhib009 · Pull Request #869 · WordPress/presence-api

devmuhib009 · 2026-10-21T04:57:27Z

This provides the Call for Testing draft for Make/Test with Playground scenarios to fulfill #550's user testing merge criterion.

Fixes #835

Use of AI Tools

AI assistance: Yes
Tool(s): Google Antigravity
Model(s): Gemini
Used for: Structuring test scenarios and drafting the Call for Testing text.

github-actions · 2026-10-21T05:00:42Z

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 devmuhib, iamchitti, huzaifaalmesbah, joefusco.

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.

i-am-chitti · 2026-10-21T17:55:41Z

+   - Does the "Editors" column display an avatar stack for who is actively editing?
+   - Does the count and avatar list stay neatly within the table column without overflowing?
+
+### Task 3: Post Locking and Takeover


You need a second user to take over a lock. With one user, no lock notice shows up. The "Editing together" scene in Option A shows a takeover.

i-am-chitti · 2026-10-21T17:58:22Z

+
+---
+
+## Where to Report Feedback


The Test handbook asks the version to test, and a list of known issues. Could you add those?

huzaifaalmesbah · 2026-10-22T03:33:41Z

Hi @devmuhib009, thanks for picking this up! Adding a few notes to @i-am-chitti's, checked against the handbook's checklist:

Intro and timeline (optional, but on the checklist): a line on who is asking for testing, and an end date for feedback, would help testers.
What is it? Say in one line that post locks look the same and only moved out of post meta (An open editor makes every cached post query stale on each Heartbeat tick #548), so testers know what "working" looks like.
Version: the blueprints install the preview-main build, not the 0.18.3 release, so the post should say which one is being tested.
Scenes: in Option A, name the scene each task needs (e.g. "Editing together" for the takeover task).
Screenshots: add a few from desktop and mobile; fix: show the admin bar presence node on phones and spell out hover-only names on touch #830 and Screens haven't been checked on touch devices and small screens #833 already have some.
Known issues: add a short list, or a link to an issues filter.
Reporting: ask testers to include browser, OS, device and steps, or point to the Test Reports format.
Publishing: tag #needs-testing, and decide between Make/Test and Make/Core (the handbook notes Make/Core gets more visibility). If it goes on Make/Core, it can be cross-posted to Make/Test.

@josephfusco, should this file be merged into the repo, or only reviewed here before it goes up as a Make post?

Happy to help triage the feedback once it's live.

josephfusco

Thanks for drafting this! To answer Huzaifa's question: it's best reviewed here and then posted to Make/Test rather than merged, so this PR can close once the post is up. One more for Task 1: the admin bar leaves out your own account, so a second tab as the same user shows nothing there; the scenes in Option A put someone else in it. With Deepak's and Huzaifa's notes, that should cover it.

josephfusco · 2026-10-23T15:46:17Z

One small correction for the screenshots: #830 has the phone ones, but #833 has none.

josephfusco · 2026-10-26T16:54:57Z

Hi Muhib, are you still up for working through Deepak's and Huzaifa's notes? Once they're in, Huzaifa offered to help get it posted on Make/Test.

huzaifaalmesbah · 2026-10-28T03:46:13Z

Hi @josephfusco, I’ve spoken with @devmuhib009 . He has been away from work for the past few days due to his involvement in organizing the WordPress Campus Connect event, and he’ll need a few more days before he returns.

In the meantime, should we go ahead and work on the remaining updates and prepare the post for Make/Test, so it’s ready to publish?

devmuhib009 · 2026-10-29T06:20:09Z

Thanks all for the helpful review notes! I have updated CALL_FOR_TESTING.md to incorporate the feedback:

Clarified build version (preview-main) and noted that post locks move to wp_presence without UI changes (An open editor makes every cached post query stale on each Heartbeat tick #548).
Updated Option B to "Playground with Demo Data", noting that separate browser instances don't share state and pointing to the demo helper button.
Pointed Tasks 1, 2, and 3 to Option A's "Editing together" scene, noting that the admin bar intentionally excludes your own user.
Updated Task 4 to use Settings > General or post edit screens with the demo helper button.
Added timeline (through November 15, 2026), #needs-testing tag, known issues link, mobile screenshot reference (fix: show the admin bar presence node on phones and spell out hover-only names on touch #830), and the Test Reports format.

Please let me know if anything else needs adjusting before we publish to Make/Test!

i-am-chitti

Thanks @devmuhib009, this is close! A few notes -

i-am-chitti · 2026-10-30T18:05:41Z

+
+### Option A: Interactive Testing with Simulated Collaborators (Recommended)
+This instance runs the companion `presence-scenes` tool, which simulates real-time virtual users editing posts and navigating the admin:
+👉 **[Launch Playground with Simulated Collaborators](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/WordPress/presence-api/main/blueprint-scenes.json)**


The scene lasts under a minute, then removes its users and post. Worth saying how to replay it?

Suggested change

👉 **[Launch Playground with Simulated Collaborators](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/WordPress/presence-api/main/blueprint-scenes.json)**

👉 **[Launch Playground with Simulated Collaborators](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/WordPress/presence-api/main/blueprint-scenes.json)**

*(The scene lasts under a minute. To replay it, open `/wp-admin/edit.php?presence_scene=editing-together`.)*

i-am-chitti · 2026-10-30T18:05:58Z

+👉 **[Launch Playground with Simulated Collaborators](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/WordPress/presence-api/main/blueprint-scenes.json)**
+
+### Option B: Playground with Demo Data
+This instance comes pre-seeded with 100 demo posts and users, along with a demo helper button in the admin to simulate saves from other users:


It's 100 demo users, but only a handful of posts.

Suggested change

This instance comes pre-seeded with 100 demo posts and users, along with a demo helper button in the admin to simulate saves from other users:

This instance comes pre-seeded with 100 demo users and a few demo posts, along with a **Demo** bar to simulate saves from other users:

i-am-chitti · 2026-10-30T18:10:17Z

+### Task 1: Admin Bar Real-Time Presence
+*Use Option A (Simulated Collaborators).*
+
+1. Open `wp-admin` and look at the presence/heart icon in the top toolbar.


The heart with the countdown is the Presence Debugger's Heartbeat timer, so testers may mix the two up. The presence menu is the faces and "N online" next to Howdy.

Suggested change

1. Open `wp-admin` and look at the presence/heart icon in the top toolbar.

1. Open `wp-admin` and find the faces and "N online" count next to **Howdy** in the toolbar.

i-am-chitti · 2026-10-30T18:10:50Z

+2. Observe the counter updating as simulated collaborators move across screens.
+3. Hover or use keyboard navigation (Tab) to open the presence menu.
+4. **What to verify**:
+   - The toolbar shows other active users (your own user is intentionally excluded from the count).


The count includes you; only the faces and menu leave you out.

Suggested change

- The toolbar shows other active users (your own user is intentionally excluded from the count).

- The faces and menu show other people (not you), and the "N online" count includes you.

i-am-chitti · 2026-10-30T18:25:54Z

+1. Navigate to **Posts > All Posts**.
+2. Locate posts that simulated collaborators are actively editing.


The scene's post only shows up after a reload.

Without reload After reload

Suggested change

1. Navigate to **Posts > All Posts**.

2. Locate posts that simulated collaborators are actively editing.

1. A few seconds after the scene starts, reload **Posts > All Posts**.

2. Find **Launch checklist**, the post the collaborators are editing.

i-am-chitti · 2026-10-30T18:26:32Z

+3. Click **Take over**.
+4. **What to verify**:
+   - The lock dialog indicates that another user is currently editing the post.
+   - Taking over grants you editing access smoothly, transferring the lock row in `wp_presence`.


Testers can't see the wp_presence table in Playground.

Suggested change

- Taking over grants you editing access smoothly, transferring the lock row in `wp_presence`.

- Taking over closes the dialog and lets you edit the post.

i-am-chitti · 2026-10-30T18:27:07Z

+1. Navigate to **Settings > General** (or open an existing post in the editor).
+2. Click the floating **Pretend another user saved** helper button (or save the setting via a second tab).


Playground opens posts in the block editor, which hides both the Demo bar and the notice, so Settings > General is the reliable path. Also, the buttons read Save as {name}, and a second tab won't trigger the notice, since it ignores your own saves.

Suggested change

1. Navigate to **Settings > General** (or open an existing post in the editor).

2. Click the floating **Pretend another user saved** helper button (or save the setting via a second tab).

1. Navigate to **Settings > General**.

2. In the **Demo** bar at the top, click a **Save as {name}** button.

i-am-chitti · 2026-10-30T18:28:03Z

+
+## How to Report Feedback
+
+Please share your testing report following the [Make/Test Reporting format](https://make.wordpress.org/test/handbook/call-for-testing/#testing-reports):


Suggested change

Please share your testing report following the [Make/Test Reporting format](https://make.wordpress.org/test/handbook/call-for-testing/#testing-reports):

Please share your testing report following the [Make/Test reporting format](https://make.wordpress.org/test/handbook/call-for-testing/#how-to-report):

i-am-chitti · 2026-10-30T18:28:26Z

+
+You can post feedback:
+- As comments on the Make/Test post, or
+- Directly on the [Presence API GitHub Issues](https://github.com/WordPress/presence-api/issues) tracker with the `#needs-testing` tag.


#needs-testing is the tag for the Make post itself; the repo has no such label.

Suggested change

- Directly on the [Presence API GitHub Issues](https://github.com/WordPress/presence-api/issues) tracker with the `#needs-testing` tag.

- Directly on the [Presence API GitHub Issues](https://github.com/WordPress/presence-api/issues) tracker.

docs: add call for testing draft for Make/Test

55e1130

devmuhib009 marked this pull request as ready for review October 21, 2026 05:00

devmuhib009 requested review from i-am-chitti and josephfusco as code owners October 21, 2026 05:00

i-am-chitti reviewed Oct 21, 2026

View reviewed changes

Merge branch 'main' into docs/835-call-for-testing

1b77ec5

josephfusco added [Type] Documentation Documentation to be added or enhanced [Area] Infrastructure Issues for the repository infrastructure labels Oct 23, 2026

josephfusco reviewed Oct 23, 2026

View reviewed changes

Merge branch 'main' into docs/835-call-for-testing

ac0e80b

josephfusco assigned huzaifaalmesbah Oct 26, 2026

josephfusco mentioned this pull request Oct 26, 2026

📌 Tracking: Presence API path to Core #550

Open

24 of 36 tasks

Merge branch 'main' into docs/835-call-for-testing

e10b0cc

docs: update call for testing draft from review feedback

bc0ad8f

i-am-chitti reviewed Oct 30, 2026

View reviewed changes

	👉 [Launch Playground with Simulated Collaborators](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/WordPress/presence-api/main/blueprint-scenes.json)
	👉 [Launch Playground with Simulated Collaborators](https://playground.wordpress.net/?blueprint-url=https://raw.githubusercontent.com/WordPress/presence-api/main/blueprint-scenes.json)
	(The scene lasts under a minute. To replay it, open `/wp-admin/edit.php?presence_scene=editing-together`.)

	This instance comes pre-seeded with 100 demo posts and users, along with a demo helper button in the admin to simulate saves from other users:
	This instance comes pre-seeded with 100 demo users and a few demo posts, along with a Demo bar to simulate saves from other users:

	1. Open `wp-admin` and look at the presence/heart icon in the top toolbar.
	1. Open `wp-admin` and find the faces and "N online" count next to Howdy in the toolbar.

	- The toolbar shows other active users (your own user is intentionally excluded from the count).
	- The faces and menu show other people (not you), and the "N online" count includes you.

		1. Navigate to Posts > All Posts.
		2. Locate posts that simulated collaborators are actively editing.

	- Taking over grants you editing access smoothly, transferring the lock row in `wp_presence`.
	- Taking over closes the dialog and lets you edit the post.

		1. Navigate to Settings > General (or open an existing post in the editor).
		2. Click the floating Pretend another user saved helper button (or save the setting via a second tab).


		## How to Report Feedback

		Please share your testing report following the [Make/Test Reporting format](https://make.wordpress.org/test/handbook/call-for-testing/#testing-reports):

	- Directly on the [Presence API GitHub Issues](https://github.com/WordPress/presence-api/issues) tracker with the `#needs-testing` tag.
	- Directly on the [Presence API GitHub Issues](https://github.com/WordPress/presence-api/issues) tracker.

Conversation

devmuhib009 commented Oct 21, 2026

Uh oh!

github-actions Bot commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

huzaifaalmesbah commented Oct 22, 2026

Uh oh!

josephfusco left a comment

Choose a reason for hiding this comment

Uh oh!

josephfusco commented Oct 23, 2026

Uh oh!

josephfusco commented Oct 26, 2026

Uh oh!

huzaifaalmesbah commented Oct 28, 2026

Uh oh!

devmuhib009 commented Oct 29, 2026

Uh oh!

i-am-chitti left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

github-actions Bot commented Oct 21, 2026 •

edited

Loading