Highlighted Posts

Categorize a post as Highlight to add it to this section.

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

X-post: Test Team Update: 2 December 2024

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

X-post: Test Team Update: 25 November 2024

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

Week in Test: November 25, 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:

  • No tickets found

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:

🚨 There is the change in weekly meeting time. Now, all the meetings will happen at 16:00 UTC on every Wednesday.

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: 19th November 2024

On Tuesday, November 19, 2024, at 02:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@jagirbahesh, @krupajnanda, @lumiblog, @zeelthakkar, @dhruvang21, @mayanktripathi32, @sumitbagthariya16, @parthvataliya, @sukhendu2002, @yogeshbhutkar, @sainathpoojary, @abcd95, @ankitkumarshah, @hage, @narenin, @sarthaknagoshe2002, and @noruzzaman

2. Looking for Volunteer

  • November 26: Test Triage Facilitator: Volunteers Needed
  • December 3: Test Chat Meeting Facilitator: Volunteers Needed 
  • December 3: Test Chat Meeting Recap Notes: Volunteers Needed

3. Announcements 📣

  • WordPress 6.7, Rollins, is out!
  • Keep an eye on 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. for the 6.7.X series
  • Please join the WordPress Community Team as a Supporter of Cohort 2024-25
  • Successfully completed the six weeks of the mentorship program, and many folks have graduated! Congratulations to all the mentees!
  • The Playground team added browser support for cURL, making it easier for WordPress 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 developers to showcase their plugins directly in Playground and use them in runPHP blueprint steps.
  • Experimental inline comments: 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/ 19.6, inline commenting is now available as an experiment. You can follow the ongoing development of this feature in the tracking issue or review the previous work in the original pull request. Testing and feedback are needed.
  • Introducing the WordPress.org Experiments plugin: A new plugin called WordPress.org Experiments allows contributors to test experimental features before they’re integrated into WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

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

There was nothing from the members. 

8. Next Meeting 🗓

The next meeting will be on Tuesday, December 3, 2024, at 11.00 UTC, 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!

#meeting-notes, #summary

Team Chat Agenda: 19th November 2024

Here is the agenda for the upcoming Test Team Chat scheduled for 19 November 2024 at 11: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
  • Announcements
    • WordPress 6.7, Rollins, is out!
    • Keep an eye on 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. for 6.7.X series
    • Please join the WordPress Community Team as a Supporter of Cohort 2024-25
    • Successfully completion of the six weeks of mentorship program, and many folks had graduated! Congratulation to all the mentees!🎉
    • The Playground team added browser support for cURL, making it easier for WordPress 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 developers to showcase their plugins directly in Playground and use them in runPHP blueprint steps.
    • Experimental inline comments: 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/ 19.6, inline commenting is now available as an experiment. You can follow the ongoing development of this feature in the tracking issue or review the previous work in the original pull request. Testing and feedback are needed.
    • Introducing the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ Experiments plugin: A new plugin called WordPress.org Experiments allows contributors to test experimental features before they’re integrated into WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • Test Team Announcements
  • Focal Group Updates
    • No updates to share
  • 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

X-post: Test Team Update: 18 November 2024

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

X-post: Test Team Update: 18 November 2024

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