Core Test Team at WCEU 2024: Contributor Day  

Hello WordPress enthusiasts!

We’re gearing up for an exciting Contributor Day at WordCamp Europe (WCEU) 2024, set to take place next month in the beautiful city of Torino, Italy! This annual gathering of WordPress aficionados brings together a diverse group of contributors to collaborate, learn, and make significant strides in the WordPress project. Here’s a sneak peek at what we have planned for the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Test Team and how you can get involved.

Core Test Team Goals

Our objectives for the day are ambitious but focused:

Collaboration and Community

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/. at WCEU 2024 will not just be about work; it will also be about building connections and fostering community spirit. The collaborative atmosphere will be palpable, with contributors exchanging ideas, offering help, and celebrating each other’s successes. The energy and enthusiasm of the participants will be truly inspiring, reinforcing the sense of belonging and shared purpose within the WordPress community.

Test Team Table Leads

We’re thrilled to introduce our Test Team Table Leads for WCEU 2024. These dedicated individuals will be guiding and supporting contributors throughout the day:

Their expertise and enthusiasm will be invaluable in ensuring a productive and engaging Contributor Day for all participants.

Helpful Resources

The links below have details that will be helpful on contributor day.

Be Prepared

To ensure you get the most out of Contributor Day, please review the following before the event so that you can focus on the fun stuff when you arrive:

Looking Ahead

As we prepare for this Contributor Day, we look forward to the progress and innovation that these contributions will bring to the WordPress project. We encourage everyone who plans to participate to stay engaged and keep the momentum going. Your contributions, whether big or small, make a significant impact.

Thank you in advance to all the contributors who will join us in Torino and those who will participate remotely. Together, we’re making WordPress better. 

Please stay updated for WCEU 2024, and 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/.

See you next month 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. Europe 2024!

Props to @martinkrcho, @webtechpooja, and @krupajnanda for peer review of this post.

+make.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//test/

#contributor-day, #wceu, #core-test

Test Chat Summary: 21 May 2024

On Tuesday, 21 May 2024 at 14:00 GMT +3, <test-chat> started in #core-test facilitated by @webtechpooja. The agenda can be found here.

Attendance: @webtechpooja, @hitendra-chopda, @oglekler, @lumiblog, @ankit-k-gupta, @hareesh-pillai, @lamarajan, @mukesh27, @sumitbagthariya16, @krupajnanda, @nhrrob, @sumitsingh, @rcreators, @freewebmentor, @kafleg, @huzaifaalmesbah, @hareesh-pillai

1. Looking for Volunteer

  • Triage Facilitator May 28 – needs volunteer
  • Chat meeting Facilitator June 4 – needs volunteer
  • Chat Meeting recap note taker June 4 – @ankit-k-gupta

2. Profile Badge Awards 🎉

Profile badge awarded to harshalkadu, harshalk, Hitendra Chopda, Ramon Ahnert, and Sumit Bagthariya.

3. WCEU 2024 Test Team Table Leads

@boniu91 and @martinkrcho will be our Test Table leads. @krupajnanda and @ankit-k-gupta will be online leads.  A post containing all the information about what and how contributors can help at the WCEU contributor table will be published soon.

The WCEU 2024 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/. will be on June 13 2024. Details can be found here

4. Announcements 📣

5. Test Team Updates

6. Focal Group Updates

7. Questions/Blockers

No questions/blockers were reported by the members. 

8. Call for Testers/Visibility

9. Open Floor

@nhrrob mentioned there is a bug scrub happening today for WordPress 6.6 in the #core channel at 14:00 UTC on 21 May 2024. He encouraged beginners to join as it’s a good opportunity to learn about how tickets move forward and what keywords mean. 

@webtechpooja then said they are thinking of starting a test bug scrub for upcoming 6.6 version tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets in the #core-test channel, asking if anyone is interested.

@oglekler expressed interest, saying it would be great with the 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 release in 2 weeks and some promising enhancements that need testing, stating “No tests – no go”.

@pbearne shared a trac link with a list of tests waiting to be committed that could be looked at.

@oglekler shared another trac link as a priority for the 2 weeks before beta 1.

@webtechpooja asked if anyone had day/time preferences for scheduling a bug scrub meeting. She also stated focus will be on as many tickets as possible with everyone’s support.

