Pooja Derashri 12:04 pm on March 12, 2024  

Highlighted Posts

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

annezazu 2:30 pm on May 28, 2026  

Help test new career functionality on WordPress.org

For many years, jobs.wordpress.net has been a resource for folks applying for jobs and looking for candidates. In recent weeks, various changes have been made to both the design and to WordPress.org profiles to better integrate career functionality with the aim to help foster careers in WordPress directly in 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/ infrastructure. This call for testing is to help ensure that those of us working on this are making changes that properly serve those seeking candidates or looking for jobs. If you have feedback that doesn’t align perfectly with the call for testing but that relates to the overarching vision of adding more career connections, please still share it in the comments below.

What is it?

The recent updates touch two surfaces:

  • jobs.wordpress.net — refreshed design and a more direct path between job listings and the candidates behind them.
  • WordPress.org profiles — new fields for job history, key accomplishments, and a “looking for jobs” toggle, so a contributor’s profile can double as a lightweight candidate page.

The goal is for someone’s WordPress.org profile to become a meaningful representation of their professional work in the ecosystem, and for that profile to be discoverable from the jobs board.

How to Test

The flows below are suggestions to give your testing some structure, but please don’t feel obligated to follow them in order or complete all of them. The important question is whether these surfaces feel solid enough to help people find jobs and find candidates, and whether you notice any bugs, UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. gaps, or unexpected behaviors.

Suggested Testing Flows

If you don’t fall into either the applying for jobs or looking for candidate bucket, please still test by trying out just the applying for jobs functionality and reviewing both experiences in WordPress.org profiles and on the Jobs site.

Applying for jobs

Add job history

  1. Log into WordPress.org and edit your profile by following this link https://profiles.wordpress.org/profile/edit/ 
  2. Find the Jobs tab and add one or more past roles.
  3. Save.
  4. Confirm the entries displayed correctly on your public profile.

Of note, we’re working on adding in an importer for a CV but we also want to ensure the base flowFlow Flow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it. of adding jobs works well.

Turn on “open to job opportunities”

  1. From your profile settings, enable the “open to job opportunities”  toggle.
  2. From there, decide if you want to enable the “Show an “Open to work” frame on my GravatarGravatar Is an acronym for Globally Recognized Avatar. It is the avatar system managed by WordPress.com, and used within the WordPress software. https://gravatar.com”.
  3. Click Save Settings. 
  4. Confirm your Gravatar changes and displays the frame. 

Of note, your profile will then appear on https://jobs.wordpress.net/#candidates. 

Add key accomplishments

  1. From your profile, add one or more key accomplishments.
  2. Save.
  3. Confirm they appear in the expected place on your profile.
  4. Try removing an accomplishment and confirm it’s removed. 

Browse jobs on jobs.wordpress.net

  1. Visit jobs.wordpress.net.
  2. Browse the listings.
  3. Try any filters or search.

Looking for candidates

Review how candidates appear on the Jobs site

  1. Go to https://jobs.wordpress.net/#candidates 
  2. Confirm relevant details (current job, role) are visible at a glance.
  3. Click on different candidates and review how job information is presented on their profiles.

Review individual profiles

  1. Go to https://jobs.wordpress.net/#candidates 
  2. Click on different candidates available to hire and review how job information is presented on their profiles on WordPress.org. 

Post a job listing (only do this if you have a real job to post)

Once more, only do this if you truly do have a job to post! Please do not post fake jobs.

  1. Go to https://jobs.wordpress.net/post-a-job/ 
  2. Fill out the information in the form for a real job you want to post.
  3. Click Submit job.
  4. Go to https://jobs.wordpress.net/#jobs
  5. View the job after submission and confirm it appears as you’d expect. 

Share your feedback by June 25th, 2026

Please comment on this post to share feedback. If you’re comfortable, you can also open issues in this GitHub repository directly.

