Team Chat Agenda: 16 July 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 16 July 2025 at 16:00 UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test

Team Chat Agenda: 02 July 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 02 July 2025 at 16:00 UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test

Test Chat Summary: 18th June 2025

On Wednesday, June 18, 2025 at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@krupajnanda, @azharderaiya, @sirlouen, @dvpatel, @lumiblog, @narenin, @muddassirnasim, @oglekler, @ravigadhiyawp,  and @dilip2615.

2. Looking for Volunteers

  • July 2: Test Chat Meeting Facilitator: Volunteer Needed 
  • July 2: Test Chat Meeting Recap Notes: Volunteer Needed

3. Announcements 📣

4. Test Team Updates

5. Questions/Blocker

@sirlouen noted that most people in the #core team appeared to be completely unaware of the Test team’s work. He pointed out that even though @oglekler had been running test tables for a long time, this contribution was not widely known.

@krupajnanda acknowledged the lack of awareness and clarified that this was one of the reasons she had raised several points during earlier discussions. However, she mentioned that due to time constraints, she had not received many answers.

@oglekler emphasised the need for a structured plan outlining the team’s activities and goals. She suggested we also needed a proper content plan and proposed checking with the Core Dev Blog team to determine what kind of testing-related content could be shared there. She highlighted that once such content was published, the team could request amplification for a broader reach.

@krupajnanda proposed creating a “Month in Test” summary, similar to our existing weekly updates but offering a higher-level overview. She also suggested:

  • Reporting on the number of tickets resolved,
  • Tracking the onboarding of new contributors,
  • Hosting monthly video meetings (e.g., on Zoom or Google Meet),
  • Documenting updates,
  • And continuing patch testing work, which SirLouen had already been involved in.

@sirlouen shared that the current testing activities during release parties often involved repetitive tasks that did not effectively uncover issues in new features. He stated that contributors often performed the same basic actions, which could easily be covered by automated E2E (End-to-End) tests. He added that resources could be used more wisely by focusing on deeper feature-specific testing.

He proposed that:

  • Ideal test cases could be documented in developer notes before release parties.
  • 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. Testing 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 could be enhanced to provide contextual testing instructions.
  • The plugin could be improved to engage testers more effectively, taking inspiration from Apple TestFlight.

@oglekler agreed that they needed automation for routine tasks, but stressed that human testers brought creativity and unpredictability that machines could not replicate. She felt the release parties served a dual purpose; verifying package integrity and fostering community spirit, and should not be discarded.

@krupajnanda added that documentation already existed (such as Help Test Docs), which outlined testing steps. However, she agreed that testers should go beyond ticking off checklists and explore newly introduced features to ensure functionality.

@sirlouen clarified that his intention was not to eliminate release parties but to make them more effective by focusing efforts on meaningful testing. He suggested creating a bullet list of tasks typically performed during release parties to help define what could be automated and what required human input.

@oglekler remarked that while most testers were simply updating via plugins, some were doing more extensive work, like testing version upgrades. She acknowledged that parties still had value but agreed that more targeted testing should be encouraged.

@krupajnanda proposed shifting focus from triage to testing 6.8.2 tickets starting next week. @oglekler responded that she would review the tickets, or possibly @sirlouen would do so first. 

@sirlouen added that most 6.8.2 tickets had likely already been tested, as they had been merged into trunk earlier. He said he would still monitor bug scrubs for any relevant tickets.

@krupajnanda concluded that they would assess whether any tickets required special attention; if not, they would continue with triage as usual.

6. Call for Testers/Visibility

7. Open Floor

There was no issue to discuss. 

8. Next Meeting 🗓

The next meeting will be on Wednesday, July 2, 2025 at 07:00 PM GMT+3, held on #core-test!

#meeting-notes

Thank you, @krupajnanda, for the peer review of 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.

#test-team

Team Chat Agenda: 18th June 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 18 June 2025 at 16:00 UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

  • Attendance
  • Note-taker and facilitator selection for the next meeting
    • This week’s facilitator is – @krupajnanda
    • This week’s note-taker is – Looking for a volunteer
  • Announcements
  • Test Team Announcements
  • Questions/Blockers
  • Call for testers/visibility:
  • Open Floor
  • Got a topic? Add in comments below, or bring it up live during the chat.

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test

