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

Test Chat Summary: 27 February 2024

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

1. Attendance and Looking for Volunteer

Attendees: @oglekler, @bph, @shiponkarmakar, @huzaifaalmesbah, @sumitbagthariya16, @hasanuzzamanshamim, @webtechpooja, @nazmul111, @ankit-k-gupta, @devmuhib, @narolainfotech, @lumiblog, @tapan29bd, @hage, @krupajnanda, @rcreators, @ironprogrammer, @freewebmentor

Note-taker and facilitator for the next meeting:

Facilitator – Looking for volunteer (@webtechpooja will be traveling during the next meeting to attend WCAsia.)
Note taker – @freewebmentor

Looking for Volunteer

We are looking for a volunteer to work on user calls for testing (for more detail, check out the guide: How to facilitate a Call for Testing).

@webtechpooja asked for more insight from @bph. She added that the recent outreach program restart revealed positive feedback, highlighting the effectiveness of this approach in engaging non-coders. Test Team seeks collaborators for the regular creation of no-code user testing calls, catering to site builders and owners. Join us at 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 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/. for discussions, or connect asynchronously to plan and schedule Hallway Hangouts.

2. Announcements 📣

  • WordPress 6.5 Beta 2, released on February 20, 2024, extends thanks for your contributions. Asked to join the upcoming WordPress 6.5 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. 3 release party in the #core channel.
  • Exciting update: WordPress 6.5 introduces AVIF support, a cutting-edge image format delivering superior quality and compression, up to 50% smaller than JPEGs. Explore and test this feature in the latest release!
  • WordPress developer live stream: testing WordPress 6.5 If you want to know what is upcoming in WP 6.5. @psykro is hosting an online workshop. Do join the workshop.

3. Test Team Announcements

4. Focal Group Updates

@ankit-k-gupta is extending the opportunity to host the Test Team Triage biweekly meeting. If anyone is interested, please express your willingness.

@hage asked, Is there additional AVIF information beyond Specifically, I’m curious if existing JPEGs can be converted to AVIF without using a 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.

@ironprogrammer replied, The update introduces support for new AVIF uploads and auto-conversion upon upload via the ‘image_editor_output_formatfilterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output., but it doesn’t alter existing images. @hage suggests that to modify existing images to AVIF in bulk, installing a corresponding plugin may be necessary.

@oglekler has a proposal that she would love to see working groups between developers and testers. @bph replied they just created 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/ group WordPress/Outreach that developers can pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” for feedback and testing. She also drafted the announcement on Google Doc.

@oglekler replied – @bph, I’m not just suggesting casual pings; I’m advocating for close collaboration from project inception. Testers can contribute valuable insights on project architecture right from the start, applicable not only to the Editor but across WordPress. @bph replied – Yes, of course, the ping is the first step for the developer when they are ready to connect.

@hage added – The background to my question: I would like to test this in more detail. @webtechpooja replied – you’re on the right track! @oglekler and other Test Release leads are crafting a post set to release this week. It will contain comprehensive details and testing instructions, so stay tuned for updates.

5. Call for testers/visibility

6. Open Floor

@rcreators think we should create high priority testing tags for features that need more testing. Or we can have quite a separate list for testing for this part.

@bph asked – why in the list of things to testing issues from Gutenberg repo are not listed. Just want to know the history of the decision. @ironprogrammer is seeking clarification on areas where we might have overlooked pointing out issues related to GB (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/).

@bph replied I only noticed it on This week of Test where new tickets are listed under Reproduction tests. They seems to be all trac tickets. @ironprogrammer mentioned the omission of highlighting Gutenberg issues in WiT posts wasn’t intentional. Challenges arose due to labeling inconsistencies and filtering issues, making it difficult to categorize “small/medium/large” ticket types accurately. The dilemma lies in triage/labeling, and the suggestion is to explore using the “Needs Testing” label for potential solutions.

@rcreators added – Also, if we can add something like a deadline for testing task that would be great. @webtechpooja replied – In our open-source, volunteer-driven project, imposing deadlines is not feasible.

@krupajnanda requested to change the weekly meeting time. But rest of the people are happy with the current time and suggested her to join asynchronously.

7. Next Meeting 🗓

Next meeting will be on Tuesday, March 12, 2024 at 04:30 PM GMT+5:30, held on #core-test! </test-chat>

If anyone wants to facilitate the next meeting, please feel free to comment in this thread.

Thank you, @webtechpooja, for the peer review and for helping me write this post. 