Some questions to consider:

  • Did adding job history, accomplishments, or turning on “looking for jobs” feel intuitive? What features would you add to make it even easier?
  • Did your profile look the way you expected once you’d filled it out?
  • As someone looking for candidates, did the Jobs site surface the right people, and was it easy to understand who they are?
  • Did anything feel slow, confusing, or broken?
  • Are there pieces of the career story that feel missing: things you’d want to see your profile express, or filters you’d want when looking for candidates?

Shout out to @bor0 for reviewing this and for all of the help getting this functionality in place.

Moses Cursor Ssebunya 12:41 pm on May 28, 2026  

Test Team Voice Chat Summary:: 7th May, 2026

Voice Chat notes: 5/8/26 in #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/ AI took notes for this huddle from 15:01:42 – 15:58:07 UTC. The meeting covered updates and discussions on several test team initiatives, including 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 by the repository owner. https://github.com/ markdown templates, a fix for finding tickets, the ongoing handbook review, and issues with the Playground installation guide. A significant portion of the discussion focused on testing a new weekly digest workflow for Slack, and the team finalized a new alternating weekly meeting schedule. View huddle in channel

Attendees

@Moses Cursor, @ozgursar, @Huzaifa Al Mesbah, @nikunj8866, @r1k0, @Shazzad, @SAndrew, @Mohammed Kateregga, @BIGUL, @Azhar Deraiya, and @Kaushik Domadiya

🌟 Summary

  • Attendance and Introductions
  • Review/Update GitHub Markdown Test Report Templates
    • @Moses Cursor initiated a discussion to review and update the GitHub markdown test report templates, noting an issue where the existing template referenced an old report. [12:34] [14]
    • @Huzaifa Al Mesbah confirmed that he had requested the new reports be considered. [13:10]
    • @ozgursar suggested informing Yusuf about the updated test reports 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. from Sirlouen’s GitHub repository to update the markdown templates based on that. [13:43] [14:12] [14:29]
    • @Huzaifa Al Mesbah considered it a good idea but suggested creating a new issue for it, as Yusuf is a new contributor, and it might be better to handle it separately. [14:38]
    • @ozgursar agreed, noting the differences are not significant, and proposed waiting for Yusuf to make the requested changes before approving. [15:02] [15:19]
    • @Moses Cursor questioned the necessity of the current ticket if the new report already supports Markdown. [16:52] [17:32]
    • @ozgursar clarified that the combined report is archived, so Yusuf needs to work on the new one. [16:37]
    • @nikunj8866 offered to review the template once he had access to a system. [17:20]

🗣️ Announcements

This Slack Bot uses AI to generate notes, so some information may be inaccurate. They’re based on the huddle transcript and thread and can be edited anytime.

Props to the Slack Bot that helped make the summary and @huzaifaalmesbah for Peer reviewing this

Nikunj Hatkar 1:20 pm on May 25, 2026
Tags: ,   

Test Chat Summary: May 21st, 2026

On Thursday, 21 May 2026, 03:00 PM UTC, <test-chat> started in  #core-test facilitated by @nikunj8866. The agenda can be found here.

1. Attendance

In attendance was:
@nikunj8866 @huzaifaalmesbah @ozgursar @r1k0 @juanmaguitar @mabfahad @pavanpatil1 @mosescursor @andrewssanya (sync) @Jadavsanjay (async)

2. Volunteer

This week’s Note-taker was @nikunj8866

3. Test Team Discussions

Review the current handbook PRs before publishing

  1. Update reproduction and patch testing report templates
    • @ozgursar noted that the Test Reports plugin had already been updated 1 day ago, with the changelog confirming the change aligned with the handbook PR.
    • @huzaifaalmesbah confirmed 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. now reflects the new Bug Reproduction and Patch Testing templates.
    • Special thanks to @afragen for the quick turnaround on the plugin update.
    • Merged the PR after no concerns were raised.
  2. Create patch testing scrub guide
    • @ozgursar confirmed it looked good.
    • Merged this PR as well after review.

Proposed new handbook pages

  1. Proposal: Building a Test Chat and Bug Scrub Facilitator Plugin
    • @ozgursar proposed building a WordPress plugin to help facilitate Test Chats and Bug Scrubs by replacing boilerplate text placeholders.
    • @nikunj8866 suggested that a 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 by the repository owner. https://github.com/ issue template could be a simpler and more maintainable alternative to a plugin – paired with a sample filled-out issue on the Chat Moderator handbook page so facilitators know what good looks like.
    • @juanmaguitar floated the idea of exploring an AI Agent skill to handle this workflow, and @nikunj8866 asked that this idea be added to the GitHub issue to keep all proposals in one place.
    • @mosescursor expressed support for the GitHub template approach.
    • @ozgursar agreed the GitHub template serves a similar purpose and offered to build a prototype for the Scrub only during upcoming free days, with the goal of brainstorming further possibilities and finding something easier to maintain long-term.
    • @nikunj8866 welcomed the prototype idea and invited everyone to share feedback either 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/ or on the GitHub issue.

4. Open Floor

There were no additional topics raised during the open floor session.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

#core-test, #test-chat-summary

Nikunj Hatkar 4:33 am on May 22, 2026
Tags: ,   

X-post: Media Editor Modal: Call for Testing

X-comment from +make.wordpress.org/core: Comment on Media Editor Modal: Call for Testing

Nikunj Hatkar 9:20 am on May 21, 2026
Tags: ,   

Team Chat Agenda: 21st May, 2026

Here is the agenda for the upcoming Test Team Chat scheduled for Thursday, 21 May 2026, 03:00 PM 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.

#core-test, #test-chat-agenda

Ankit K Gupta 6:38 am on May 20, 2026
Tags: , FAQ, WP7.0   

WordPress 7.0 Updates & Testing – FAQ

WordPress 7.0 is scheduled to release today, and you may have some questions or doubts related to testing, updating, compatibility, or how the release process works.

Below are some questions that may help contributors, developers, 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./theme authors, site owners, and general WordPress users better understand the WordPress 7.0 release and testing process.

What is WordPress 7.0 RC5?

WordPress 7.0 RC5 (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. 5) is a near-final testing version of WordPress 7.0. At this stage, the release is considered feature complete, but community testing is still needed to identify remaining bugs, regressions, compatibility issues, and usability concerns before the final release.

When will the final version of WP 7.0 be released?

The final stable release of WordPress 7.0 is currently scheduled for May 20, 2026.

How can I know what is coming in WP 7.0 and how to test those features?

The following posts contain detailed information about new features, improvements, developer notes, and suggested testing areas for WordPress 7.0:

These resources can help contributors, testers, plugin/theme authors, and site owners better understand what is included in WordPress 7.0 and how to test related functionality.

Why is testing RC5 important?

Testing RC5 helps improve the stability and quality of WordPress 7.0 before it reaches millions of websites worldwide. Community testing helps uncover issues across different plugins, themes, hosting environments, browsers, devices, and workflows that may not appear in limited testing environments.

I already tested my site with WordPress 7.0 during 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. 2 & Beta 3. Do I still need to test with RC5?

Yes — RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. testing is still extremely valuable even if you previously tested earlier beta versions. During the RC phase, many bugs and fixes have already been added since Beta 2 and Beta 3.

I did not get a chance to test any Beta or RC versions with my existing WordPress site. Should I directly update once WP 7.0 is officially released?

It is not recommended to update a production siteProduction Site A production site is a live site online meant to be viewed by your visitors, as opposed to a site that is staged for development or testing. immediately without any prior testing, especially if your site uses custom code, multiple plugins, custom themes, or complex integrations.

Even though WordPress 7.0 is widely tested by the community before release, every website environment is different. It is always safer to test before updating production. 

I am not a technical person, but I have a WordPress site. Should I avoid updating to the latest WordPress version?

No. Keeping WordPress updated is important for security, performance, bug fixes, and compatibility improvements.

A good approach is to ask your hosting provider to create a staging site (a copy/replica of your live website) with the latest WordPress version installed. There, you can test your normal day-to-day workflows before updating your production site.

For example:

  • if you run a photo blog, try uploading/editing/deleting photos
  • if you run an eCommerce store, test checkout and orders
  • if you run an LMS site, test courses and student access

Real-world testing on a staging site can help identify issues before updating your live website.

Do I need technical knowledge to help test?

No. You do not need to be a developer or know how to code.

Even testing your normal day-to-day website workflows can be extremely valuable, whether you use WordPress for example:

  • an eCommerce store
  • a Learning Management System (LMS)
  • a business website
  • a blog
  • a portfolio
  • or any other type of website

Real-world usage testing helps identify issues that may not appear in limited development environments.

I just learned that a new WordPress version is coming, but I did not test my site with any Beta or RC versions. Is it okay to wait before updating after the official release on May 20 until I test my site?

Yes, absolutely. It is completely fine to wait and test your site before updating your live/production website to a major WordPress release.

Should I test RC5 on a production website?

No. RC versions are intended only for testing.

Please use:

Do not test directly on live / production websites.

What should I test first?

Start with workflows you use most often.

Suggested areas:

  • 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. editor
  • Site editor
  • Publishing workflow
  • Media uploads
  • Theme compatibility
  • Plugin compatibility
  • Menus/widgets/navigation
  • Responsive/mobile behavior
  • 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)
  • Performance

What should plugin and theme authors focus on?

Plugin and theme authors should carefully test:

  • Installation and activation
  • Updates
  • Editor integration
  • Frontend rendering
  • Settings screens
  • Custom blocks
  • APIs and hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same.
  • Styling/layout behavior
  • Fatal errors or warnings

Compatibility testing before release helps reduce user issues after launch.

What kinds of issues should testers look for?

Helpful issues to report include:

  • Fatal errors
  • Broken layouts
  • Missing UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. controls
  • Failed saves/updates
  • 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 issues
  • Accessibility regressions
  • Performance slowdowns
  • Mobile/responsive issues
  • Unexpected behavior changes
  • Plugin or theme conflicts

Even small usability problems can be valuable feedback.

How can I tell whether something is actually a bug?

A good approach is to:

  1. Reproduce the issue multiple times
  2. Test with unnecessary plugins disabled
  3. Switch temporarily to a default theme
  4. Compare behavior with WordPress 6.x if possible

If something worked previously but behaves differently in 7.0 RC5, it is worth reporting.

How do I report a bug?

Before reporting:

  • Try reproducing the issue consistently
  • Document exact reproduction steps
  • Collect screenshots or screen recordings if possible

Then report the issue through:

What information should a bug report include?

A useful bug report should include:

  • WordPress version
  • 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 version
  • Browser/device
  • Active plugins/themes
  • Exact reproduction steps
  • Expected result
  • Actual result
  • Screenshots or screencasts (if available)

Clear reports help contributors verify and fix issues faster.

What if I find a security issue?

Please do not report security vulnerabilities publicly.

Security issues should be reported privately through:

How much testing is enough?

There is no minimum requirement. Even 15–30 minutes of focused testing is valuable.

Testing a few important workflows carefully is often more helpful than trying to test everything quickly.

Where can I follow WordPress 7.0 updates?

You can follow updates on:

What is a WordPress Release Party?

A WordPress Release Party is a live, coordinated session where contributors gather in the Make WordPress Slack to help test, monitor, and celebrate a new WordPress release as it’s being packaged and published. It’s both a working session and a community event, where people collaborate in real time to catch last-minute issues, validate fixes, and ensure the release goes smoothly.

Here are detailed instructions on how to contribute to a release party.

What happens if the WordPress release team finds a critical bug during release party? Will the new version still be released?

Not necessarily. If a critical issue is discovered during release testing, the release team may decide to delay the final release until the issue is investigated and resolved.

The stability and safety of WordPress sites always take priority over releasing on a fixed date.

