DocsWP — WordPress Help

Test Chat Summary: March 12, 2025

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

1. Attendance

@Krupajnanda, @oglekler, @sirlouen, @vgnavada, @kausaralm, @shiponkarmakar, @pavanpatil1, @narenin, @nikunj8866, @pmbaldha, @mukesh27

2. Looking for Volunteers

  • @vgnavada volunteered to take notes on this meeting.

3. Announcements

4. Test Team Updates

5. Focal Group Updates

  • We are in the 6.8 release cycle and only 2 weeks from our first RC 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

7. Call for testers/visibility

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:

  1. 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.
  2. 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.

9. Next Meeting 

10. Closing Remarks

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!

#core-test, #summaries