Highlighted Posts

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

Help test WordPress 6.5 Beta 1

It’s time for the next big release in the WordPress world! WordPress 6.5 is planned for March 26, 2024, and we need your help to make it the best it can be. New features and improvements make this release a game-changer as always. 

This is the second Call for Testing post for the 6.5 release after the early call that highlighted new Editor features. 

Table of Contents:

Why should you test the upcoming WordPress version

Are you a professional QA specialist, developer, business owner or blogger? You can easily test WordPress Betas, Release Candidates and the development version at any given moment to be sure that your site, theme and plugins are fully compatible with the upcoming version and there are no complications with server settings, certain data in the database or other things that can be almost unique for your site. This way you can be sure that when a new version is launched, you can easily update your site, or your theme/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 users will be happy when they update their sites. 

Do you find something that does not match up but you are not sure? Report it in the Forums (details below).

This is also a great way for you to contribute to WordPress and become a part of the worldwide open-source community improving the CMS you are using in your day-to-day business that benefits your business as well. 

Get ready

This is quite simple. You can test the latest development version, or a specific BetaBeta 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./RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. with the WordPress Beta Tester Plugin on any site you want, but please only test on a development siteDevelopment Site You can keep a copy of your live site in a separate environment. Maintaining a development site is a good practice that can let you make any changes and test them without affecting the live/production environment. and not on a production/live site. You can use any local environment and run WordPress locally or launch another site on your hosting. Some hosting companies provide a simple way to launch a staging site alongside your main site, so check what options you have. And please consider the security of your staging site by avoiding the use of simple passwords or leaving the installation process halfway through.

Test Environment installation

If you are a developer or a QA specialist and are planning to test patches, you can follow these instructions to set up a WordPress development version locally; or if you want to test just what is already in the release, use a Playground or install WordPress in your local environment and use the WordPress Beta Tester Plugin

For more detailed steps about the Beta Tester Plugin, follow this link for complete instructions.

With Playground, you can also easily test individual Core tickets.

What to test

Each release introduces a lot of new features, improvements and bug fixes. Most of them do not require any additional actions from you, but in some cases, something might need to be changed. This is why testing is a good practice as well as following along with the release to see if something can require actions from your side or provide you new opportunities.

If you missed the previous call for testing, you can start with Early Opportunities to Test WordPress 6.5.

To make your testing experience as smooth as possible and save your time, follow the instructions: 

General testing

  1. Update your theme and plugins to the latest versions.
  2. Switch to the Beta/RC/Night build you want to test.
  3. Check Site Health to see if there are already some issues that will be unrelated to the update.
  4. Check for Errors, Warnings and Notices
    • Turn on the debug log by adding settings to your wp-config.php. (Note that SCRIPT_DEBUG can change the behaviour of scripts, so it is recommended to test this constant both on and off.)
    • Run a spider against your site to process all the available pages.
    • Open the developer console in the browser.
    • Try to create a new post, add some content and save it, especially try to copy and paste content from another source, add comments, add media files of different types and do other usual actions in the admin. While doing it, pay attention to the information in the console to see if there are any issues.
      Note: Sometimes some issues are not visibly affecting any of the site functionality and sometimes it can be tricky to decipher where they are coming from. 
    • Check special functionality, go through the most important logic of your site: if you have an e-commerce store, place an order; perform a search; etc.
    • Open your site in different browsers and try the same things.
  5. Check the debug log to see if something is reported there.
    Note: Things that occur in the theme or a plugin need to be addressed to its developer. Additional information about your environment and site setting is in the Site Health information. Check information for any sensitive data before publishing it in any forum or other public space.
  6. Check Site Health to see if some issues were not present before.
    Note: depending on the message, the steps you should take can be quite different. For example, if you have a low 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. http://php.net/manual/en/intro-whatis.php. version (this issue should be present before testing the upcoming version) this can and should be changed on the hosting. So, for most of these issues, your hosting provider or a site developer will be the first person to go to.
  7. If errors appear in the log, check the paths to where these issues occurred, and contact the theme/plugin developer, or ask in the Forums (or your local native language Forum). But firstly check if this is already reported by someone else. In our case, multiple reports are not making things more important but only creating additional work for contributors who are triaging tickets. And read the sticky post first to find out how to work and communicate in the Forums.

If this looks complicated, just do what you can and take it easy. If you didn’t find anything, most likely everything is working for you just like it should.

Check the WordPress 6.5 Release Schedule to see which pre-release build can be tested now.

Advanced testing

Ready to get started to dive deeply into testing? Be creative and think out of the box. 

Tips:

  • Test across different browsers.
  • Test in different languages.
  • Compare features on different screen sizes, including tablets and mobile.
  • Use just your keyboard to navigate, or use a screen reader.
  • Test with both 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. and classic themes.
  • Try to make everything the wrong way.

Key Features to Test