Need More Help or Have Questions?

If you still have any questions or doubts beyond the topics covered above, feel free to ask in the comments below or reach out in the #core and #core-test Slack channels.

Every test, bug report, reproduction step, screenshot, verification, and piece of feedback helps improve WordPress for millions of users worldwide.

Thank you to everyone helping test and contribute to WordPress❤️

#call-for-testing, #faq, #wp7-0

Nikunj Hatkar 4:34 am on May 20, 2026
Tags: ,   

X-post: Test Team Update: 20 May, 2026

X-post from +make.wordpress.org/updates: Test Team Update: 20 May, 2026

r1k0 2:51 pm on May 8, 2026
Tags:   

Test Chat Summary: 30th April, 2026

On Thursday, 30 April at 18:00 GMT+3, <test-chat> started in #core-test facilitated by @r1k0. The agenda can be found

1. Attendance

In attendance were: @ozgursar, @mosescursor, @khushdoms, @nikunj8866, @lumiblog, @juanmaguitar, @huzaifaalmesbah, @darshitrajyaguru97, @andrewssanya and @mohkatz (async)

2. Volunteer

This week’s facilitator and note-taker was @r1k0

3. Test Team Discussions

Review and finalize the current handbook PRs before publishing.

The team started its discussion with the first Pull Request by @juanmaguitar on adding a weekly digest workflow for the #core-test.

@r1k0 mentioned he shared his thoughts on the Pull Request and welcomed everyone to test it.

Since the Pull Request needed a bit more work, @juanmaguitar reverted it to a draft till it is properly refined, to begin reviewing and testing.

@r1k0 added that he will include a comment on the Pull Request on how to test the workflow locally and with 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/. He also offered to give anyone an invite to the test Slack and Repo to try out the workflow.

The team moved swiftly to the next agenda item, which was reviewing a Pull Request that seeks to correct a numbering issue in one of the Test Handbook pages.

@ozgursar said he had reviewed the code but noted that it contains HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. tags in the Markdown file. Which needed to be replaced with appropriate Markdown formatting. HTML tags should only be used as a workaround.

@ozgursar asked iamsohilvahora to fix the Pull Request with the suggested changes before the team can approve and merge it.

The team also checked in on the progress of another handbook Pull Request for a new documentation page.

@ozgursar mentioned that the Pull Request only needed a revision of the test report format.

@khushdoms acted fast and made the changes, allowing the team to review before publishing it.

Finally, @r1k0 asked the participants to share any comments or thoughts on a Proposal to update the Test Team meeting schedule.

@mosescursor expressed his excitement for this particular proposal.

@ozgursar encouraged everyone to vote using emojis in the last comment by @nikunj8866: 👍for Tuesday and 👀for Thursday.

@mosescursor reminded everyone that the closing will be closed on Saturday to allow others to cast their votes.

4. Open Floor

@ozgursar asked where the most appropriate place would be to add the Test Reports 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. in the Handbook, so that other pages can link to it.

He also added that we needed to use the forked version of the plugin in the WPContrib repo.

@r1k0 said we could reference it in the issue and patch reports pages.

Since this is a minor revision, @ozgursar pointed out that new contributors could try working on this.

5. Announcements

WordPress Ecosystem Announcements

Test Team Announcements

Call for Testing

6. Other Meetings

Props to @huzaifaalmesbah and @ozgursar for helping review this article and offering feedback

#test-chat-summary

Moses Cursor Ssebunya 1:12 pm on May 7, 2026
Tags: , ,   

Test Team Voice Chat Agenda: 7th May, 2026

Here is the agenda for the upcoming Test Team Voice Chat scheduled for Thursday, 7th May, 2026 at 15: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.

#core-test, #gutenberg, #make-wordpress-orgupdates

Nikunj Hatkar 12:49 pm on May 5, 2026
Tags: ,   

X-post: Test Team Update: 5 May, 2026

X-post from +make.wordpress.org/updates: Test Team Update: 5 May, 2026