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.
If you’d like to help test Full Site Editing, please join the FSE Outreach Program. You can find current calls for testing for this program here and you can join the fun in #fse-outreach-experiment.
For context on this program, please review this post shared on May 1st kicking off this experiment
Program Goal:
Help improve the Full Site Editing experience by gathering feedback from WordPress site builders. This program does not replace sharing feedback on GitHub so, whether you’re a part of this program or not, please keep sharing there.
Approach:
We’ll start with more limited common user experiences and, over time, will move to more complex testing (adding in different themes, plugins, etc). For example, this means that we won’t be testing across a wide range of themes, but will start with a fairly simple setup 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/ and a FSE ready 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. theme. While this might mean the program starts off more slowly, over time, the hope is that we get into a fast pace with multiple items to test each month and feedback integrating into the Gutenberg team’s workflow.
Communication:
All calls for testing and summaries will be shared on Make Test with a cross post to Make Core. Here are the tags you can use to follow along specifically:
As much as possible, please communicate in #fse-outreach-experiment openly about the program itself. While you can always DM @annezazu separately, it’s preferred to communicate in the open. When you ask your question in the open channel, it helps everyone learn, even the people who might have been too shy to ask the same thing.
If you have questions about the FSE project separate from this outreach program, it’s best to ask in #coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor,
To help stay up to date on the FSE work itself, please review this post on ways to keep up with FSE.
Amplification:
To get the word out to more people who can help test, the following pathways are used to amplify the calls for testing:
Format:
A prompt will be shared on Make Test with details about testing environment, a testing script to follow, and where to give feedback by when. For now, feedback will be processed and reported appropriately. From there, a follow up post summarizing the findings will be posted.
In time, the ideal is to have a faster cycle of prompts and feedback that might look more like this but this depends on capacity of the wider community:
To start though, the prompts will be slower paced and spaced out in order to get our bearings and to align with the current pace of work being done.
Tools:
While you are free to use your own testing environment and follow these instructions, we wanted to share basic tools you’ll need to get started:
Last updated:
