Test your plugins and themes on WordPress 7.2 Beta

Testing steps

1. 1 Go to Tools → Site Health. Check the Secrets API tests on the Status tab and the encryption details on the Info tab.
2. 2 Register and retrieve credentials with the Secrets API helper functions in test code, or via WP-CLI.
3. 3 Confirm stored credentials are encrypted in the database and never exposed in plain text.
4. 4 Confirm secret values are omitted or redacted from REST API responses, debug logs, Site Health info, and XML exports.
5. 5 Make invalid credential calls and confirm they fail gracefully without fatal errors.

Testing steps

1. 1 Render posts and blocks with complex, nested HTML and custom tags.
2. 2 Confirm self-closing tags, script tags, and custom attributes parse without truncation or broken layout.
3. 3 Check for regressions in post content formatting or shortcode expansion.

Testing steps

1. 1 Open a post or page with several blocks.
2. 2 Select a block, click Add Note in the block toolbar, and leave a test note.
3. 3 Open the Settings panel and confirm both the Settings sidebar and the Notes panel stay open at the same time.
4. 4 On a note card, minimize and expand the thread.
5. 5 Add an emoji reaction (👍, ❤️) and confirm the count increments.
6. 6 Open All Notes from the header and filter active vs. resolved notes.
7. 7 Switch admin color schemes and confirm note badges and text stay legible.

Testing steps

1. 1 Open any post or page and open the Post / Page tab of the Settings sidebar.
2. 2 Toggle Status & Visibility between Public, Private, and Password protected.
3. 3 Change the publish date and schedule the post.
4. 4 Switch the author, set/replace/remove a featured image, enter a custom excerpt, and switch templates.
5. 5 Save, refresh, and confirm every value persists.
6. 6 Resize the sidebar and browser window and confirm fields wrap without overlapping.

Testing steps

1. 1 Move through wp-admin screens and inspect the admin bar and the side menu.
2. 2 Zoom to 200%, 300%, and 400% and confirm icons stay sharp.
3. 3 Try each Admin Color Scheme (Users → Profile) and confirm the icons adapt.
4. 4 With a screen reader, confirm icons announce proper labels or are hidden with aria-hidden="true".

Testing steps

1. 1 Open a screen with metaboxes, such as the Dashboard or a classic post edit screen.
2. 2 Open Screen Options and check “Disable metabox rearranging”. Confirm metaboxes can no longer be dragged.
3. 3 Uncheck it and confirm drag-and-drop works again.

Testing steps

1. 1 Test interactive blocks or plugins that use data-wp-html.
2. 2 Confirm trusted markup updates reactively as store state changes.
3. 3 Test client-side navigation on interactive regions and confirm route changes trigger observers without reload regressions.

Testing steps

1. 1 Insert an Icon block.
2. 2 Search for synonyms such as “mail” or “letter” (envelope) and “plus” (+).
3. 3 Confirm the relevant icons appear in the results.

Testing steps

