Test Chat Summary: December 18, 2024

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

1. Attendance

@krupajnanda, @n8finch, @mayanktripathi32, @lumiblog, @mobarak, @hage, @oglekler, @shanemuir, @narenin, @sirlouen, @patrickl, and Narendra Sishodiya

2. Looking for Volunteers

3. Announcements 📣

  • WordCamp Asia 2025 Contributor Day: The Test Team is seeking leads for the Contributor Day table at WordCamp Asia, which will take place on February 20, 2025. Please express interest in the thread if you plan to attend WCAsia in person or can assist remotely.
  • WordPress 6.7.2:  No release date is currently planned for WordPress 6.7.2. Please review the next minor releaseMinor Release A 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. milestone for 6.7.2 and check the associated tickets for ways to contribute.
  • WordPress 6.8 Release Cycle:  The team is currently working on the WordPress 6.8 release cycle.
  • Proposals for Major Releases in 2025:  A proposal for 2025 has been drafted. Review the post for more details.
  • Write Books With the Block Editor:  We are currently discussing how to use the blockBlock Block 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. editor to write books.
  • State of the Word 2024: The State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. 2024 session focuses on Legacy, Innovation, and Community.

4. Test Team Updates

5. Focal Group Updates

No updates were reported during the Meeting.

6. Questions/Blockers

The members reported no blockers or questions.

7. 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. Improving Test Results Trustworthiness:
    • @OGlekler raised the need to enhance trust in test results, suggesting that test case coverage be included as proof in reports.
    • @krupajnanda agreed and emphasized the importance of detailing scenarios covered in testing fixes/PRs to reduce regression risks and improve clarity on the scope of fixes.
    • @OGlekler shared an example from a workplace discussion, noting the value of systematic reporting and documenting test cases.
  2. Forum for Brainstorming Ideas:
    • @SirLouen proposed having a persistent space, like a forum or blog post, to brainstorm and collect broader feedback on such topics.
    • The group agreed that creating a collaborative Google Doc to collect ideas and present the issue without initial bias could be effective.
  3. Next Steps:
    • @krupajnanda committed to sharing a collaborative Google Doc link for feedback collection.
    • The group agreed to publish a finalized document on the team blog and invite input from other teams and contributors.

Resources:

The open floor concluded with a call for participants to contribute their ideas, ensuring diverse perspectives are incorporated.

8. Next Meeting 🗓

9. 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 was encouraged to continue contributing and collaborating outside of scheduled meetings.

Highlights:

  • @krupajnanda thanked everyone for their participation and emphasized the community spirit of Test Team contributors.
  • @OGlekler extended gratitude to the team, wishing everyone a great end to the year and an inspiring start to 2025.

Takeaways

  • Keep engaging in discussions within the channel.
  • Use this time of year to reflect, recharge, and prepare for exciting contributions in the new year.
  • Remember to bring family and friends into the WordPress journey!

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, #meeting-notes, #summaries

Calling all WordPress test enthusiasts in Ahmedabad! 📢

Get ready to dive into the exciting world of WordPress at WordCamp Ahmedabad for a 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/.! 🎉

🗓️ When: 3rd January,2025

📍 Where: Auda Auditorium, Shela

This awesome event brings passionate folks like you together to collaborate, learn, and make a real difference in the WordPress project. Here’s a glimpse of what awaits you and how you can jump right in.

How can you be part of this contributor day? 

  • If you have any previous contributing experience with the test team and know how to contribute, there is an opportunity for you to become a Table Lead. The call for Table Lead is still open.
  • Are you new to testing? No worries! Our friendly Test Team will guide you every step of the way.
  • Expand our automated testing coverage! Your contribution will make WordPress even more stable and secure.
  • Improve testing documentation! Help us make the process crystal clear for everyone.
  • Triage issues and lend a helping hand! Your expertise will be invaluable to the team.

Contributor Day is more than just coding and testing!

Contributor Day isn’t just about work – it’s about building connections and having fun! You’ll get to meet other passionate WordPress users, exchange ideas, and celebrate each other’s achievements. The energy and enthusiasm will be contagious, and you’ll leave feeling inspired and part of a supportive community. 🚀

Get Prepared to Contribute!

To make the most of Contributor Day, here are a few things you can do beforehand:

Looking Ahead!

We’re incredibly excited to see the progress and innovation that will come out of this Contributor Day. Every contribution, big or small, makes a huge difference! A big thank you in advance to everyone who joins us in Ahmedabad and remotely. Together, we’re making WordPress better than ever.✨

Stay tuned for more updates! And don’t forget to join the #core-test and #contributor-day channels in Make WordPress Slack!

Kicking off 2025 with the first 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.! See you in Ahmedabad! 👋

Props to @webtechpooja for peer review.

+make.wordpress.org/test/

#contributor-day, #core-test, #wcahmedabad

Team Chat Agenda: 18th December 2024

Here is the agenda for the upcoming Test Team Chat scheduled for 18 December 2024 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

X-post: Test Team Update: 16 December 2024

X-post from +make.wordpress.org/updates: Test Team Update: 16 December 2024

Week in Test: December 16, 2024

Hello and welcome to another edition of Week in Testthe place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Jump to: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

Weekly Testing Roundup 🤠