10. Next Meeting 🗓

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

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

#meeting-notes

Test Chat Summary: 7 May 2024

On Tuesday, 7 May 2024 at 14:00 GMT +3, <test-chat> started in #core-test facilitated by @nhrrob. The agenda can be found here.

Attendance: @webtechpooja, @shiponkarmakar, @sumitbagthariya16, @zunaid321, @hage, @nhrrob, @hitendra-chopda, @monikarao, @lumiblog, @pooja9712, @rcreators, @krupajnanda, @voboghure, @devmuhib, @pbearne, @devsahadat.

1. Looking for Volunteer

  • Next meeting Note Taker – Looking for Volunteer.
  • Next meeting facilitator – @lumiblog

2. Announcements 📣

3. Test Team Updates

4. Focal Group Updates

5. Questions/Blockers

6. Call for Testers/Visibility

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

7. Open Floor

@webtechpooja acknowledged @zunaid321 for facilitating the CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-Test team table at WordCamp Sylhet 2024. @nhrrob also praised @zunaid321 on his recent involvement in the recent releases. 

@webtechpooja provided guidance on joining the Core Test team to @devsahadat who had asked how to join core-test, contribute and earn a Test Contributor badge.  She also shared the link to core handbook where one could learn more about testing. 

@nhrrob announced the impending release of WordPress 6.5.3 and encouraged participation in the release parties. 

@webtechpooja shared information on data liberation and WordPress Playground usage

The conversation shifted to holiday plans, with @shiponkarmakar mentioning Buddha Purnima/Vesak which is to be on 23rd May, and @nhrrob discussing Mother’s Day celebrations, 12th May. 

@pbearne raised questions about finishing @covers for tests and shared resources on PHPUnit annotations

@webtechpooja updated on changes to @covers and discussed plans for addressing them, involving the core team. 

@ironprogrammer informed @pbearne about the significant changes required to prepare for PHPUnit 10/11. He suggested revisiting plans to avoid potential rework and shared a link to a relevant ticket on WordPress TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. for further reference.

The discussion concluded with @pbearne and @webtechpooja agreeing to await further input before finalizing plans for the core test meeting.

8. Next Meeting 🗓

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

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

Thank you, @webtechpooja, for the peer review of this post.

#core-test, #gutenberg, #meeting-notes

Test Chat Summary: 23 April 2024

On Tuesday, 23 April 2024 at 16:30 GMT+5:30, <test-chat> started in #core-test facilitated by @sumitsingh. The agenda can be found here.

Attendees: @webtechpooja, @sumitsingh, @huzaifaalmeabah, @hitendra-chopda, @lumiblog, @sumitbagthariya16, @ankit-k-gupta, @krupajnanda, @pooja9712, @nhrrob, @voboghure, @freewebmentor, and @nikitasolanki1812

1. Looking for Volunteer

2. Announcements 📣

3. Test Team Updates

  • Weekly update: Test Team Update
  • 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.

4. Focal Group Updates

5. Questions/Blockers

Nothing discussed.

6. Call for Testers/Visibility

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

7. Open Floor

Nothing discussed.

Next Meeting 🗓

The next scheduled meeting is on Tuesday, April 30, 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!

#meeting-notes

#core, #core-test, #fse-hallway-hangout, #meeting-notes

Test Chat Summary: 9 April 2024

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

Attendees: @krupajnanda, @huzaifaalmesbah, @hage, @rahulharkhani, @ankit-k-gupta, @shiponkarmakar, @oglekler, @mujuonly, @semnaveen, @sumitsingh, @hitendra-chopda.

1. Looking for Volunteer

2. Announcements 📣

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

4. Focal Group Updates

  • Test Team Profile Badge! – We have almost finalized the criteria for awarding badges. Thanks to @ironprogrammer and @oglekler for their valuable feedback. Thanks to @ankit-k-gupta for working on this.
  • Use a spider to crawl the test website. @nagpai worked on a draft of this 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. He will be working on pending things during this week.

5. Questions/Blockers

Nothing discussed.

6. Call for testers/visibility

7. Open Floor

  • It was a Hindu New Year and people across India celebrated this day.

Next Meeting 🗓

The next scheduled meeting is on Tuesday, April 23, 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!