There are a lot of new features mentioned in the 6.5 Beta 1 release post. Each feature needs to be properly tested in all possible ways, noticing nuances and details. Start with the Font library, it will be a lot of fun to explore and will be useful for you shortly. If you are a plugin developer or a plugin user who has issues with plugin dependencies from time to time, try Plugin dependencies to see how it is working and if this meets your expectations. And there are even more new options and enhancements in the Editor. Forget about testing and spend some time admiring the great work… Not really, test them while having fun.

New translation system

WordPress 6.5 changes how translations are being loaded, replacing the existing localization system with a more lightweight and much faster mechanism. This is mostly an invisible change which has been extensively tested before via the Performant Translations plugin. If you are using WordPress in a language other than English (US), you should verify whether translations are still loaded everywhere as expected. Especially if you are using any kind of multilingual/translation plugin. Make sure that all your translations are up-to-date on Dashboard -> Updates as well. More information about this new translation system will be published in a dedicated developer note soon.

Where to report feedback

If you find any issues but are not sure that is actually a bug or where should be reported, share them on the WordPress.org alpha/beta forums. If you are certain that you found a bug in WordPress Alpha/Beta/RC and don’t have an issue with something else, report it on Core Trac. And the Test Reports plugin will help you in creating detailed reports. Please search for an existing report first. 

For helpful reporting guidelines, refer to the Test Reports section of the Test Handbook. Also, see the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team guidelines for Reporting Bugs.

Please share feedback as soon as you can before the final release on March 26, 2024.

What else you can do

  • Share this post to advise other WordPress developers, DevOps, QA specialists and site owners to join efforts in testing.
  • Ask your local meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. organizers to make a meetup about testing, QA and release cycles. 
  • Subscribe to the Test Team blog to get further information and updates. You may also subscribe to the Core Team blog to stay in the 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. with Core updates, including the latest “Week in Core” posts.
  • Join our regular Test Team meetings in the #core-test Slack channel, where you can get real-time updates, get help with testing or discuss tricky cases. Participate in team meetings and test scrubs every week to engage in the testing community.
  • Do you have suggestions for how this post can be improved? Please leave a comment below.

A big thank you to @vipuljnext, @lumiblog, @swissspidy, @ironprogrammer, @ankit-k-gupta, @webtechpooja and @annezazu for contributing to this post.

Changelog

2024-02-15

  • Initial Post

#6-5

X-post: Test Team Update: 18 March 2024

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

Week in Test: March 18, 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: 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

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 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. 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 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 no tickets are available for 6.5 that need PHPUnit tests built to accompany their respective patches.

6.5 Related issues need testing

The following 6.5 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.

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

#make-wordpress-orgupdates

Test Chat Summary: 12 March 2024

On Tuesday, March 12, 2024 at 04:30 PM GMT+5:30, <test-chat> started in #core-test facilitated by @webtechpooja Agenda can be found here.

Attendees: @webtechpooja, @huzaifaalmesbah, @freewebmentor, @oglekler, @hage, @krupajnanda, @devmuhib, @mainetenance

1. Announcements 📣

  • WordPress 6.5 Release Candidate 1 was released last week on March 5. RC2 was also released on March 12.
  •  Highlights from WordCamp Asia 2024 – 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. Asia was in Taipei, Taiwan. Here, you can check the quick summary, including Matt’s Q&A.
  • Recap of Core Test team at Contributors Day WCAsia – The Test team had a great contributors’ day at WordCamp Asia. @webtechpooja has shared about WordCamp Asia that it was a great & successful 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/.. The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-Test team worked on the following tasks:
    • Tested WP 6.5 RC1 across different environments(10 contributors tested).
    • Test report submitted for 2 tickets of the WP 6.5 release.
    • We found 2 new 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/ related issues that are submitted on GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.
    • We worked on 1 handbook page related to how to use wget to crawl pages for new testers, which is under review. We will soon add it to the handbook.
    • We had a nice discussion on how we can continue user testing calls for the #outreach program with @bph
  •  Josepha shared about Unblocking WP6.5 – Font Library and Synced Pattern Overrides. give it a read.
  •  Gutenberg 17.9 is scheduled for release on March 13 and will include these issues.

Test Team Announcements

2. Focal Group Updates

This part checks on any specific areas of the test, such as manual testing, unit testing, E2E, the handbook, etc. Does anyone have an update pertaining to any of these items?

The Test team is working on criteria for providing Test Team Profile Badge – Your Feedback Needed! Please check out the post and provide your valuable feedback.

At WordCamp Asia Contributor Day, the Test team has worked on creating a draft that will be useful for our new contributors. Please have a look and provide your feedback. Here is the Draft of using wget to crawl pages for new testers.

@webtechpooja asked if anyone knows about any specific 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 that makes this work easy and fast, and @costdev has suggested Broken Link Checker plugin.

3. Call for testers/visibility:

4. Open Floor

@ankit-k-gupta has asked for suggestions about the Test Team Profile Badge – Your Feedback Needed!

We have included all the possible areas where Test Team contributions should be recognized via badge. However, we believe that if there are any additional areas where test contributions should be considered for earning a badge, we are open to suggestions. If you find any such areas, please feel free to suggest them.

Next Meeting 🗓