1. 1 Select a Navigation block and click its + inserter.
2. 2 Search for a page, post, or category and confirm results are grouped by content type.
3. 3 Type “Home” and confirm the Home link block appears in the results.
4. 4 Insert an item and confirm its label and link are correct.
5. 5 Paste an external URL (e.g. https://wordpress.org) and confirm the link is created without focus glitches.

Testing steps

1. 1 Insert Heading, Paragraph, Group, Buttons, and Columns blocks.
2. 2 Apply a text gradient under Typography / Color.
3. 3 Adjust width, height, margin, and padding and confirm layouts hold.
4. 4 Apply borders and drop shadows to container and content blocks.
5. 5 On the frontend, confirm gradients and spacing render in Chrome, Safari, and Firefox, on desktop and mobile.

Testing steps

1. 1 In the Site Editor, open Styles → Typography and pick Headings or Text.
2. 2 Find the Shadow control (check the ⋮ menu if hidden) and apply a preset or a custom shadow.
3. 3 Save, then add a Heading block and apply a local text shadow override.
4. 4 On the frontend, confirm shadows render on light and dark backgrounds and text stays legible.

Testing steps

1. 1 In the Site Editor, open Styles and go to Blocks / Elements → Form Elements.
2. 2 Style text inputs, selects, and labels (border, radius, background, typography).
3. 3 Save, then view pages with forms (comment form, Search block, contact forms).
4. 4 Confirm the styles apply consistently across every form field.

Testing steps

1. 1 Set a global font size or text color under Styles.
2. 2 Select a Paragraph or Heading block and confirm its inspector shows the inherited values.
3. 3 Apply a local override, then reset it, and confirm the control reverts to the inherited value.

Testing steps

1. 1 In the Site Editor, open Styles → Blocks and customize a couple of blocks.
2. 2 Back on the block list, switch the filter to Customized and confirm only modified blocks remain.
3. 3 Switch back to All and confirm the full list returns.

Testing steps

Gallery duotone

1. 1 Insert a Gallery with several images and pick a duotone preset.
2. 2 Confirm every image takes the tint, including one you add afterwards.
3. 3 Check the frontend on desktop and mobile.

Site-wide palettes

1. 1 In the Site Editor, open Styles → Colors → Palette → Duotone.
2. 2 Edit a default preset or add a custom shadows/highlights pair and save.
3. 3 In an Image or Cover block, confirm the custom preset appears in the Duotone picker.

Testing steps

1. 1 Insert a Navigation block with several page links.
2. 2 Select a Navigation Link (or Styles → Blocks → Navigation Link) and switch the state selector to current.
3. 3 Apply a distinct color or weight and save.
4. 4 On the frontend, move between pages and confirm the active link styling follows the current URL.

Testing steps

1. 1 Insert a Gallery block with several images.
2. 2 Switch the device preview to Tablet or Mobile and change columns, crop, or aspect ratio.
3. 3 Switch back to Desktop and confirm the desktop layout is untouched.
4. 4 Add custom CSS for a responsive state in the Advanced panel.
5. 5 Check the frontend in responsive mode and confirm styles apply at each breakpoint.

Testing steps

1. 1 Go to Appearance → Themes and activate Ipsum.
2. 2 In the Site Editor, switch between its style variations.
3. 3 Try the bundled patterns (headers, post lists, footers, callouts).
4. 4 Check the Index, Single, Page, 404, and Archive templates.
5. 5 Add varied content (images, quotes, tables, description lists) and check the frontend on desktop, tablet, and mobile.
6. 6 Switch the sandbox PHP version and confirm Ipsum works from PHP 8.2 to 8.5.

Testing steps

1. 1 In a Chromium browser, upload an animated GIF or WebP in the editor or via Media → Add New.
2. 2 Insert it and switch between Thumbnail, Medium, and Large; confirm every size still animates.
3. 3 Upload AVIF, WebP, and HEIC files in the Media Library and confirm sub-sizes are generated in the browser.
4. 4 In Safari or Firefox, confirm uploads fall back to server-side processing without failing.

Testing steps

1. 1 On a site with many images, open the media inserter and browse, search, and filter.
2. 2 Insert a Gallery and choose “Use attached images”; confirm it shows the post’s attachments.
3. 3 In a static gallery, sort images by date, title, or drag-and-drop.

Testing steps

1. 1 Insert an Image block, open the crop tool, crop or rotate, and save.
2. 2 In Media → Library, confirm the cropped image is linked to its original.
3. 3 Re-open the editor on the cropped image and confirm you can re-adjust from the original.

Testing steps

1. 1 Did any plugins or themes deactivate automatically after the update?
2. 2 Check the WordPress Site Health tool. Did you find any new warnings or issues?
3. 3 Check templates and patterns, and then actual posts and pages, for layout problems. Are all the elements lined up properly? Is spacing correct?
4. 4 Test links and permalinks to ensure there are no 404 or other errors.
5. 5 Do design elements, images, and media look the way they should? Do media files load and play properly?
6. 6 How are the sitemap and robots.txt files working?
7. 7 Can users at every permission level get to the admin dashboard without errors? Does each level show the right tools, and do they work?
8. 8 Does your site have custom blocks? Add content to a new block. Edit it. Now edit a block that already has content.
9. 9 Create a new post: add content, copy/paste text, add a few different kinds of media, save, and watch the console for issues.
10. 10 Create a new page, add content, and open it in several different browsers.
11. 11 Open the browser’s developer tools. Check each tab, plus the console, for errors, warnings, or notices.
12. 12 Check the error log file for notices, warnings, and errors — especially fatal errors.
13. 13 Have you set up scheduled posts or automated tasks (like backups)? Can you find them in the admin? Do they run on schedule?
14. 14 Check integrated services like payment gateways or analytics. Do they still connect? Do they execute?
15. 15 Open your site in different browsers and make sure all functionalities work as expected.
16. 16 Check site performance: page loading, API calls, database requests — on a few devices if you can.
17. 17 Use browser tools to simulate low bandwidth. How does your updated site handle it?
18. 18 Test accessibility basics: keyboard navigation, contrast, screen-reader behavior.
19. 19 Check your forms — contact, checkout, login, and more. Can you fill all the fields? Submit and clear? Does the data end up in the right place?
20. 20 Can you upload media? Edit images? Does gallery functionality work properly?
21. 21 Check your theme. Does the basic theme look right? Did Site Editor or Customizer customizations change in the upgrade?