#meeting-notes

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

#core-test, #fse-hallway-hangout, #meeting-notes

Week in Test: 16 January 2023

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:

Early Opportunities to Test WordPress 6.5

Ahead of 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 for WordPress 6.5 on February 13th, this is an early opportunity to provide feedback as features are rapidly underway. Of note, this is intentionally just a selection of what’s ready to test and doesn’t include everything mentioned in the roadmap. Expect a broader testing post, like this for 6.4, for the release once beta 1 is out in the world. 

Weekly Testing Roundup 🤠

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

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

Reproduction Testing 🔁

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

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

Patch Testing 🩹

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

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

PHPUnit Tests 🛟

Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. 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.4.2 tickets need PHPUnit tests built to accompany their respective patches:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

  • WordPress End of Year Celebrations! – Amidst the myriad events and releases that get highlighted during the course of a year in WordPress, countless other projects and contributions quietly move us ever closer to our goals.
  • A Look Ahead at WordPress in 2024 – Curious about WordPress’s big-picture items for 2024? Phase 3, Data Liberation, new meetups, and more, get the spotlight in this episode
  • Are you interested in helping pilot a new tool to streamline testing and improve developer feedback? Please see Early Opportunities to Test WordPress 6.5

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.

Thank you @ankit-k-gupta for the peer review.

#build-test, #core-test

Week in Test: 16 December 2022

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:

FSE Program Testing Call #19: Running Through Refinements

Help efforts to wrap up Phase 2 of the WordPress Roadmap by putting the editor’s latest updates to the test (😉) in a simulation of making a few improvements a client’s website. Please leave feedback by 6 January 2023 🗓 #fse-outreach-program

Weekly Testing Roundup 🤠

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:

  • #57322: Twenty Twenty-Three: Gradients clear on save with KSES filters active.
  • #57329: Cannot save new custom template when name has non-Latin characters.
  • #57339: Twenty Twenty theme pull quote border color issue.

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:

  • #57320: RevisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision.: add 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. before deleting revisions.
  • #56412: Twenty Sixteen: gallery 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. produces shifted or scrambled output.

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.2 tickets need PHPUnit tests built to accompany their respective patches:

  • #55290: Not all image edits are applied to all subsizes.
  • #56340: PHP8.1 E_DEPRECATED in PasswordHash::gensalt_blowfish.

Profile Badge Awards 🎉

And a huge belated Thank You to the following contributors who earned the Test Contributor profile badge by participating in the WordPress 6.1 and 6.1.1 releases:

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

🚨 There will be no more regular #core-test meetings held for the remainder of 2022. Weekly meetings will resume on 3 January 2023. See you then!

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

#build-test, #core-test

Week in Test: 15 October 2022

Hello and welcome to 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 | 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:

Help Test WordPress 6.1 🌟

6.1 RC1 was released on Tuesday, and is available for testing. See the 6.1 Call for Testing post for a rundown of major new features and tips for testing. Prereleases of 6.1 will be available until its official release the first week of November, so please test and provide feedback before 1 November 2022.

Call for Testing: Plugin Dependencies

Have you ever gotten stuck installing a fancy new 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, and then spent two days in support forums just to find out that you needed to install another required plugin to get it working? Or are you a plugin author who would like to bundle plugins for a smoother setup experience for your users? Plugin Dependencies is here to help! See the Plugin Dependencies call for testing, and provide feedback before 1 December 2022. #feature-project

Weekly Testing Roundup 🤠

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:

  • #56768: Base64-encoded images render in editor, but not frontend.
  • #56789: Toolbar: .screen-reader-shortcut does not have background color until focused.

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:

  • #55990: Twenty Twenty: Pullquote 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.: Add Citation Text Color Issue.
  • #48244: script-loader.php: Use _n() when multiple results found.
  • #56388: Remove unnecessary comments from compiled block styles.
  • #56802: Query: Post IDs cached for search and other ‘LIKE’ queries are unreachable.

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.2 tickets need PHPUnit tests built to accompany their respective patches:

  • #47164: map_deep in formatting.php does not handle null-byte.
  • #55290: Not all image edits are applied to all subsizes.
  • #56340: Resolve PHP 8.1 E_DEPRECATED in PasswordHash::gensalt_blowfish.