Test Chat Summary: 21st May 2025

On Wednesday, May 21, 2025 at 12:00 AM GMT+8, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance


@krupajnanda @ravigadhiyawp @sirlouen @mosescursor @kausaralm @oglekler @pooja1210 @pavanpatil1 @iamshashank @muddassirnasim (async) @nikunj8866 (async), @lumiblog (async)

2. Volunteer

This week’s Note-taker and facilitator:


For the next bi-weekly chat –

3. Announcements 📣

  • Test team table lead for WCEU 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/.
  • A Month in Core – April 2025 is out.
  • Performance Chat Summary: 20 May 2025
  • The next 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. things are in progress and can be found here.
  • WCEU is around the corner. Please check out the schedule.
  • Gutenberg 20.8 is now available
  • 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/ 20.9 is scheduled for release on Wednesday, May 28, 2025.
  • Test team table lead for WCEU Contributor day @OGlekler will leading the Table for test team at WCEU. @Puja and  @SirLouen will be our online leads. We will soon publish a post mentioning all the information about what and how contributors can help us at WCEU contributor table.

4. Test Team Updates

5. Focal Group Updates

  • No updates.

6. Questions/Blockers

  • No Questions/Blockers were reported in this meeting

7. Call for Testers/Visibility

  • #core-editor team has shared this issues that needs testing. Please feel free to pick and contribute to any tickets and make sure to update the same in the #core-editor for the better visibility.

8. Open Floor

The conversation focused on improving the testing workflow and coordination during Contributor Days, especially regarding ticket handling and visibility of test efforts.

  • @sirlouen raised concerns about the difficulty of enforcing test tag management purely through control, suggesting that clear contributor instructions might be more effective.
  • @krupajnanda supported the idea that contributors should ensure tickets with sufficient test reports no longer carry the “needs-testing” keyword and encouraged proactive keyword checks before picking tickets.
  • @oglekler proposed better planning for future Contributors Day, highlighting interesting or challenging tickets to attract attention.
  • The team agreed on the need for more strategic planning and gradual improvements. @krupajnanda offered to draft a Contributor Day post, incorporating curated tickets with specific keywords, to guide contributors more effectively.
  • The idea of showcasing handpicked tickets was welcomed to engage contributors and highlight meaningful work..

9. Next Meeting 🗓

The next meeting will be on Thursday, June 05, 2025, at 12:00 AM GMT+8 , held on #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!Thank you @krupajnanda, for the peer review and for helping me write this post.

#core-test

Team Chat Agenda: 21th May 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 21 May 2025 at 16:00 UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

  • Attendance
  • This week’s
  • Looking for Note-taker and facilitator for the next meeting.
  • Announcements
  • Test Team Announcements
  • Focal Group Updates
    • No Updates
  • Questions/Blockers
  • Call for testers/visibility:
    • #core-editor team has shared this issues those needs testing. Please feel free to pick and contribute to any tickets and make sure to update the same in the #core-editor for the better visibility.
  • Open Floor
  • Got a topic? Add in comments below, or bring it up live during the chat.

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test

Test Chat Summary: May 07, 2025

On Wednesday, May 07, 2025 at 12:00 AM GMT+8, <test-chat> started in #core-test facilitated by @pavanpatil1. The agenda can be found here.

1. Attendance

@krupajnanda @muddassirnasim @pavanpatil1 @oglekler @sirlouen @SJ @kausaralm @lumiblog(asnyc) @narenin(asnyc) @puja

2. Volunteer

This week’s Note-taker and facilitator:

3. Announcements

4. Test Team Updates

5. Focal Group Updates

  • #core-editor team has shared this for the issues that needs testing. Please feel free to pick and contribute to any tickets and make sure to update the same in the #core-editor for the better visibility.
  • @sirlouen shared an update to the team that the new keyword has already been updated. Reports containing the old keyword will not be automatically updated and will need to be revised manually. He also mentioned that if any old keywords will be encountered then he will handle that part.
  • SirLouen requested @OGlekler to remove the -needs-testing-info keyword from the weekly reports.
  • The new list of keywords to use is: needs-testing has-patch -dev-feedback -2nd-opinion -close -needs-refresh -needs-design -needs-design-feedback

