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: Weekly Testing Roundup | Profile Badge Awards | Read/Watch/Listen | Upcoming Meetings
Weekly Testing Roundup 🤠
Weekly update: Test Team Update
Here’s a roundup of active tickets that are ready for testing contributions.
Did you know that contributions with the Test Team are also a fantastic way to level up your WordPress knowledge and skill? Dive in to contribute, and gain coveted props 😎 for a coming release.
Reproduction Testing 🔁
Who? Any contributor.
Why? It is helpful to show an issue exists for other users in order to move a ticket forward for patching.
The following new tickets are awaiting review, and need testers to attempt to reproduce the reported issue (aka “repro”), and then provide a reproduction test report with the results:
- #62761 Database error logged on re-install with custom LOGGED_IN_COOKIE name
- #62767 Featured image: media-models.min.js?ver=6.8-alpha-59568:2 Uncaught TypeError: t.get is not a function
- #62776 Non-latin post type rewrite slugs break post editor since 6.7
- #62779 WordPress pattern module in file selection in same images visible in all the pages.
- #62777 Force a 404 when no sitemap provider is found
- #62781 Twenty Twenty Theme: Inconsistent styles between editor and front-end in calendar block
- #62763 get_calendar(): IDs may be duplicated
- #62778 display options for Links/Blogroll in sidebar not saving
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:
- #14060 Misleading “You do not have sufficient permissions to access this page.”
- #13459 Conflict between post and page slugs/permalinks when permalink setting is set to /%postname%/
- #55974 Bundled theme: Add support for border options
- #61765 Twenty Twelve: The large quote pattern does not use a quote block
- #60374 Twenty Sixteen: Navigation block inherits colors from button styles
- #40057 Double hashed value for background-color of body.background-color
- #56311 Week query variable is not being sanitized correctly
- #21022 Use bcrypt for password hashing; updating old hashes
PHPUnit Tests 🛟
Who? Any QA or PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/index.php developer contributors who can (or are interested in learning how to) build automated PHPUnit tests.
Why? Automated tests improve the software development feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop for quality and backward compatibility.
The following 6.8 tickets need PHPUnit tests built to accompany their respective patches:
6.7 Related issues need testing
The following 6.8 tickets need testing those are having patches:
- #55974 Bundled theme: Add support for border options
- #61765 Twenty Twelve: The large quote pattern does not use a quote block
- #40057 Double hashed value for background-color of body.background-color
- #21022 Use bcrypt for password hashing; updating old hashes
Profile Badge Awards 🎉
No Badges awarded this week.
Read/Watch/Listen 🔗
- WordPress Themes Need More Weird: A Call for Creative Digital Homes
- The Nominations for 2025’s Core Team Reps are now open! Please nominate people in the comments of that post. Self-nominations are welcome. The deadline is January 31, 2025.
- There is currently no release date planned for WordPress 6.7.2. You can review the next minor release milestone.
Upcoming Meetings 🗓
🚨 There will be regular #core-test meetings held for 2025.
2025 Schedule:
- January 8, 2025, at 21:30 GMT+5:30: <test-triage> #core-test!
- January 15, 2025, at 21:30 GMT+5:30: <test-chat> #core-test! in #core-test.
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.