The next scheduled meeting is on Tuesday, 19 March 2024 at 16:30 GMT+5:30<test-triage> in #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

Test with Playground

Are you excited about the next big release in the WordPress world? The current target for the WordPress 6.5 release is March 26, 2024, which is less than a month away! Your help in testing 6.5 ensures everything in this release is the best it can be.

In addition to betaBeta 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. and RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. testing with a handy tool like the WordPress Beta Tester 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, which requires a hosted or local development environment, did you know that you can test WordPress’s newest features using only your browser? Let’s see how WordPress Playground makes this possible.

“Instant” Test Environment

It’s true! Launching a site with WordPress Playground makes getting set up for testing much easier. Here’s a shortcut to launch Playground running the latest WordPress pre-release, with Test Reports pre-installed to help with bug reports.

  • Use the menus in the top-right corner of a Playground instance to change the 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. http://php.net/manual/en/intro-whatis.php. version, load additional PHP extensions, and more.
  • After applying changes, the Playground will reload with your new configuration.

Let’s Test!

Now open up the Help Test WordPress 6.5 post and put 6.5 through its paces! You can easily test and experiment with the latest development version of WordPress.

In addition to testing the latest pre-release build, here are the things what to Test with Playground:

  • Check Site Health to see if there are already some issues that will be unrelated to the update.
  • Check for Errors, Warnings, and Notices.
  • Open the developer console in the browser.
  • Try to create a new post, add some content, and save it, especially try to copy and paste content from another source, add comments, add media files of different types, and do other usual actions in the admin. While doing it, pay attention to the information in the console to see if there are any issues.
  • Test in different languages.
  • Use just your keyboard to navigate, or use a screen reader.
  • Test with both 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. and classic themes.
  • If you want to create your own setup in Playground and save it for later use, export your configuration with the download/export button in the top-right corner of Playground. Use the upload/import link to restore a saved configuration in the future.

If you’d like to learn more about WordPress Playground, check out the official Playground start page, and to go even further, the Playground developer portal.

Share Your Experience

Have you tried Playground for testing yourself? Were there any WordPress features that you couldn’t test? Got any tips or tricks you learned on the way? Please share your feedback in the comments below.

A big thank you to @oglekler, @ankit-k-gupta, and @ironprogrammer for contributing to this post.

#6-5#fse-outreach-program#full-site-editing

Test Team Chat Agenda for 12 March 2024

Here is the agenda for the upcoming Test Team Chat scheduled for 12 March 2024 at 11: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.

#agenda

Week in Test: March 12, 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: 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: 11 March 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, 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. 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 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.5 tickets need PHPUnit tests built to accompany their respective patches:

  • No ticket has been available for the PHPUnit Test in the past weeks.

6.5 Related issues need testing

The following 6.5 tickets need testing those have patches:

#60740 wp_mime_type_icon function fails to return non-SVG icons

Profile Badge Awards 🎉

No Badges were 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>The test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

X-post: Test Team Update: 11 March 2024

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

Test Team Profile Badge – Your Feedback Needed!

In the Test Team, we are planning to create a handbook page to provide criteria for earning the Test Team Badge. After discussions, we have finalized the criteria listed below to earn the Test Team Badge. There are a few recommendations that we should consider before incorporating them into the handbook.

If you would like a badge on your 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/ profile that acknowledges your contributions to the Test Team, the following criteria must be met:

Test Contributor Badge

To earn a Test Contributor Badge, you must have completed at least one of the following:

  • Submitted a test report comprising at least 3 tickets for testing instructions, issue reproduction, or patch testing either on WordPress or 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/. Please note that reports can be submitted, whether it’s on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. or GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.
  • Reported an issue on Core Trac or the Gutenberg GitHub repo which has been fixed and merged into a WordPress release.
  • Submitted unit or end-to-end tests that have been merged.
  • Contributed to a Test handbook PR that has been merged.
  • Participated in ZIP package builds or default theme tests during a #core <release-party>.
  • Participated in 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/. (as a table lead, providing technical support, or assisting with onboarding).
  • Suggested a thoughtful idea aimed at improving testing processes in any way, which gets implemented.

Test Team Badge

If you have served as a Test Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. or Test Lead in any major releaseMajor 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. of WordPress, you are eligible for the Test Team badge.

How to Request a Test Team Badge?

If you meet the criteria mentioned above, you can request a badge using this link. You will have to include details that demonstrate you have met the criteria mentioned above.

Upon request, a Test Team Rep will confirm your contribution(s) and assign you a badge. There will be a monthly review of contributions, and badges will be awarded at that time. The Test Team will post updates on newly awarded profile badges on the Test Team blog.

Call for feedback.

What do you think of the suggested criteria? Please leave your thoughts on this post by Friday, 22 March 2024.


Week in Test: March 4, 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: 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: 4 March 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 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. 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 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.5 tickets need PHPUnit tests built to accompany their respective patches:

  • No tickets have been available from the past 1 week

6.5 Related issues need testing

The following 6.5 tickets need testing those have patches:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

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