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.
On 29 August 2023 at 16:00 UTC, <test-chat> started in #core-test.
<release-party>. Raise your hand, or be kind and share this post with folks you think can help out. Thanks!There is an open PR to add a Test Team Rep page to the handbook. Reviews are welcome, which can be comments/reviews on the PR, or a 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.” in #core-test if something needs more discussion.
[This discussion started here.]
It has been proposed that the #fse-outreach-experiment begin the process of spinning down its user testing aspect (i.e. the program’s calls for testing) by the time WordPress 6.4 ships. In place of testing efforts, focus would shift to emphasize wider adoption of the Site Editor through hallway hangouts, dev documentation efforts, and other adoption-focused initiatives on the path toward wrapping up Phase 2 of the WordPress Project Roadmap.
Because the FSE Outreach Program has considerable overlap with Test Team efforts, program leadership has requested input from Test Team contributors with questions or concerns around the proposed shift. This follows other shared feedback from current program participants.
It was stressed that changes in the outreach program be handled carefully and slowly, and to capture opportunities for feedback. The next step is to compile initial feedback and thoughts around this change to share in a Make/Test post for wider input.
Current contributors in the #fse-outreach-experiment have expressed a desire to continue testing in a format adapted from or similar to the outreach program. Structured ad hoc calls for testing from within the Test Team are similar, and would provide an opportunity for continued contribution through testing. [Ed. note: the Test Team should also consider adopting things that worked for FSE CfTs to improve the experience for all testers.]
A possible source for CfT topics could be pulled from roadmap posts (for example), or otherwise collected in an ideas backlog (for example). Some pertinent links for CfTs can be found at:
Work is ongoing for documenting processes in the Test Team. The Handbook project can be found at https://github.com/wordpress/test-handbook.
[This discussion started here.]
The Call for Nominations for the next Test Team Reps is underway. Test Team members’ help is needed to nominate or volunteer for this role, to help represent the team to the wider project.
If you have a nominee in mind, or questions about the role, please comment on the post, ask in #core-test, or reach out directly to @ironprogrammer in 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/..
@ironprogrammer stepped forward with an offer to help mentor volunteers for this role. It was also noted that serving as a rep offers an excellent opportunity to gain a broader perspective of how Test Team interacts with other teams, and that while it isn’t a “lead” role, there are some leadership-focused skills that reps develop in the process.
Please submit nominations by Thursday, August 31 Friday, September 22, end of day (UTC).
The next scheduled meeting is on 5 September 2023 at 16:00 UTC for <test-triage> in #core-test.
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!
Props @annezazu for peer review of this post.
On 15 August 2023 at 16:00 UTC, <test-chat> started in #core-test.
And we received one participant-submitted announcement:
Volunteers were asked to step forward to help facilitate the Test table, both in person and remotely 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/.. @ironprogrammer volunteered to help lead in person at the event, but at the time of this writing there was no clear lead for coordinating contributors online in Slack. Contributors wishing to help are asked to comment below or raise their hand in Slack.
The remote session for Contributor Day is scheduled to begin at 2023-08-24 10:00 EDT in the #contributor-day channel. For more details, see the Test Team at WCUS 2023 post.
It was shared that the nomination process for the next Test Team Reps would begin soon, and team members were encouraged to help identify and nominate individuals who might be a good fit for the role (even themselves). [Ed. note: the 2023-24 call for nominations has been published.]
The next scheduled meeting is on 22 August 2023 at 16:00 UTC for <test-triage> in #core-test.
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!
Props @boniu91 for peer review of this post.
On 23 May 2023 at 16:00 UTC, <test-chat> started in #core-test.
And last, but not least:
@oglekler also invited everyone to take part in the Day 15: #WP20 From Blogs to Blocks campaign.
wp-now Package@ironprogrammer drew attention to the recent release of wp-now (npm package), part of the WordPress Playground project. He noted that wp-now works with Node.js, and could be a possible replacement for wp-env. He gave an example of having navigated to a pluginPlugin A 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 source directory and running wp-now start, which quickly launched a new WordPress site to test the plugin.
@ironprogrammer mentioned that the utility could be a fast way for contributors to get set up for testing or development, and referred to WCEU as a possible testing ground for test contributors to try it out.
@oglekler provided a link to a MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. event that featured Playground, occurring shortly after Test Chat.
@ironprogrammer then shared his plans to draft wp-now setup instructions to propose for addition to the Test Handbook, and asked the team to try out the utility and report any blockers or challenges they encounter.
@boniu91 asked if PRs and patches could be applied to sites running on wp-now. @ironprogrammer confirmed having tested with plugin repos, but that testing with the wordpress-develop repo would be important before recommending it for broader Test Team use.
The next scheduled meeting is on 30 May 2023 at 16:00 UTC for <test-triage> in #core-test.
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!
Props @costdev for peer review of this post.
On 9 May 2023 at 16:00 UTC, <test-chat> started in #core-test.
And a reminder:
@ironprogrammer highlighted that the PR to prerelease Playwright test utils — aka @wordpress/e2e-test-utils-playwright — has been merged, and is slated for release with 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/ 15.8 🎉. He noted that this facilitates inclusion of the package in other test suites, and expressed hope that it would eventually contribute toward improved E2E coverage in WordPress.
@oglekler wondered how well Playwright worked in WP admin, outside of the editor context. She referred to reports of Quick Edit rows disappearing after an update, and whether an E2E test could help identify this.
@ironprogrammer clarified that the release of the @wordpress/e2e-test-utils-playwright package was in response to several requests from community members who wished to use it, and encouraged continued exploration regarding previous discussions about Cypress.
The next scheduled meeting is on 16 May 2023 at 16:00 UTC for <test-triage> in #core-test.
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!
Props @juhise for peer review of this post.
On 25 April 2023 at 16:00 UTC , <test-chat> started in #core-test.
There was no agenda preceding the chat.
@ironprogrammer asked @oglekler if there was an update from the last chat’s E2E discussion, and they would follow-up later.
@ironprogrammer invited/reminded the team to consider submitting topics and/or applying to the 2023 WordPress Community Summit, emphasizing that ideas and input from underrepresented community members is especially important to summit discussions.
The next scheduled meeting is on 2 May 2023 at 16:00 UTC for <test-triage> in #core-test.
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!
Props to @costdev for peer review of this post.
On April 11, 2023 at 16:00 UTC , <test-chat> started on #core-test.
There was no agenda preceding the chat.
@ironprogrammer re-introduced this section as pertaining to Test Team discussions from 2021. Because contributorship has changed a lot since then, he asked that contributors interested in representing a particular focal group reach out to @boniu91 or @ironprogrammer (himself). He also noted that the team can adjust the focal groups to align with current needs, particularly if it would help inspire greater collaboration.
@oglekler noted their positive experience with Cypress, an open-source testing tool which uses Mocha and jQuery, and can be run headless. @ironprogrammer asked if it was compatible with the current WordPress E2E standard, Playwright, and suggested that discussion with other E2E contributors be held to discuss further.
@ironprogrammer suggested that a follow-up Make/Test post be considered to gauge interest on possible focal group rep interest, particularly for E2E.
@ironprogrammer gave a brief update on the Test Handbook, noting that a new Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. page was under final review. The page will provide new Test Team contributors a good place to start at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. events. He encouraged contributors to share the page at future WordCamp Contributor Day events, and to raise suggestions for improvement in the #core-test channel, or to create a PR in the handbook’s official GitHub repo.
The next scheduled meeting is on April 18, 2023 at 16:00 UTC for <test-triage> in #core-test.
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!
Props to @costdev for peer review of this post.
On March 28, 2023 at 16:00 UTC , <test-chat> started on #core-test.
There was no agenda preceding the chat.
Are you interested in hosting a <test-scrub>? The Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.
@ironprogrammer pointed out that the release process helps ensure that issues like the regression noted above can be identified and resolved prior to general release.
And a shout out was given to @juhise for running last week’s Test Team Triage, as well as thanks to everyone else who attended! 🎉
@afragen requested UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. testing for the Plugin Dependencies feature plugin, noting that @azaozz was looking for “newish” user feedback for the plugin dependency activation workflow. The instructions provided by Andy included two steps: installing the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins., and then installing a separate plugin with a dependency.
@costdev and @afragen explained that providing only basic instructions might better measure how easy or difficult the workflow is to users in discovering the process organically — i.e. how to successfully install the dependent plugin without outside guidance.
@costdev outlined the feedback desired from testers, and @ironprogrammer asked where the feedback should be provided. Additional discussion along with @afragen lead to the decision to create a new call for testing post. [Editor’s Note: The CFT for the above has been posted to Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..]
The next scheduled meeting is on April 4, 2023 at 16:00 UTC for <test-triage> in #core-test.
On 14 March 2023 at 16:00 UTC , <test-chat> started on #core-test.
There was no agenda preceding the chat.
Are you interested in hosting a <test-scrub>? The Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.
@afragen called for awareness of the Rollback Update Failure and Plugin Dependencies plugins, so that they might land in 6.3-alpha. @ironprogrammer noted that both features could improve the user experience in WordPress.
@afragen also asked for testing of #53323: Place Hello Dolly in containing folder, so that this plugin follows documented best practices.
@costdev mentioned that improved release testing has been discussed in #core, and asked if anyone had thoughts on how the number of testers might be increased during the Alpha/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./RC phases. @ironprogrammer noted that this has been suggested as a 2023 WordPress Community Summit topic, but that short term options are needed.
@costdev asserted that collaboration with MarComms (#marketing) would be key to finding ways to pull in more contributors for testing. He asked where we might extend reach/awareness, and what motivates users to become testers.
@afragen suggested that managed hosting providers, such as WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/, might facilitate RC testing by working with opt-in site owners. @costdev agreed that this would help environment testing, but that there is a lack of feature-specific testing and reporting. He asked what tools might be offered to make this easier.
@costdev’s question spawned a long thread discussing ideas to simplify issue reporting for pre-release builds, the outcome of which is described below.
The next scheduled meeting is on 21 March 2023 at 16:00 UTC for <test-triage> in #core-test.
Thank you props to @costdev for review of this post.
Olá! We’d like to express our gratitude to everyone who stopped by the Test Team (or CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.:Test) table at this year’s WCEU Contributor Day 🙇. Your ideas, perspectives, and open discussions help foster initiatives critical to testing WordPress. Thank you to everyone who participated!
Participants at the event covered the following topics (some of which were also referred to #core-test in Slack):
@todo Investigate whether Trac supports pre-populated template options, for initial post and/or comments.wp-env, VVV, Laravel Valet, Local, etc). There shouldn’t be a preference for “the best” or “one way” to run/test WordPress, since it should reflect the real-world variation across the WordPress community.week-in-test categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. to Week in Test posts, for easier filtering of “where to start” in testing (currently grouped under the more generic summary category).<test-chat> and <test-triage> be shifted from 17:00 to 16:00 UTC to allow broader participation from European contributors. Please share your vote or thoughts here.Props to @boniu91 for peer review of this post.
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.