6. Questions/Blockers

@sirlouen raised a concern that many test reports genuinely needing attention are being overlooked, while others are already tested number of times but are still being retested which indeed does not add any value. To address this, he proposed manually curating a list of reports that actually need testing and will share clear, straightforward testing instructions to help non-technical testers contribute effectively.

In response, @krupajnanda thanked @sirlouen for volunteering to curate the list and requested that the list be posted in the channel once ready, so it can be pinned and easily accessed by others. (The list has already been pinned)

7. Call for Testers/Visibility

8. Open Floor Discussion

In a recent discussion, @sirlouen proposed a new initiative to host public Patch Test Scrub sessions dedicated to testing patches. Participants will be able to:

  • Join a scheduled session and test patches live alongside others.
  • Ask questions and get real-time guidance especially for more complex patches.
  • Learn from practical examples pulled from SirLouen’s Curated Testing List.

The very first Patch Test Scrub is scheduled for Monday, May 12th at 3PM GMT (5PM CEST / 8:30PM IST) and will be facilitated by @sirlouen. Future scrubs may adapt based on feedback and participation that we will receive.

9. Next Meeting

Wednesday, 14 May 2025 at 21:30 GMT+5:30:  <test-triage> in #core-test.

Wednesday, 21 May 2025 at 21:30 GMT+5:30:  <test-chat> in #core-test.

#core-test

Team Chat Agenda: 7th May 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 07 May 2025 at 16:00 UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

  • Attendance
  • Note-taker and facilitator selection for the next meeting
    • This week’s facilitator is – @muddassirnasim
    • This week’s note-taker is – Looking for a volunteer
  • Announcements
  • Test Team Announcements
  • Focal Group Updates
    • We are waiting for updates regarding the newly proposed keyword from #core team. A detail about the same can be found here under Discussion section.
  • Questions/Blockers
  • Call for testers/visibility:
  • Open Floor
  • Got a topic? Add in comments below, or bring it up live during the chat.

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test

Test Chat Summary: 10th April 2025

On Thursday, April 10, 2025 at 12:00 AM GMT+8, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@muddassirnasim @sirlouen @krupajnanda @oglekler @ravigadhiyawp @pbearne @sumitbagthariya16 @mukesh27 @indirabiswas27 @pavanpatil1 @mkrndmane @pratiklondhe @narenin @mebo (async) @nikunj8866 (async) @vaibhavsweb (async)

2. Volunteer 

For the next bi-weekly chat –

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

  • We are in a 6.8 release cycle and only a week from our final release. WordPress 6.8 is going to be released on April 15, 2025
  • Check what to expect in WordPress 6.8 release: Roadmap to 6.8

6. Questions/Blockers

@Muddassir Nasim reported successful testing using 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. Tester 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, expressed interest in learning WP-CLIWP-CLI WP-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/, and showed a willingness to explore interactive testing through CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress..

  • @Krupa Nanda suggested testing via WP-CLI and directed Muddassir to @Makarand Mane for further guidance.
  • @Makarand Mane reaffirmed his availability to support WP-CLI testing and offered assistance proactively.
  • @Manuel Camargo sought clarification on the scope of Nasim’s interest, distinguishing between WP-CLI specific testing and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. testing.

@Olga Gleckler encouraged to test the site with real and data, if you have this opportunity. So, if you can test on a staging site close to what you have on production (not on production, of course). Becasue some things can only happen in certain circumstances and conditions.

7. Call for Testers/Visibility

8. Open Floor

@krupajnanda suggested @SirLouen to prepare a draft for the suggestion and feedbacks he added here and mentioned once thr post will be ready we can post it in the community for feedback. 

9. Next Meeting 🗓

The next meeting will be on Wednesday, April 23, 2025, at 12:00 AM GMT+8 , held on #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!

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

#meeting-notes 

#core-test

Team Chat Agenda: 9th April 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 09 April 2025 at 16:00 UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#core-test