Week in Test: June 17, 2024

Hello and welcome to another edition of  Week in Test the  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:  Calls for Testing  |  Weekly Testing Roundup  |  Profile Badge Awards  |  Read/Watch/Listen  |  Upcoming Meetings

Calls for Testing 📣

Calls for Testing  can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Weekly Testing Roundup 🤠

Weekly update:  Test Team Update: June 17

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  PHP PHP 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. http://php.net/manual/en/intro-whatis.php .  developer contributors who can (or are interested in learning how to) build  automated PHPUnit tests .
Why?   Automated tests  improve the software development feedback  loop Loop 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.6 tickets  need  PHPUnit tests  built to accompany their respective patches:

6.6 Related issues need testing

The following 6.6 tickets need testing those are having patches:

Profile Badge Awards 🎉

These folks contributed at WordCamp WordCamp 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 . Europe Contributor Day Contributor 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/ . : @ mai21 , @akinom500, @mathieulamiotwpmedia, @wilbertschaapmancom, @thabotswana, @thup90, @z1ang, @hugod, @JustTePi, @yahaly, @ stefke89 , @thabotswana, @martinkrcho, @hugod, @vrajadas

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.

Week in Test: June 10, 2024

Hello and welcome to another edition of  Week in Test the  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:  Calls for Testing  |  Weekly Testing Roundup  |  Profile Badge Awards  |  Read/Watch/Listen  |  Upcoming Meetings

Calls for Testing 📣

Calls for Testing  can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Weekly Testing Roundup 🤠

Weekly update:  Test Team Update: 10 June 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  PHP PHP 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. http://php.net/manual/en/intro-whatis.php .  developer contributors who can (or are interested in learning how to) build  automated PHPUnit tests .
Why?   Automated tests  improve the software development feedback  loop Loop 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.

6.6 Related issues need testing

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.

Week in Test: June 3, 2024

Hello and welcome to another edition of  Week in Test the  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:  Calls for Testing  |  Weekly Testing Roundup  |  Profile Badge Awards  |  Read/Watch/Listen  |  Upcoming Meetings

Calls for Testing 📣

Calls for Testing  can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Weekly Testing Roundup 🤠

Weekly update:  Test Team Update: 3 June 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  PHP PHP 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. http://php.net/manual/en/intro-whatis.php .  developer contributors who can (or are interested in learning how to) build  automated PHPUnit tests .
Why?   Automated tests  improve the software development feedback  loop Loop 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.6 tickets  need  PHPUnit tests  built to accompany their respective patches:

6.6 Related issues need testing

The following 6.6 tickets need testing those are having patches:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

  • Gutenberg Gutenberg 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/ eighteen point five RC Release Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. was released on May 31 and included  these issues .
  • WordPress 6.5.4 Release Candidate 1 (RC1) is available for testing, and final release is scheduled for June 5.
  • The scheduled date for  WordPress 6.6 Beta 1 is June 4 . From then on, we will focus on testing and fixing bugs discovered during  beta 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. Begin writing Dev Notes and the About page.
  • WordCamp Europe 2024: Mid-Year Update and Q&A with Matt Mullenweg

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.

Week in Test: May 27, 2024

Hello and welcome to another edition of  Week in Test the  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:  Calls for Testing  |  Weekly Testing Roundup  |  Profile Badge Awards  |  Read/Watch/Listen  |  Upcoming Meetings

Calls for Testing 📣

Calls for Testing  can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Weekly Testing Roundup 🤠

Weekly update:  Test Team Update: 27 May 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  PHP PHP 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. http://php.net/manual/en/intro-whatis.php .  developer contributors who can (or are interested in learning how to) build  automated PHPUnit tests .
Why?   Automated tests  improve the software development feedback  loop Loop 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.6 tickets  need  PHPUnit tests  built to accompany their respective patches:

6.6 Related issues need testing

The following 6.6 tickets need testing those are having patches:

Profile Badge Awards 🎉

@ marc4 , @ markoheijnen , @ rcreators

Read/Watch/Listen 🔗

  • WordPress 6.5.4: An upcoming maintenance release
    • 30 May 2024 –  Release Candidate Release Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.  made available and announced here on the make/ core Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.  site.
    • 5 June 2024 – Final release made available.
  • What’s new in Gutenberg 18.4 (22 May) Our next  major release Major 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.  is  WordPress 6.6 . See the  Roadmap Post  for details about what is planned. Also, see the  Bug Scrub post  for more details on when the 6.6 bug scrubs are happening.
  • What’s new in Gutenberg 18.4 (22 May)
  • @ ellatrix   recently announced  that the last  Gutenberg Gutenberg 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 to go into WP 6.6 will have an  RC Release Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.  next Friday, May 31.

Upcoming Meetings 🗓

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

June 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.

Week in Test: May 20, 2024

Hello and welcome to another edition of  Week in Test the  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:  Calls for Testing  |  Weekly Testing Roundup  |  Profile Badge Awards  |  Read/Watch/Listen  |  Upcoming Meetings

Calls for Testing 📣

Calls for Testing  can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Weekly Testing Roundup 🤠

Weekly update:  Test Team Update: 20 May

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  PHP PHP 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. http://php.net/manual/en/intro-whatis.php .  developer contributors who can (or are interested in learning how to) build  automated PHPUnit tests .
Why?   Automated tests  improve the software development feedback  loop Loop 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.6 tickets  need  PHPUnit tests  built to accompany their respective patches:

