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.
Please drop by any time in SlackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. with questions or to help out.
We are in the last lap for the test handbook completion!
@sirlouen reported that he had already contacted the MetaMetaMeta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team to schedule a date to start syncing and also mentioned that the project is 99.99% complete, and once a date is confirmed, they will complete the final administrative tasks and proceed. @sirlouen also noted that @dd32 was copied in on the communication.
@sirlouen also shared that he is going to edit all current documentation pages to add a GitHubGitHubGitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ link and indicate that the pages are outdated. Once the sync is complete, those pages will be removed and replaced with new content. He also mentioned that work can begin on one or two GitHub pages now, starting with the badges page.
@nikunj8866 emphasized that the slugs needs to be observed as same before removing and archiving old pages
A few Tickets were pending Reviews and volunteers were assigned. We are almost there. All tickets were reviewed by meetings end and merge ready. @sirlouen will proceed to merge
Proposal for creating an Archive Section in the Handbook. The archive section was supported in the last meeting and these two pages are among those to be first archived.
We need to build a new page for GutenbergGutenbergThe 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/testing @sirlouen is moving to Gutenberg tests and will do build the page
4. Open Floor
No additional topics were brought up during the open floor section of the meeting.
Call for Testing Several Issues are available for testing ahead of the 6.9 release. Let’s help collaborate on these as well. Here is a short list but more will surely be found especially after the betaBetaA 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. release last night
Collaboration: add blockBlockBlock 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.-level comments:
We usually have 2 meetings held every week and the times have been listed bellow for next week. an adjustment has been made to include the WordPress 6.9 Test Scrub and will soon be listed
Note-taker and facilitator selection for the next meeting We encourage all members to contribute to the team chat and we now welcome Note Takers and Facilitators. This is a great time to get involved in the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. team. Have you recently joined and you don’t know where to go. Start here (No Skills Required)
Today’s session facilitator and note-taker is @mosescursor
This week’s facilitator and note-taker is @mosescursor
Test Team Discussions
Time to Review the Test Handbook Overhaul:
We are in the last lap for the test handbook completion!
Collaboration: add blockBlockBlock 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.-level comments:
The RC2 release of WordPress 6.8 is scheduled for the 1st of April. Please check the detailed overview of the release schedule for WordPress 6.8. Join the Release Party 1st April @5PM CEST in #core to test and provide the feedback.
GutenbergGutenbergThe 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/ 20.5 was released on Thursday, March 20th. Checkout the milestone for the issues that were part of the 20.5 release.
4. Test Team Announcements
Week in Test Post: Wondering where you can contribute and learn? The Test Team’s got you covered.
SirLouen first raised the recurring issue about the lack of a place for test team members to comment on improvement ideas and proposed a solution to use the following site to add ideas and comments for future meetings. You can see the topics without registering, but if you want to propose new topics, you can send a direct message to @SirLouen on the Slack server with an email address to add you.
Krupa proposed another additional approach to add ideas for next meetings: A thread will be opened 2 days before each meeting in the #core-test Slack channel, and you can add your ideas there.
Help test WordPress 6.8 and share your feedback. WordPress 6.8 will be released on April 15, 2025
Gutenberg 20.6 is scheduled for release on Wednesday, April 2, 2025. Checkout the milestone for Gutenberg 20.6
8. Open Floor
SirLouen first raised an issue about the testing workflow implementation gap, insufficient test reports, QA concerns and a lack of a stable testing team, and proposed a solution: Introducing an unofficial mentorship program to help new contributors get involved in testing more details here, with the primary goal of building a stable testing team that could be referenced similar to the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. team, editor team, or performance team.
OGlekler noted that testing is being promoted in Core Contributor meetings and suggested promoting testing in other places as well. We will do a brainstorming session to discuss this. Here is a thread to brainstorm the ideas. Also mentioned that the previous success with the Contributor Mentorship Program came from social media promotion, and pointed out the challenge with gaining volunteer motivation and commitment over time.
Krupa acknowledged the need for a structured testing workflow and a stable team, but volunteer participation can be a challenge and the suggested mentorship program had potential to be a stepping stone for new contributors to get involved in testing. More insights are needed to ensure proposed changes are both sustainable and practical.
SirLouen will help to develop a roadmap for progressive improvements to the testing workflow, with a focus on building a reliable testing team as the first priority.
We encourage you to participate in any of the ways available, Slack #core-test channel, with a comment in this post, directly in the next meeting or adding up to the Shared Doc Notes commented in this post.
Props to krupajnanda for peer reviewing this meeting recap.
The BetaBetaA 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. 3 release of WordPress 6.8 is scheduled for next Tuesday, March 18th. Please check the detailed overview of the release schedule for WordPress 6.8. Don’t miss the Release Party in #core to test and provide feedback! :dart:
GutenbergGutenbergThe 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/ 20.4 was released on Wednesday, March 5th. Check out the milestone for the issues that were part of the 0.4 release.
4. Test Team Updates
Week in Test Post: Details for new contributors and ongoing activities.
Test Team Update: Progress on overall team contributions and performance shared.
5. Focal Group Updates
We are in the 6.8 release cycle and only 2 weeks from our first RCRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. release.
Check out what to expect in the WordPress 6.8 release: Roadmap to 6.8
6. Questions/Blockers
@sirlouen questioned about the testing suggestions doc: https://docs.google.com/document/d/1Q7Kzs-78XvrAjnjG_MhBJR6bSBk80rvzwnV90iYTjhg/edit?tab=t.0
Help test WordPress 6.8 and share your feedback. WordPress 6.8 is going to be released on April 15, 2025
Gutenberg 20.5 is scheduled for release on Wednesday, March 19th. This will be the first version of Gutenberg to be merged into WordPress 6.9.
8. Open Floor
The discussion started with an invitation for participants to share thoughts or raise topics for discussion. New contributors were directed to the bookmarks folder in the channel for helpful resources.
Key Points Discussed:
Addressing Ethical Practices in Testing:
@vgnavada: Highlighted the issue of copying someone else’s test case, including the exact screenshot and text copy, and presenting it as their own, pointing out the unethical nature of this practice.
@sirlouen: Stated that the other user likely reused the same steps to confirm the patch without taking the time to do the work again from scratch. He described this as poor testing practice, as it would have been better to try different approaches to expand the testing cases.
@oglekler: Acknowledged that such issues hadn’t been caught before but noted that it should be looked into now. While copying someone else’s work is demotivating, She reassured that it wouldn’t benefit the person doing it and advised not to worry too much about it.
@krupajnanda: Expressed understanding of the concern and emphasized that copying someone else’s work, especially when it involves significant effort, is not the right way to contribute. She suggested that more eyes should be on each ticket to offer different perspectives and solutions.
Bridging the Gap: Improving Collaboration Between QA and Development Teams
Challenges Identified:@sirlouen mentioned the often it observed that patches get approved with minimal verification, which can lead to unexpected issues down the line. When tickets don’t clearly outline use cases, it can slow down testing and create confusion. We need a clear mechanism for this situation to be resolved.
Proposed Solutions: Introduce a needs-use-cases tag to ensure clear reporting and smoother testing to encourage detailed testing reports and context from committers.
Next Steps:@mukesh27 supported the ideas and suggested a blog post to drive awareness and change.
The meeting wrapped up with a reminder to participants that discussions and questions are always welcome in the Test Team channel. The community is encouraged to continue contributing and collaborating outside of scheduled meetings.
@krupajnanda thanked @sirlouen for their feedback and assured them that the team would work on resolving the gaps identified. She acknowledged the active participation of the team during the meeting and emphasized that team members can raise questions or start discussions anytime in the Test Team channel.
Takeaways
The main takeaway is that better teamwork, clear communication, and accountability between QA and development teams are key to success. When both sides work together with honesty, transparency, and shared responsibility, things run more smoothly and lead to better results.
Thank you, @krupajnanda, for the peer review and for helping me write this post.
Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!
Welcome! Here’s a guide to help you join and participate in the Release Parties scheduled for WordPress 6.8. If you are new to attending a release party, this will help you get started.
This is where the release party happens! Use this link to join: #core channel
Arrive Early and Be Prepared:
Join the channel about 10 minutes before the scheduled time and make sure your test environment is ready to go.
Skip above steps if you already have WordPress Slack account and joined #core already.
Setting Up Your Test Environment:
Make sure you have a local development environment or testing site ready to run the latest WordPress 6.8 version.
(Please don’t test/update on any client site or any Production/Live Site)
Here are two methods to update to an RCRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge./BetaBetaA 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. version:
Using WP-CLIWP-CLIWP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/https://make.wordpress.org/cli/: Ensure WP-CLI is installed on your environment. Run the following command to update:
wp core update --version=6.8-beta1
To verify the update with:
wp core version
Using the WordPress Beta Tester PluginPluginA plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party:
Install and activate the WordPress Beta Tester plugin:
Go to Plugins > Add New, search for “WordPress Beta Tester,” install, and activate.
Configure the settings:
After activation, go to Tools > Beta Testing in your WordPress dashboard.
You’ll see options to select the type of updates you want:
Bleeding Edge – Updates to the latest development version.
Beta/RC Only – Updates only to Beta and RC versions.
For testing an upcoming release candidateRelease CandidateA beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge., choose Beta/RC Only.
Go to Dashboard > Updates and update to the RC version.
What to Test During a Release Party:
When testing a WordPress release candidate (RC), the goal is to catch any issues or inconsistencies that could impact the final release. Here’s a checklist of key areas to focus on during testing: General Testing Checklist
You can also test anything you would like to ensure and provide your feedback.
Where to Provide the Status of Your Testing:
Main Channel: Provide updates directly in the #core channel on the WordPress Slack.
Format for Updates: Use a brief format to keep your updates clear and easy to follow:
What You Tested: Mention the specific feature you tested like creating a page with a coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress.blockBlockBlock 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..
Results: Share whether the test passed or failed, along with any notable observations. Please look at the below scrshot for reference.
If test Passed: add
If any issues happen, add
Issue Details (if applicable): If you found a bug, provide a short description and any error messages, screenshots, or reproduction steps.
How to Update RC/Beta Via WP CLICLICommand Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress. – Demo Video
For a step-by-step video guide on updating the RC version through WP CLI, watch this demo:
How to Update RC/Beta Via Beta Tester Plugin – Demo Video
If you prefer using the Beta Tester plugin, here’s a video guide to walk you through the process:
Previous Release Parties
If you looking to see what happens in Release Party, please checkout recent RC-2 Release Party here
September 24: Test Chat Meeting Recap Notes: @lumiblog
October 1: Test Triage Facilitator : Volunteers Needed
October 8: Test Chat Meeting Facilitator: Volunteers Needed
October 8: Test Chat Meeting Recap Notes: Volunteers Needed
3. Call for Nomination for the Test team RepTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.
The call for Nomination for the Test team Rep is open for one more week. If you want to nominate yourself or anyone else, you can do so in the next one week here.
4. Announcements 📣
Next major releaseMajor ReleaseA 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.: 6.7
We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBetaA 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. 1 is scheduled for Tuesday, October 1. The Road Map post can be found here.
Next minor releaseMinor ReleaseA set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality.: 6.6.3
Following the recent WordPress 6.6.2 release, the next maintenance release (if needed) will be WordPress 6.6.3. There were no updates shared in the meeting.
Next GutenbergGutenbergThe 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/ release: 19.2
The next Gutenberg release will be 19.2, scheduled for September 11 (this release occurred after the meeting).
PDX + WCUS 2024: A Recap: WordCamp US (WCUS), North America’s largest WordPress event, hosted over 1,500 attendees from around the world at the Oregon Convention Center in Portland, from September 17 to 20.
@ankit-k-gupta mentioned that a Test Scrub is scheduled every alternate Tuesday in the #core-test channel. He added that if anyone is interested in speeding up progress on tickets related to the WordPress 6.7 release and wants to lead a test scrub, support and assistance would be provided.
August 13: Test Chat Meeting Recap Notes: @lumiblog
August 20: Test Triage Facilitator : Volunteer Needed
August 27: Test Chat Meeting Facilitator: Volunteer Needed
August 27: Test Chat Meeting Recap Notes: Volunteer Needed
3. Announcements 📣
Release related update:
We are currently in the WordPress 6.7 release cycle. WordPress 6.7 BetaBetaA 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. 1 is scheduled for Tuesday, October 1.
The next maintenance release will be 6.6.2 and will likely be released at the end of the month, likely August 26 with RC1 the week before.
GutenbergGutenbergThe 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/ 19.0 is scheduled for August 14. RC1 was released on August 7.
Call for Nomination to select next term Test team repTeam RepA Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. who will serve for the next 12 months. If you know someone who can take this responsibility, please either comment on this post or reach out to @ankit-k-gupta or @webtechpooja.
4. Test Team Updates
Week in Test Post: Wondering where you can contribute and learn? The Test Team’s got you covered.
We are currently in the WordPress 6.6 release cycle. WordPress 6.6 Beta 2 was released on Tuesday, June 11. BetaBetaA 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. 3 will be released today at 16:00 UTC in #coreslackSlackSlack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel.
GutenbergGutenbergThe 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/ 18.6 is scheduled for June 19 and will include these issues. This version will NOT be included in the WordPress 6.6 release.
@boniu91 and @martinkrcho will be our Test Table leads. @krupajnanda and @ankit-k-gupta will be online leads. A post containing all the information about what and how contributors can help at the WCEU contributor table will be published soon.
@nhrrob mentioned there is a bug scrub happening today for WordPress 6.6 in the #core channel at 14:00 UTC on 21 May 2024. He encouraged beginners to join as it’s a good opportunity to learn about how tickets move forward and what keywords mean.
@webtechpooja then said they are thinking of starting a test bug scrub for upcoming 6.6 version tracTracTrac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets in the #core-test channel, asking if anyone is interested.
@oglekler expressed interest, saying it would be great with the betaBetaA 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. 1 release in 2 weeks and some promising enhancements that need testing, stating “No tests – no go”.
@pbearne shared a trac link with a list of tests waiting to be committed that could be looked at.
@oglekler shared another trac link as a priority for the 2 weeks before beta 1.
@webtechpooja asked if anyone had day/time preferences for scheduling a bug scrub meeting. She also stated focus will be on as many tickets as possible with everyone’s support.
We are currently in the WordPress 6.6 release cycle. The deadline for leaving feedback on this Planning Proposal post has ended, and we expect a release squad to be announced soon. Please leave a comment if you have any updates to share about this.
Week in Test Post: Wondering where you can contribute and learn? The Test Team’s got you covered. Check out this post and pick any issue mentioned in it.
There are currently 15 open tickets in the 6.5.3 release milestone. More information about this release is in this post, including the bug scrub schedule and how you can get involved.
GutenbergGutenbergThe 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/ 18.2 is scheduled for April 24 and will include these issues.
We are in the last lap for the test handbook completion!
