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.
X-comment from +make.wordpress.org/core: Comment on Migrating WordPress E2E tests to Playwright
X-comment from +make.wordpress.org/updates: Comment on Test Team Update for 21 March 2022
With WordPress 5.9 introducing full site editing and WordPress 6.0 in the works, it’s time for another round of questions. If possible, please focus questions specifically around WordPress 6.0 as those will be the most high impact to address ahead of this upcoming release. You are welcome to submit questions using the form below or to leave them as a comment on this post by March 30th, 2022.
Like the last few times, keep in mind that because various pieces are still very much in progress some answers will be less definitive and more context setting. This is especially true for features/milestones that are planned for the 6.0 release and beyond.
Where will you share the answers?
I’ll share a recap post on this blog (Make Test). Questions will either be grouped with corresponding answers for easy review or will be shared in one post, depending on the number of submissions received. I will track down answers to every question and share my work as I go by creating a collaborative Google doc where people can help find answers or simply see how the work evolves. I very much welcome collaboration here!
While the main result will be a lovely list of answers, this collective effort will also be useful for future documentation updates and potential tutorials. Once the post is published, I will follow up via email with everyone who left their email and a question in the form. For anyone who leaves a question as a comment on this post, I will @ your username in the recap post so you don’t miss out too!
For more information about this 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.
The meeting started on 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/. here.
@hellofromtonya made a summary of last week in Test:
@Ugyen asked if there’ll be a 5.9.3 release before 6.0, @audrasjb confirmed 5.9.3 release in the upcoming weeks.
@pbearne refreshed the @covers PR
@hellofromtonya agreed to move forward with the batch approach to make a review and commit process easier for this big PR
@tykoted joined his first meeting
@hellofromtonya reminded about the need of having one or two people that would lead the Test Handbook project. Together with @boniu91 agreed that summary post will be a good place to promote this opportunity.
@justinahinon described that moving e2e tests to Playwright in 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/ is going quite well. He’s also working together with @juhise on moving existing tests to Playwright
@hellofromtonya reminded why we are in the process of switching to the Playwright
@pbearne offered Tugboat as a tool that could help the Test Team, he’ll provide more details soon.
Test Team is looking for a volunteer or two as lead(s) to shepherd Test Handbook forward. If you’re interested in this role, please leave a meesage.
The meeting started on 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/. here. With no agenda, the chat was open floor discussions.
@costdev asked: What projects or specific goals are targeted for 6.0? @hellofromtonya replied that 6.0 roadmap of the key features and refinements to be built for this major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality.. The Test Team will support that effort.
Team discussed other projects and goals not necessarily specific to 6.0:
@covers and #53010.@hellofromtonya shared a bigger picture framework / thinking for testing:
Tests express the intended and expected behavior of how the code should and shouldn’t behave under different conditions. When tests do this, they are a wonderful source for learning.
Testing itself fuels the feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. back into the development process to know what does and doesn’t work as expected.
How?
The goals aren’t to build more tests. Rather, the goals are to build the tests that are needed to validate the code works as expected under different conditions to further help improve the user experience and get feedback fed back into the development cycles.
Team discussed whether to start with planning the test suite reorganization or getting the @covers tags added / corrected.
The team decided to prioritize the @covers tags in order to ensure the code coverage reports are accurate to point to where more work is needed.
Team then discussed how to divide the auditing work to finish the @covers PR and get it merged.
Restructuring the handbook raises the potential for more team members to work on the other initiatives. Since it feeds the numbers, confidence and accuracy of the team, it helps with everything else. Coverage reports won’t help increase the number of test team contributors, so I’m tempted to say that our first big drive should be to work on the handbook. If there’s things that need to be done in advance of handbook entries, such as establishing a new structure for the tests, that should be done in order to help 1) achieve the goal of restructuring and 2) provide information for the handbook entries.
by @costdev
Props to @boniu91 for proofreading.
X-comment from +make.wordpress.org/core: Comment on Proposal to Start a News blog on developer.WordPress.org
