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 Beta 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 Plugin 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
if you are going to be doing the testing report. 
You must be logged in to post a comment.