Highlighted Posts

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

Team Chat Agenda: July 16, 2024

Here is the agenda for the upcoming Test Team Chat scheduled for 16 July 2024 at 11:00 UTC, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

Leave a Comment

  • Do you have something to propose for the agenda?
  • Can’t make the meeting, but have a question for the Test Team?

If any of the above apply, please leave a comment below.

#agenda, #meeting

Week in Test: July 15, 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: 15 July 2024

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

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

Reproduction Testing 🔁

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

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

Patch Testing 🩹

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

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

PHPUnit Tests 🛟

Who? Any QA or 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.7 tickets need PHPUnit tests built to accompany their respective patches:

6.7 Related issues need testing

The following 6.7 tickets need testing those are having patches:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

2024 Schedule:

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

X-post: Test Team Update: 15 July 2024

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

Test Chat Summary: 2nd July 2024

On Tuesday, 2nd July 2024 at 11:00 UTC, <test-chat> started in #core-test facilitated by @krupajnanda . The agenda can be found here.

Attendance: @webtechpooja@krupajnanda@mobarak@hitendra-chopda@ankit-k-gupta@lamarajan@sumitbagthariya16@devmuhib@shiponkarmakar@pooja9712, @voboghure (async), @sumitsingh (async), @nhrrob (async), @hage (async)

1. Looking for Volunteer

  • Triage Facilitator July 9 – @mobarak
  • Chat meeting Facilitator July 16 – Volunteers Needed
  • Chat Meeting recap note taker July 16 – @voboghure

2. Profile Badge Awards 🎉

No badge was awarded this week.

3. Announcements 📣

  • WordPress 6.6 RC1 was released on June 25. We are now in a hard string freeze. Note that the dev-feedback and dev-reviewed workflow is required prior to committing to the 6.6 branch (handbook reference).
  • WordPress 6.5.5, a security release, was shipped on June 24
  • Gutenberg 18.6.1 was released on June 25
  • We are currently in the WordPress 6.6 release cycle. The WordPress 6.6 RC2 release is scheduled for today, July 2. Please review this post for an update about the Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. Phase.
  • Gutenberg 18.7 is scheduled for July 3 and will include these issues. This version will NOT be included in the WordPress 6.6 release.

4. Focal Group Updates

5. Questions/Blockers

6. Call for Testers/Visibility

7. Open Floor

There were no issues to discuss.

8. Next Meeting 🗓

The next meeting will be on Tuesday, July 16, 2024 at 11.00 UTC, held on #core-test! </test-chat>

#core-test, #meeting-notes

X-post: Let’s start testing Learn.WordPress.org

X-comment from +make.wordpress.org/training: Comment on Let's start testing Learn.WordPress.org

Week in Test: July 8, 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:

  • Help test WordPress 6.6 – We are currently looking for volunteers who can help us in testing the upcoming version.

Weekly Testing Roundup 🤠

Weekly update: Test Team Update: 08 July 2024

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

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

Reproduction Testing 🔁

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

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

Patch Testing 🩹

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

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

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

Upcoming Meetings 🗓

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

2024 Schedule:

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

#core-test

X-post: Test Team Update: 8 July 2024

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

Team Chat Agenda: July 2, 2024

Here is the agenda for the upcoming Test Team Chat scheduled for Tuesday, July 2, 2024 at 04:30 PM GMT+5:30, which is held in the #core-test Slack channel. Lurkers welcome!

Agenda

  • Attendance
  • Note-taker and facilitator selection for the next meeting
    • This week’s facilitator is – @krupajnanda
    • This week’s note-taker is – Tapan Kumer Das
    • 9 July Test Triage facilitator – Mobarak Ali
  • Announcements
    • We are currently in the WordPress 6.6 release cycle. The WordPress 6.6 RC2 release is scheduled for today, July 2. Please review this post for an update about the Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. Phase.
    • 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.7 is scheduled for July 3 and will include these issues. This version will NOT be included in the WordPress 6.6 release.
  • Badges Awarded
    • No badge awarded this week.
  • Test Team Announcements
  • Focal Group Updates
  • Questions/Blockers
  • Call for testers/visibility:
  • Open Floor
  • Got a topic? Add in comments below, or bring it up live during the chat.

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.

X-post: Test Team Update: 1 July 2024

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

Week in Test: July 1, 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:

  • Help test WordPress 6.6 – We are currently looking for volunteers who can help us in testing the upcoming version.

Weekly Testing Roundup 🤠

Weekly update: Test Team Update

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

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

Reproduction Testing 🔁

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

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

Patch Testing 🩹

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

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

6.6 Related issues need testing

The following 6.6 tickets need testing those are having patches:

Profile Badge Awards 🎉

No Badges awarded this week.

Read/Watch/Listen 🔗

  • WordPress 6.6 RC1 was released on June 25. We are now in a hard string freeze. Note that the dev-feedback and dev-reviewed workflow is required prior to committing to the 6.6 branch (handbook reference).
  • WordPress 6.5.5, a security release, was shipped on June 24.
  • Gutenberg 18.6.1 was released on June 25.
  • We are currently in the WordPress 6.6 release cycle. The WordPress 6.6 RC2 release is scheduled for next Tuesday, July 2. Please review this post for an update about the Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. Phase.

Upcoming Meetings 🗓

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

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