#core-editor-improvement, #meeting-notes

Help test WordPress 6.5 Beta 3

This post is not covering all important features for testing in WordPress 6.5 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. 3, more will come. The previous call with general instructions for testing can be found here.

If you want to help in testing but are not sure how to start, join the #core-test channel in SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. and ask for guidance. Seasoned testers will gladly point you in the right direction and share interesting stuff to play with. 


WordPress 6.5 RC1 is coming on 5 March 2024 which means String freeze – no new strings should be added or changed in the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. to give Polyglots the ability to translate strings into different languages before the release. This is the time to pay careful attention to new strings. If you know English by heart, please test new features and check out the language.

Table of contents

Key features to test

I18n – Translations performance

WordPress Core contributorsCore Contributors Core contributors are those who have worked on a release of WordPress, by creating the functions or finding and patching bugs. These contributions are done through Trac. https://core.trac.wordpress.org. put great efforts into localization performance, and we can see significant improvement in translation loading.

TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket: #59656

Detailed information about the project:

Not all the 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’s features went into the Core and the plugin is still useful with translations from 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.-files that can benefit with OPcache.

Testing instructions

Special request to developers who maintain multilingual sites to test WordPress 6.5 with real data on staging versions of the real sites. Do it now and be confident when the time will come to update sites on production and benefit from this improvement.

General checks

  • Front end theme translations
  • Back end translations
  • Memory usage
  • Site speed
  • Compatibility with different plugins, including plugins for multilingual sites and plugins with huge amounts of strings
  • MultisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core.https://codex.wordpress.org/Create_A_Network. translations
  • Absence of errors with different PHP versions (more: supported versions, recommendations)

Notes:

  • WordPress 6.5 has new or changed strings that are not available for translation until RC1. WordPress, themes and plugins can also have untranslated strings in languages you choose to test with. If you want to translate WordPress, follow the guidance in the Translator Handbook.
  • If you find an issue file a new ticket on Trac under the I18N component.
  • If you find an issue with a plugin or theme, please, report it to its developer.
  • The Query Monitor plugin is an active observer and can make an impact on the result as well.
  • Some strings can lack translation, and, in this case, they will be absent in 6.4 as well as 6.5 (with some exceptions as ‘Activate’ after plugin installation that looks the same but actually is a different string).
  • At this stage, the solution is working fine at first glance, and you have to be creative, notice details and take bold actions to get into every possible corner and dig deep to be sure that there are no hidden holes.

Fresh installations

  • Install 6.4 and 6.5 latest Beta/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 English default language keeping everything else the same.
  • Install Query Monitor plugin on both sites to check memory usage and execution time.
  • Debug settings
  • Change the default site language to another language
    • Check that translations are working in the Admin
    • Check that translation work on the front end (you will have by default Twenty Twenty-Four theme and it has strings for the front end)
    • Check that in general each 6.5 admin page uses less memory than 6.4 pages
    • Check that JS translations work, for example by clicking on the Apply button on the plugin page without selecting any plugins, install plugin, install theme, use Quick/Bulk Edit and change post/page attributes
  • Change the user language to another one adding a third language. If you know the RTL language, please check it and mix with LTR.
  • Install a lot of languages to check that the system will still be quick with this number of languages.
  • Install plugins that have translations in chosen languages (one of the most popular will most likely be one of them) and check that translations are identical.
  • Install a classic theme and check its translations.

If we missed some aspects that should be checked, please leave a comment below this post.

Plugin dependencies

Logic of installing, activation, deactivation and removal of plugins was reworked. This is a significant enhancement in addition to already existing safeguards during plugins installation for compatibility and errors checks. 

To get detailed information and find previous test calls, please, read Merge announcement

Testing instructions

Environment

  • Install WordPress 6.5 latest Beta/RC version
  • Debug settings
    • Enable Debug and Debug log
    • Keep Console open to notice JS and ajax/REST request errors
  • Remove all plugins
  • Install Query Monitor plugin and keep it active (it will show PHP errors if they will accrue)
  • Pay attention to details during the process

General checks

Plugins without dependencies should be installed, activated, deactivated, uninstalled, enabled/disabled to auto-updates as before (single or bulk). 

  • Install several plugins
  • Activate plugin
  • Activate several plugins using Bulk action
  • Install old versions of plugins via file upload
  • Update one plugin
  • Update several plugins using Bulk action
  • Try to install plugin that will cause fatal error (invent nonexistent function, for example)
  • Deactivate one plugin
  • Deactivate several plugins using Bulk action
  • Delete a plugin
  • Delete several plugins using Bulk action
  • Did the same with Enable/Disable auto-updates

