The Test Team helps manage testing and triage across the WordPress ecosystem. They focus on user testing of the editing experience and WordPress dashboard, replicating and documenting bug reports, and supporting a culture of review and triage across the project.
This post is the twenty-fifth call for testing as part of the Full Site Editing Outreach Program. For more information about this experimental program, please review this FAQ for helpful details. To properly join the fun, please head to #fse-outreach-experiment in Make Slack for future testing announcements, helpful posts, and more will be shared there.
WordPress 6.3 just launched this week, bringing with it the ability to build out all parts of your site without leaving the Site Editor. While we’ve tested everything leading up to the release, it’s time now to see how all of the pieces are landing with a fresh take, especially with all of the fixes found during the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. and RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. periods, and to look ahead to where 6.4 aims to iterate.
To do this, this call for testing will go through a “starting from scratch” experience, from changing styles, using and creating patterns, creating a few pages, and setting up a menu. As part of this, you’ll explore new tools, like the Command Palette, and well loved tools, like List View. This test is intentionally more open ended to encourage exploration and to gather user experience feedback. It’s ultimately not about testing individual, new features and is more centered on testing how the features continue to come together.
Since the 6.4 cycle is a bit shorter than others, this call for testing will only be open for two weeks rather than three so additional testing can occur as more features and refinements are released.
To use a prebuilt test site:
- Open this link only once: https://app.instawp.io/launch?t=fse-testing-call-25&d=v2
- Please do not repeatedly open this link as it creates a new site each time and there’s a limit of 50 sites that can be created.
- This will launch a site for you to use for up to 24 hours. Select “Magic Login” to log in to the wp-admin dashboard.
- Save the link to your site so you can access it again during the test.
To set up your own test site:
- Have a test site using the latest version of WordPress. It’s important this is not a production/live site.
- Install and activate the Twenty Twenty Three by going to Appearances > Themes.
- Install and activate Gutenberg 16.4 or the latest version of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ after 16.4.
If you have any issues with manual setup, just comment on the post or pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” me (@annezazu) in WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..
What follows are open ended tasks to complete, intentionally listed without detailed instructions in order to better stress test what’s been shipped in 6.3 and discover where the experience can be clarified:
- Pick and save a new style variation.
- Add a border to all Image blocks on your site and change the size of all H2 headings using Styles.
- Create an “About” page and turn on the Top Toolbar setting. Copy and paste content from this Google Doc, noting any issues in pasting with the format or content.
- Create a “Resume” page with a few different headings and use the Table of Contents blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. to better organize the page.
- Change the size and alignment of the Page title in your Pages template.
- At various points, use the Command Palette to either navigate between parts of your site or open various tools, like List View, or settings, like Top Toolbar.
- Create a menu that just lists your About page, a link to your WordPress.org profile with the Social Icons block, and a Search block.
- Create a synced pattern that details how to get in touch with you and add it to your “About” and “Resume” pages where you see fit.
- Duplicate the synced pattern from the Patterns section and make an unsynced version.
If you’d like to go further and have time to do so, please explore the following: creating pages and editing the template surrounding the page & building and inserting more patterns, synced and unsynced.
If you get stuck at any point, please note it in the comments with details around where you tried to attempt to complete the task.
What to notice:
- Did the experience crash at any point?
- Did the saving experience work properly?
- What did you find particularly confusing or frustrating about the experience?
- What did you especially enjoy or appreciate about the experience?
- What would have made this experience easier for site building and for writing new content?
- Did you find that what you created matched what you saw on your site?
- Did it work using Keyboard only?
- Did it work using a screen reader?
- Did it work while using just a mobile device? Shout out to @nomadskateboarding for this addition!