Weekly update: Test Team Update

Here’s a roundup of active tickets that are ready for testing contributions.

Did you know that contributions with the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

Reproduction Testing 🔁

Who? Any contributor.
Why? It is helpful to show an issue exists for other users in order to move a ticket forward for patching.

The following new tickets are awaiting review, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:

Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

PHPUnit Tests 🛟

Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. for quality and backward compatibility.

The following 6.8 tickets need PHPUnit tests built to accompany their respective patches:

6.7 Related issues need testing

The following 6.7 tickets need testing those are having patches:

  • No tickets found

Profile Badge Awards 🎉

Profile badge is awarded to Md Abul Bashar and Parth Vatalitya

Read/Watch/Listen 🔗

  • The next 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/ release will be 19.9, scheduled for December 18. It will include the following issues.
  • State of the Word 2024 : This year, the event took place on December 16, 2024 Tokyo, Japan. You can watch it on official WordPress YouTube channel also.
  • You can also follow this archive for “State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/.” from previous years too.

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2024.

2024 Schedule:

Due to the upcoming Christmas and New Year holidays, we are canceling the following meetings: on December 25th <test-triage> and on January 1st <test-chat> .

2025 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

#core-test

X-post: Test Team Update: 9 December 2024

X-post from +make.wordpress.org/updates: Test Team Update: 9 December 2024

Week in Test: December 9, 2024

Hello and welcome to another edition of Week in Testthe place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Jump to: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

Weekly Testing Roundup 🤠

Weekly update: Test Team Update: 2 December 2024

Here’s a roundup of active tickets that are ready for testing contributions.

Did you know that contributions with the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

Reproduction Testing 🔁

Who? Any contributor.
Why? It is helpful to show an issue exists for other users in order to move a ticket forward for patching.

The following new tickets are awaiting review, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:

Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

PHPUnit Tests 🛟

Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. for quality and backward compatibility.

The following 6.8 tickets need PHPUnit tests built to accompany their respective patches:

6.7 Related issues need testing

The following 6.7.2 tickets need testing those are having patches:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2024.

2024 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

#core-test

Test Chat Summary: 4th December 2024

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

1. Attendance 

@krupajnanda, @noruzzaman, @sainathpoojary, @ankitkumarshah, @sarthaknagoshe2002, @oglekler, @mayanktripathi32, @shanemuir, @sirlouen, @narenin (async), @lumiblog (async), and @hage

2. Looking for Volunteer

  • December 11: Test Triage Facilitator: Volunteers Needed
  • December 18: Test Chat Meeting Facilitator: Volunteers Needed 
  • December 18: Test Chat Meeting Recap Notes: Volunteers Needed

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

The members reported no updates.

6. Questions/Blockers

No questions/blockers were reported by the members.

7. Open Floor

@sirlouen mentioned that he had been thinking about testing reports after following several conversations in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. He expressed curiosity about the extent to which developers appreciate such reports, noting that he had observed developers re-testing and commenting on information that was already clear in the reports.

@oglekler suggested that sometimes the reports might lack sufficient information and proposed that improvements could be made by ensuring all possible test cases are accounted for and explicitly checked.

@sirlouen wondered if they should inquire what information developers find useful or if the reports might be too convoluted, leading developers to disregard them.

@krupajnanda added that it would be important to observe if this pattern was specific to certain tickets owned by the same developer or spread across different developers. If so, improvements to the parameters shared in the reports would be necessary.

@sirlouen concluded by stating that he would monitor and log these occurrences over time to gather precise information, acknowledging that this behaviour might only apply to a few developers and that he wasn’t following all categories of reports.

8. Next Meeting 🗓

The next meeting will be on Wednesday, December 18, 2024, at 07:00 PM GMT+3, held on #core-test!

#meeting-notes

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!

#summaries

Team Chat Agenda: 4th December 2024

Here is the agenda for the upcoming Test Team Chat scheduled for 4 December 2024 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 volunteer
  • Looking for a volunteer to facilitate and note-taker for next meetings
  • Announcements
  • Test Team Announcements
  • Focal Group Updates
    • No Updates to share here
  • Questions/Blockers
  • 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

Week in Test: December 3, 2024

Hello and welcome to another edition of Week in Testthe place where contributors of any skill level can find opportunities to contribute to WordPress through testing. You can find the Test Team in #core-test.

Jump to: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings

Weekly Testing Roundup 🤠

Weekly update: Test Team Update: 2 December, 2024

Here’s a roundup of active tickets that are ready for testing contributions.

Did you know that contributions with the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.

Reproduction Testing 🔁

Who? Any contributor.
Why? It is helpful to show an issue exists for other users in order to move a ticket forward for patching.

The following new tickets are awaiting review, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:

Patch Testing 🩹

Who? All contributors (not just developers) who can set up a local testing environment.
Why? It is necessary to apply proposed patches and test per the testing instructions in order to validate that a patch fixes the issue.

The following tickets have been reviewed and a patch provided, and need testers to apply the patch and manually test, then provide feedback through a patch test report:

PHPUnit Tests 🛟

Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. for quality and backward compatibility.

The following tickets need PHPUnit tests built to accompany their respective patches:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings held for 2024.

2024 Schedule:

Interested in hosting a <test-scrub>? Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

#core-test