Test dependencies

  • Installation: Dependents can only be installed via Plugins > Add New if their dependencies are installed.
  • Activation: Dependents anywhere (Plugins > Installed plugins / Plugins > Add New / modals / WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ / after installing via ZIP) can only be activated if their dependencies are activated first.
  • Deactivation: Dependencies can only be deactivated on Plugins > Installed plugins (single or bulk), if their dependents are deactivated first.
  • Deletion: Dependencies can only be deleted on Plugins > Installed plugins (single or bulk), if their dependents are deleted first.

Steps to follow

Prepare several plugins and zip them into own archives to install via admin

  1. my-hello-dolly/my-hello-dolly.php
<?php

/**
* Plugin Name: My Hello Dolly
* Requires Plugins: hello-dolly
*/
  1. my-car/my-car.php
<?php

/**
* Plugin Name: My Car
*/
  1. my-car-trailer/my-car-trailer.php
<?php

/**
* Plugin Name: My Car Trailer
* Requires Plugins: my-car
*/
  1. game-stone/game-stone.php
<?php

/**
* Plugin Name: Game Stone
* Requires Plugins: game-scissors
*/
  1. game-paper/game-paper.php
<?php

/**
* Plugin Name: Game Paper
* Requires Plugins: game-stone
*/
  1. game-scissors/game-scissors.php
<?php

/**
* Plugin Name: Game Scissors
* Requires Plugins: game-paper
*/
ActionExpected behaviour
1. Install ‘My Hello Dolly’ plugin via Plugins > Add New
– Activate plugin
Plugin is installed
Error message
Dependency is not installed automatically
2. Install ‘My Car Trailer’ plugin via Plugins > Add NewPlugin is installed
3. Activate ‘My Car Trailer’ pluginPlugin is not activated
Error message
4. Install and activate ‘My Car’ plugin
– Activate ‘My Car Trailer’ plugin
Plugins are activated
‘My Car’ plugin has no link to deactivate
5. Deactivate ‘My Car Trailer’ plugin
– Deactivate ‘My Car’ plugin
Plugins are deactivated
‘My Car’ plugin has no link to delete
6. Delete ‘My Car Trailer’ plugin
– Delete ‘My Car’ plugin
Plugins are deleted
7. Install and activate ‘My Car’ plugin
– Install and activate ‘My Car Trailer’ plugin
– Manually delete ‘My Car’ plugin in the wp-content folder
– Open Plugins page in admin
‘My Car’ plugin will be deactivated due to its absence
‘My Car Trailer’ will still be active
Notice message
8. Add plugins ‘Game Paper’, ‘Game Scissors’, ‘Game Stone’ into wp-content folderWarning on the plugin page about invalid requirements 

These are only expected behaviour.

Now it is time to be creative and think about other possible scenarios. Write them down before actually testing and check if your expectations are matching what is happening.

Remember to check the Test Dependencies section above so that your expectations meet the current status of the feature.

Other improvements

Focus styles updated for full WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. compliance

Trac ticket #51870

The focus style for form inputs, buttons, and links styled as buttons, which was first introduced in WordPress 5.3 (#34904), has been fully updated in WordPress 6.5. In WordPress versions prior to 6.5, the focus styles were inconsistent across different elements like inputs, buttons, and links.

This update modifies the focus styles for all interactive elements to be consistent with the styles introduced in WordPress 5.3, in order to meet WCAG accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) standards for minimum colour contrast ratios.

Please help test consistency of focus styles for form inputs, buttons and links styled as buttons with this video to guide you.

Fixing inappropriate pointer cursor on disabled form controls in WordPress

Trac ticket #59733

WordPress 6.5 introduces a fix for an issue where disabled form controls in WordPress were still showing a pointer cursor instead of the default cursor.

Previously, WordPress set all form controls and their label elements to use cursor:pointer to highlight that they are interactive. However, when a control is disabled or has `aria-disabled=”true”`, using a pointer cursor is inappropriate and doesn’t follow web standards.

The issue affected disabled checkboxes, radio buttons, and other form controls throughout WordPress, including in the 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/ editor. While WordPress traditionally hides disabled controls rather than disabling them, there were still instances of improper cursor styling.