Profile Badge Awards 🎉

Thank you to the following contributors who have earned the Test Contributor profile badge. These users have participated in WordPress 6.1 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. release parties, as well as performed general testing over the past few weeks:

Read/Watch 📖

Upcoming Meetings 🗓

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.

#build-test-tools, #core-test, #feature-plugin, #feature-project

Week in Test: 23 September 2022

Hello and welcome to Week in Test, the place where contributors of any skill level can find opportunities to contribute to WordPress through testing. For even more talk about testing, join the Test Team over in #core-test.

Jump to: Calls for Testing | Weekly Testing Roundup | Profile Badge Awards | Read/Watch | 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:

WordPress Help Test WordPress 6.1 (get involved)

You’ve heard all the “cool kids” 😎 talking about it: 6.1 Beta 1 was released on Wednesday, and is available for testing. See the 6.1 Call for Testing post for a rundown of major new features and tips for testing. Prereleases of 6.1 will be available until its official release the first week of November, so 🗓please provide feedback before 1 November 2022.

FSE Program Testing Call #17:
Guiding 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/ Gallery (get involved)

Take on the roll of an intrepid website owner who makes the switch from Twenty Twenty to Twenty Twenty-Two. Discover 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. site editing by working with navigation, headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. and footer patterns, categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. templates, and more! Includes a testing option for users without a dev environment. 🗓Please leave feedback by 6 October 2022. #fse-outreach-program

Would you like to help organize calls for testing? Help work toward a bug-free WordPress and become a testing facilitator.

Weekly Testing Roundup 🤠

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:

  • #56591: Error decoding JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. with TT2 theme on ddev installation.
  • #56600: Twenty Ten: Pullquote block text is not reflected in editor.

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:

  • #56599: “All” view not selected for views of custom post typeCustom Post Type WordPress can hold and display many different types of content. A single item of such a content is generally called a post, although post is also a specific post type. Custom Post Types gives your site the ability to have templated posts, to simplify the concept.. More testing needed for plugins that extend the WP_Posts_List_Table class.
  • #48244: Expand translation options between singular and plural results (_n).
  • #55290: Not all image edits are applied to all subsizes.

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.1 tickets need PHPUnit tests built to accompany their respective patches:

  • #21650: Replace serialize() with print_r() in stats() function in wp-includes/cache.php.
  • #55448: WP_Widget_Block outputs empty container if widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. has no output.
  • #56340: PHP 8.1 E_DEPRECATED in PasswordHash::gensalt_blowfish.

Profile Badge Awards 🎉

Congrats and thank you to the following contributors who have earned the Test Contributor profile badge:

Read/Watch 📖

Upcoming Meetings 🗓

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.

Special thanks to @annezazu and @laurlittle for review of this post.

#build-test-tools, #core-test

Week in Test: 8 September 2022

Welcome to another exciting installment of Week in Test, where contributors of any skill level can find opportunities to contribute testing to the WordPress project. You can find the Test Team in #core-test.

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 over the next couple of weeks:

Weekly Testing Roundup 🤠

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:

  • #56505: Un-necessary Language Files are Installed.
  • #56519: Inner blocks serialization bug in serialize_block function.
  • #56490: wp-cron.php using count() on null.

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:

  • #55721: Visually align important data on the add new plugins screen.
  • #47513: JavaScriptJavaScript JavaScript or JS is an object-oriented computer programming language commonly used to create interactive effects within web browsers. WordPress makes extensive use of JS for a better user experience. While PHP is executed on the server, JS executes within a user’s browser. https://www.javascript.com/. TypeError when Video Playlists use native video elements.
  • #56468: sanitize_option() does not handle deprecated timezones correctly.

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.1 tickets need PHPUnit tests built to accompany their respective patches:

  • #56325: Some blocks’ RTL stylesheets not loading when RTL language is set.
  • #55448: WP_Widget_Block outputs empty container if widgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. has no output.
  • #55005: Improve PHP performance for block.json files.

Profile Badge Awards 🎉

Thank you to the following contributors who earned the Test Contributor profile badge by participating in the WordPress 6.0.2 release party:

Read/Watch 📖

Upcoming Meetings 🗓

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.

Props @laurlittle and @annezazu for their time to review this post.

#build-test-tools, #core-test