6.6 Related issues need testing

The following 6.6 tickets need testing those are having patches:

Profile Badge Awards 🎉

harshalkadu , harshalk , Hitendra Chopda , Ramon Ahnert , Sumit Bagthariya

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.

Week in Test: May 13, 2024

Hello and welcome to another edition of  Week in Test the  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:  Calls for Testing  |  Weekly Testing Roundup  |  Profile Badge Awards  |  Read/Watch/Listen  |  Upcoming Meetings

Calls for Testing 📣

Calls for Testing  can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Weekly Testing Roundup 🤠

Weekly update:  Test Team Update: 13 May 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  PHP PHP 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. http://php.net/manual/en/intro-whatis.php .  developer contributors who can (or are interested in learning how to) build  automated PHPUnit tests .
Why?   Automated tests  improve the software development feedback  loop Loop 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.6 tickets  need  PHPUnit tests  built to accompany their respective patches:

6.6 Related issues need testing

The following 6.6 tickets need testing those are having patches:

Profile Badge Awards 🎉

Badges awarded to: Sumit Bagthariya , Ramon Ahnert . Congratulations!

Read/Watch/Listen 🔗

  • The  WordPress 6.6 roadmap  has been published.
  • WordPress 6.5.3 was released  on Tuesday, May 7. This  minor release Minor 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.  features 12 bug fixes in  Core Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress.  and 9 bug fixes for the  block Block 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.
  • Gutenberg 18.3  was released on Wednesday, May 8. The release highlights include a full page client-side navigation experiment, negative values for margin controls, and adding a publish flow Flow Flow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone.  Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it.
    Flow is the actual user experience, in many ways. If you like, you can think of flow as a really comprehensive set of user stories. When you think about user flow, you’re thinking about exactly how a user will perform the tasks allowed by your product. Flow and Context
    to the editor.
  • We are currently in the  WordPress 6.6 release cycle  and 4 weeks away from  Beta 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.  1.
  • Core Editor Improvement: Upgrade your designs

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.

Week in Test: May 6, 2024

Hello and welcome to another edition of  Week in Test the  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:  Calls for Testing  |  Weekly Testing Roundup  |  Profile Badge Awards  |  Read/Watch/Listen  |  Upcoming Meetings

Calls for Testing 📣

Calls for Testing  can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

  • Gutenberg Gutenberg 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/ 18.3 is scheduled for May 8 and will include  these issues .

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  PHP PHP 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. http://php.net/manual/en/intro-whatis.php .  developer contributors who can (or are interested in learning how to) build  automated PHPUnit tests .
Why?   Automated tests  improve the software development feedback  loop Loop 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.6 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.

May 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.

Week in Test: April 29, 2024

Hello and welcome to another edition of  Week in Test the  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:  Calls for Testing  |  Weekly Testing Roundup  |  Profile Badge Awards  |  Read/Watch/Listen  |  Upcoming Meetings

Calls for Testing 📣

Calls for Testing  can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Weekly Testing Roundup 🤠

Weekly update:  Test Team Update: 29 April 2024

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

Did you know that contributions to 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  PHP PHP 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. http://php.net/manual/en/intro-whatis.php .  developer contributors who can (or are interested in learning how to) build  automated PHPUnit tests .
Why?   Automated tests  improve the software development feedback  loop Loop 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.6 tickets  need  PHPUnit tests  built to accompany their respective patches:

6.5.3 Related issues need testing

The following 6.5.3 tickets need testing those are having patches:

Profile Badge Awards 🎉

Earn Your Test Team Badges – A  new handbook page  detailing the process for acquiring Test Team Profile Badges.  

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

May 2024 Schedule:

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

Week in Test: April 22, 2024

Hello and welcome to another edition of  Week in Test the  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:  Calls for Testing  |  Weekly Testing Roundup  |  Profile Badge Awards  |  Read/Watch/Listen  |  Upcoming Meetings

Calls for Testing 📣

Calls for Testing  can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

  • There are currently 15 open tickets in  the 6.5.3 release milestone . There is more information about this release  in this post , including the bug scrub schedule and how you can get involved.
  • Gutenberg Gutenberg 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/ 18.2 is scheduled for April 24 and will include  these issues .

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 to 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  PHP PHP 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. http://php.net/manual/en/intro-whatis.php .  developer contributors who can (or are interested in learning how to) build  automated PHPUnit tests .
Why?   Automated tests  improve the software development feedback  loop Loop 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.6 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.

Week in Test: April 15, 2024

Hello and welcome to another edition of  Week in Test the  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:  Calls for Testing  |  Weekly Testing Roundup  |  Profile Badge Awards  |  Read/Watch/Listen  |  Upcoming Meetings

Calls for Testing 📣

Calls for Testing  can originate from any team, from themes to mobile apps to feature plugins. The following posts highlight features and releases that need special attention:

Weekly Testing Roundup 🤠

Weekly update:  Test Team Update: 15 April 2024

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

Did you know that contributions to 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  PHP PHP 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. http://php.net/manual/en/intro-whatis.php .  developer contributors who can (or are interested in learning how to) build  automated PHPUnit tests .
Why?   Automated tests  improve the software development feedback  loop Loop 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.6 tickets  need  PHPUnit tests  built to accompany their respective patches:

6.6 Related issues need testing

The following 6.6 tickets need testing those have patches:

Profile Badge Awards 🎉

No Badges were awarded this week.

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

April 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.