To address this, the change makes sure labels and disabled form controls, including those with aria-disabled, use the default platform-dependent cursor. This follows web accessibility standards and fixes the confusing pointer cursor on disabled controls. Interactive controls will still use a pointer for consistency with WordPress’ prior styling.

Testing instructions

  • Go to Settings > Reading
  • Make sure ‘Your homepage displays’ is set to ‘Your latest posts’.
  • Hover the mouse on the ‘Homepage:’ and ‘Posts page:’ disabled select elements.
  • Observe the mouse cursor is the default one.
  • Hover the mouse on the disabled select elements labels.
  • Observe the mouse cursor is the default one.
  • Install and activate the Link Manager plugin.
  • Add a new link.
  • In the form to create a new link, check the checkbox at another web address of mine.
  • Observe all the following checkboxes and radio buttons get disabled.
  • Hover the mouse on all radio boxes, checkboxes, and their labels.
  • Observe the mouse cursor is always the default one.

Media: AVIF support enabled

Trac ticket #51228

WordPress 6.5 introduces native support for uploading, editing, and saving images in the AVIF (AV1 Image File) format, provided the server has the required AVIF libraries installed.

The AVIF image format utilises the intra-frame encoding techniques of the AV1 video codec to offer drastically improved compression ratios compared to older image formats like JPEG, PNG, and even newer ones like WebP.

By incorporating AVIF encoding and decoding into the media functions, WordPress 6.5 allows users to upload AVIF files and take advantage of the file size savings, typically around 30-50% over JPEG/PNG for equivalent visual quality. Edited AVIF images can also be resaved while preserving alpha transparency and colour profiles.

Testing instructions

  • Verify your WordPress install supports AVIF — check Tools-> Site Health -> Info tab -> (expand) Media Handling section. Either GD or Imagick must have “AVIF” listed.
  • Upload an AVIF image to a post or the media library. Some test images are available in the libavif repository.
  • Test features like cropping and rotating in the media library and the editor
  • Test viewing post in all supported browsers (Browserstack would be great for that)
  • Test using the image_editor_output_format filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to output AVIF’s for uploaded JPEGs, noting JPEG/AVIF file sizes with/without the filter.

The order of loading the import map and script modules has been changed. Now, the import map is loaded first, followed by the script modules. This fixes an issue where incremental import maps would fail if loaded after the script modules.

In classic themes, the import map and script modules are now loaded in the footer rather than the head. This is because the proper order (import map first) can’t be guaranteed when printing in the head in classic themes.

Testing instructions

Create a plugin with a dependency between two script modules and an import map. You can either follow the instructions below to create a test plugin, or simply download this test plugin.

Create a new plugin with three files:

test-plugin/test.php

<?php
/*
* Plugin Name: Test Script Modules
* Version: 1.0.0
*/

wp_register_script_module( 'bar', plugins_url( '/bar.js', __FILE__ ) );
wp_enqueue_script_module( 'foo', plugins_url( '/foo.js', __FILE__ ), array( 'bar' ) );

test-plugin/foo.js

import bar from 'bar';
bar();

test-plugin/bar.js

export default function bar() {
 console.log( 'bar' );
}
  • Upload the plugin on your test website.
  • Activate the plugin.
  • Open your site (frontend).
  • Check that “bar” was printed in the console.

To check that this fixes the positioning of the scripts/link in the classic themes:

  • Load a 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. theme (Twenty Twenty-Four or another)
  • Check that the scripts with type=”importmap” and type=”module”, and the link with rel=”modulepreload” are printed in the head.
  • Load a classic theme (Twenty Fourteen)
  • Check that the scripts with type=”importmap” and type=”module”, and the link with rel=”modulepreload” are printed in the footer.

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 @oglekler, @lumiblog, @vipuljnext@swissspidy@costdev@ankit-k-gupta and @webtechpooja  for contributing to this post.

#6-5, #test

Core Test Team at WCAsia 2024

WordCamp Asia 2024 is almost here! It takes place from March 7-9 at the Taipei International Convention Center (TICC), Taiwan. As is customary at 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. events, a Contributor Day will be held, taking place on Thursday, March 7.

🕰️ Important Times to Note:

Join the Test team in person or contribute remotely. We can’t wait to see you!

Contribute

The WordPress project offers numerous opportunities for contribution through testing. Some common ways to participate are to:

If none of the above sounds right, or you simply wish to know what contributing to WordPress with testing is all about, please stop by the table to chat or join #core-test channel.

Be Prepared

To ensure you get the most out of 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/., please review the following before the event so that you can focus on the fun stuff when you arrive:

Stay Updated

In addition to keeping the WCAsia 2024 homepage handy, join the #core-test and #contributor-day channels in Make WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/., and follow #wcasia for other event updates.

Share Your Thoughts

If you have any questions about Contributor Day or the Test Team, please leave a comment below or reach out on the #core-test Slack channel.

Also, if you’re attending Contributor Day in person, let us know in the comments!

Interested in Contributor Day, but not sure if Test is the right fit for you? Try out Make WordPress’s Find Your Team tool to discover other opportunities that may interest you.

Props to @ankit-k-gupta and @oglekler for peer review of this post.

#wcasia

Test Team Chat Agenda for 27 February 2024

Here is the agenda for the upcoming Test Team Chat scheduled for 27 February 2024 at 11:00 UTC, which is held in the #core-test SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. 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: February 26, 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: 26 February 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:

6.5 Related issues need testing

The following 6.5 tickets need testing those are having patches:

Profile Badge Awards 🎉

Test Contributor badge awarded to the following WordPress users:

Congratulations: @krupajnanda

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.

#make-wordpress-orgupdates

X-post: Test Team Update: 26 February 2024

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

Week in Test: February 19, 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: 19 February 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:

6.5 Related issues need testing

The following 6.5 tickets need testing those are having patches:

Profile Badge Awards 🎉

Test Contributor badge awarded to the following WordPress users:
Congratulations 🎉 @akshayar, @pbiron, @shailu25, @zunaid321, @sakibsnaz, @vipuljnext, @gajendrasingh, @lumiblog, @tejwanihemant, @mmaattiiaass, @jamieblomerus, @hardiksharma

Test team badge to the following WordPress users. They are the Test Leads for the WP 6.5 version:
Congratulations 🎉 @oglekler, @lumiblog, @vipuljnext

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.

#make-wordpress-orgupdates

X-post: Test Team Update: 19 February 2024

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

Test Chat Summary: 13 February 2024

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

Attendees: @ankit-k-gupta, @rcreators, @JavierCasares, @mahbubmr500, @anandau14, @huzaifaalmesbah, @vipuljnext, @zunaid321, @devmuhib, @sakibsnaz, @shiponkarmakar, @krupajnanda.

Note-taker and facilitator for the next meeting:

Facilitator – @krupajnanda
Note taker – looking for volunteer

1. Announcements 📣

  • Bug scrub schedule for WordPress 6.5 – This post lists bug scrub sessions dedicated to moving things forward toward the next major WordPress release, 6.5, slated for March 26, 2024. Read the full 6.5 Release Schedule.
  • Important milestones for WordPress 6.5 – The WordPress 6.5 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. 1 was scheduled for release on February 13th, which was yesterday. Be ready for the Beta and get started for testing soon.
  • Core Editor Improvement: Power in the Details – These “CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Editor Improvement…” posts (labeled with the #core-editor-improvement tag) are a series dedicated to highlighting various new features, improvements, and more from Core Editor-related projects. Take a moment to learn more about them—and explore how the power of details in 6.5 can transform your current workflows.
  • Improving block development documentation: 2023 recap and a look ahead – Over the last year, a group of contributors has been working to improve 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. development onboarding experience within the Block Editor Handbook. In this post, you can find the highlights of the updates made, pinpoint areas for further refinement, and outline our focus for the next few months and ways you can help.

2. Test Team Updates

  • Week in Test Post: Wondering where you can contribute and learn? The Test Team’s got you covered. Check out this post and pick any issue mentioned in it.
  • Test Team Update: Metrics for overall team progress

3. Focal Group Updates

  • We are working on some easy way to provide a badge to Test team contributors, so we worked on a handbook page where all the details are mentioned. Please Review Test team badge criteria and share your feedback.

4. Open Floor

  • @rcreators discussed that the 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/ 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 nightly build does not work with the Gutenberg regular plugin. Along with that we received the feedback from @JavierCasares  who shared updates on improving the WordPress test results tool, inviting questions on reviewing fails, accessing support for failed tests, and expanding testing capabilities like WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/ integration and pre-installed plugins for hosters.

Next Meeting 🗓

The next scheduled meeting is on Tuesday, February 20, 2024 at 04:30 PM GMT+5:30 for <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!

Thank you, @webtechpooja, for the peer review and for helping me write this post. 

#meeting-notes