Category Archives: Kibble

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

Moses Cursor Ssebunya 5:07 am on March 4, 2026  

Month in Test: March 3, 2026

Hello and welcome to another edition of Month 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.

Table of Contents

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:

Test Handbook 📘

Merging of Test Handbook in 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/

For the last few weeks, a good number of test contributors embarked on the journey of reviewing our new Test Handbook based on GitHub. The Process has been concluded successfully with the merging.

  • We want to inform that the Test Handbook is officially synced. There might be a couple of bugs and things that are not looking good pending to be fixed.
  • Feel free to give it a check here, and if you find any bugs, go to the GitHub repository and report them.
    • You can send a PR with the fix, or simply send the issue, and we will check it

Weekly Testing Roundup 🤠

Bi-Weekly update: Test Team Update

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 skills? Dive in to contribute, and gain coveted props 😎 for a coming release.

1. WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Testing

a. 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 (4) 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:

b. Bug Reproduction

It is necessary to confirm if the bug is happening under multiple conditions and environments, using the bug reproduction report in order to validate the issue.

The following tickets (141) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, then provide a bug reproduction report:

c. Test Team Issues

Here are the current activities being discussed in the Test Team Github:

  1. We need to review the Test Team Issues. If you have a possible solution, comment in the Issue or submit a PR.

2. 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/ Testing

👋 Want to contribute to WordPress/Gutenberg? If you have a bug or an idea, read the contributing guidelines before opening an issue. If you’re ready to tackle some open issues, we’ve collected some good first issues for you.

a. Gutenberg Bug Reproduction Testing

The following tickets (3) have been filed reporting a known bug and needs testers to manually test, then provide feedback through a bug reproduction report that the issue can be reproduced.

b. Gutenberg Patch Testing

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 (1) 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 🎉

Congratulations to the recipients of the Test Contributor Badge 🎉

  • none this Month

– Kindly find the Contribution Guidelines here

Read/Watch/Listen 🔗

  1. WordPress Ecosystem Announcements
  2. Test Team Announcements
    • Weekly Patch Testing Scrub: Tuesday at 15:00 UTC (runs every week)
    • Weekly Test Chat: Thursday at 15:00 UTC (runs every week)
    • Monthly Voice Test Chat: First Thursday of each month at 15:00 UTC
  3. Call for Testing

Upcoming Meetings 🗓

🚨 There will be regular #core-test meetings. The schedule is being worked on and final schedule will be shared after finalizing the discussion

Current 2026 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.

Props to @nikunj8866 for helping review this article and offering feedback

Ankit K Gupta 2:48 pm on February 17, 2026
Tags: , ,   

Test Scrub Schedule for WordPress 7.0

As you’re aware, WordPress 7.0 is slated to be the first major release of 2026, with the official release date set for April 9, 2026. As we gear up for this important milestone, our Test team will be shifting gears a bit. 

Starting from our upcoming weekly Patch Testing Session, we’ll be running a Test Scrub for WP 7.0 instead of the usual Future Milestone Tickets. These scrubs will focus specifically on tickets and issues related to the WordPress 7.0 milestone. It’s a great opportunity to contribute to this major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality. and make a tangible impact on the final product. 

Where Will It Happen?

Each Test Scrub will take place in the #core-test channel on the 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/ at the same time as our regular weekly Test team meetings. If additional release‑focused scrubs are scheduled, they’ll also be announced in #core-test and added to the meetings calendar. 

What Tickets Will We Focus On?

We’ll primarily concentrate on tickets that are tagged Has Patch or/ Needs Testing for the 7.0 milestone. You can find these tickets in the 7.0 report on Trac. As the release moves through 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. and RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge., we’ll also highlight key features and regressions that need focused testing.

Interested in Leading a Test Scrub?

Did you know that anyone can lead a Test Scrub at any time? Yes, that means you can!

If you’re interested in leading a scrub, please reach out in the #core-test Slack channel with: 

  • The day and time you’re considering
  • The report or tickets you’d like to focus on (for example, a specific TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. report, a feature area, or a Beta/RC build)

If you’re planning a scrub that’s specifically focused on WordPress 7.0, that’s fantastic! We can add it to our schedule so the rest of the team knows to join in. Leading a scrub is a great way to contribute. 

Let’s Contribute Together

This is a perfect chance to get involved with the major release of WordPress 7.0, learn more about the release process, and help ensure the quality and stability of WordPress. Your contributions will make a difference, so join us for the Test Scrub sessions and be a part of this exciting release. 

Thank You ❤️

Thanks to everyone contributing time, testing, feedback, and expertise. Community testing plays a critical role in making each WordPress release successful.

Let’s work together to make WordPress 7.0 a smooth and high-quality release.

Props to @huzaifaalmesbah, @marybaum, and @nikunj8866 for pre-publish review.

#call-for-testing, #core

David Smith 3:51 pm on January 27, 2026
Tags: , navigation,   

Call for Testing – Customizable Navigation (“Mobile”) Overlays

Customizable Navigation Overlays are a new feature for WordPress 7.0 that gives you full control over “mobile” navigation menus using blocks and patterns.

We’re inviting the WordPress community to test this feature and share feedback. We’d love to hear from you by February 9, 2026 to allow time for refinements before the feature freeze.

Why This Change?

Mobile navigation overlays have been a significant pain pointPain point Pain points are “places where you know from research or analytics that users are currently getting hung up and have to ask questions, or are likely to abandon the site or app.” — Design for Real Life for WordPress users. Users have had very little control over the design and content of their mobile navigation menus. When someone taps a hamburger menu on mobile, they’ve been stuck with WordPress’s default overlay – no ability to customize branding, add promotional content, adjust styling, or control the layout.

This creates real problems:

  • Sites can’t maintain brand consistency on mobile
  • No way to add calls-to-action or promotional content in the mobile menu
  • Mobile navigation feels disconnected from the rest of the site design
  • Users resort to complex workarounds or custom code

Custom Navigation Overlays addresses this by giving users full control over their mobile overlay menus using the familiar 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.

What’s New?

Navigation Overlays enable users to:

  • Create custom mobile overlay menus using blocks and patterns
  • Control overlay design, content, and behavior – add branding, images, calls-to-action, and more
  • Manage multiple overlay variations – create different overlays for different contexts

Custom overlays are saved as template parts, which means they’re reusable components you can manage alongside your other theme templates. As such Themes can also provide their own Overlays suited to their particular design and use case.

This feature is targeting WordPress 7.0 and represents the first iteration of customizable navigation overlays. We’re shipping a solid v1 foundation that solves the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. user need, with plans to expand capabilities in future releases based on community feedback.

We’d Love Your Feedback

We’re inviting the WordPress community to test this feature before it ships in 7.0. Your feedback will help us:

  • Catch bugs and edge cases
  • Validate the user experience is intuitive
  • Ensure compatibility across themes and use cases
  • Identify what works well and what needs refinement

Timeline: We’d appreciate feedback by February 9, 2026 (this gives us time to address issues before the February 19 feature freeze)

How to Test

Testing Environment

Quick Start with Playground:

  1. Open this Playground instance.
  2. You’re ready to test in the Site Editor.

What you’ll need:

  • Latest Chrome, Firefox, or Safari browser
  • A Navigation block inserted to access overlay controls

What to Test

We’ve outlined three testing scenarios below. You don’t need to test everything – pick what interests you or matches your use case.

Scenario 1: Create Your First Custom Overlay

Try this if you: Want to experience the feature as a first-time user

Steps:

  1. Insert a Navigation block on a page or in a template
  2. Look for the overlay customization controls in the block settings
  3. Create your first custom overlay
  4. Preview it in the editor
  5. View it on the frontend in mobile view

What we’d love feedback on:

  • How easy was it to discover the overlay controls?
  • Was the creation process clear and intuitive?
  • Does the overlay look correct on mobile?

Scenario 2: Build a Custom Overlay from Scratch

Try this if you: Want to design a custom overlay with your own blocks and styling

Steps:

  1. Create a new overlay starting with blocks (not a pattern)
  2. Add various content: headings, images, buttons, navigation links, etc.
  3. Style your overlay: colors, spacing, typography
  4. Test submenu behavior
  5. View on frontend mobile

Bonus: Try creating multiple overlay variations and switching between them.

What we’d love feedback on:

  • Can you build the overlay design you want?
  • Are the design controls sufficient?
  • Does switching between overlays work smoothly?

Scenario 3: Test Edge Cases

Try this if you: Want to help us find bugs and boundary conditions

Ideas to test:

  • Try creating an overlay without a close button – what happens?
  • Test with different WordPress themes
  • Delete a custom overlay and see how Navigation blocks handle it
  • Add multiple close buttons to one overlay
  • Test with complex block combinations

What we’d love feedback on:

  • Does anything break or behave unexpectedly?
  • Are error messages (if any) helpful?
  • How does the feature handle edge cases?

Testing Tip: Try Both Editor and Frontend

For any scenario you test, it’s helpful to check both:

  1. ✅ Editor experience – Does it work while editing?
  2. ✅ Frontend experience – Does it work on the live site (especially mobile)?

You can use browser DevTools device emulation or resize your browser to mobile width to test.

SEO and 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) Feedback Wanted

We’re actively discussing the technical implementation of overlay markup and would especially value input from SEO and accessibility experts.

The question: Where should the overlay markup be placed in the 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.?

Current options under consideration:

  • Within the Navigation block’s <nav> element
  • Outside the <nav> element (as a sibling)
  • At the top of the page’s HTML markup
  • At the bottom of the page’s HTML markup

Each approach has potential implications for:

  • SEO: How search engines crawl and index content
  • Accessibility: Screen reader behavior, navigation landmarks, focus management
  • Performance: Initial page load and rendering

If you have expertise in SEO or accessibility, we’d appreciate your perspective on which approach would best serve users. Feel free to share relevant standards, best practices, or real-world considerations that should inform this decision.

Relevant discussion: https://github.com/WordPress/gutenberg/issues/74583

How to Share Feedback

Comment on this post with your findings, or create 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/ issues in the WordPress/gutenberg repository and link to them in your comment.

Helpful to include:

  • Browser and device/theme used
  • Screenshots or recordings (visual evidence is super helpful!)
  • Clear steps to reproduce any issues
  • Your assessment of severity (if reporting a bug)

Example:

Browser: Chrome 131, macOS
Theme: Twenty Twenty-Five

Issue: Overlay close button not visible on dark backgrounds

Steps to reproduce:
1. Create overlay with dark background
2. Add default close button
3. View on frontend mobile

Expected: Close button should be visible
Actual: White close button disappears against dark background

Severity: Medium - workaround is to add custom close button

[Screenshot]

Known Limitations (v1)

This is the first iteration of Navigation Overlays for WordPress 7.0. Some capabilities are intentionally out of scope for this release and will be considered for future versions:

  • Mega menus
  • Dialog-block reuse for overlays
  • Inline editing overlays directly in main canvas (currently must edit via template part editor)
  • Custom mobile breakpoints

See the complete scope: https://github.com/WordPress/gutenberg/issues/73084

We’re focused on shipping a solid foundation that solves the core user need. Future releases will expand capabilities based on community feedback and real-world usage.

Resources

Thank you for testing! 🙏

Your feedback will help ensure Navigation Overlays provide a great experience for WordPress users managing mobile navigation. This is a v1 release, and your input will shape future iterations of the feature.

#call-for-testing #wordpress-7-0 #navigation

+make.wordpress.org/core/

Olga Gleckler 5:52 am on September 15, 2025
Tags:   

Test Team Reps: Submit Your Votes (2025–2026)

This election is closed, and I’m contacting the finishers for final steps before making the official announcement.
Thank you, everyone who voted, as well as the nominees who stepped forward for this role!

Thanks to everyone who took part in nominations and for all your contributions to testing and team progress this year. 🎉 We will now elect two Test Team Representatives for the next term.

Voting is open for two weeks until 0:00 UTC on September 29, 2025.

Who Are the Nominees

In alphabetical order, this term’s nominees are:

How to vote

  • Who can vote: Test Team contributors only.
  • How many picks: You may select up to 2 nominees.
  • Voting period: Open for two weeks.

Eligibility & fairness checks (why we’re doing this)

Last year we encountered unusual voting activity and had to reset the poll. To keep things fair, learning from this experience, we’re adding light verification.

What we’ll ask on the form (and how we’ll use it):

  • Your 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/ profile URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org (to confirm you’re a Test contributor).
  • Your email (one vote per address; used only to prevent duplicates—votes will be kept private).

Thank you for helping us keep the process welcoming, transparent, and fair. 💙

Vote Now

👉 The poll will remain open for two weeks, until September 29, 00:00 UTC. After that, votes will be tallied and reps selected based on votes received.

Props to @krupajnanda and @sirlouen to review this post.

#team-reps

Pavan Patil 11:23 am on April 23, 2025  

Team Chat Agenda: April 23, 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 23rd April 2025 at 16: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.

Krupa Nanda 1:19 pm on January 29, 2025
Tags: ,   

Team Chat Agenda: 29th January 2025

Here is the agenda for the upcoming Test Team Chat scheduled for 29 January 2025 at 16:00 UTC, 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 – Looking for a volunteer
  • Looking for volunteers
    • Facilitator and note taker for the next bi-weekly chat
    • Remote Table leads for WCAsia. Please check this guide fore more details on what to expect as Table Lead.
    • To work on Call for testing WordPress 6.8 release. For more detail, check out the guide: How to facilitate a Call for Testing
  • Announcements
  • Test Team Announcements
  • 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.

#agenda, #core-test

Pooja Derashri 7:57 am on October 15, 2024
Tags:   

Introducing: Test Team Reps for 2024 – 2025

Following this year’s nominations and voting period, we are pleased to announce our new Test Team Reps for the 2024-2025 term! 🎉 Join us in welcoming Olga Gleckler and Krupa Nanda to represent the Test team!

Election Results | Detailed Results

Olga Gleckler (@oglekler)

Olga is a full-stack developer with over 15 years of experience in software support, marketing, and web development. She is an active WordPress contributor, a Codeable expert, and a fantasy writer.

She has been contributing to WordPress in her spare time since 2019.

She was the Test co-lead for the WordPress 6.5 release and the triage co-lead for several other releases. She is actively participating in the Contributor Mentorship Program. She believes in open-source and is passionate about everything she does. She likes rock music and sharing knowledge.

You can read more about Olga on her profile page.

Krupa Nanda (@krupajnanda)

Krupa is a QA Engineer with over 6+ years of experience who specializes in testing WordPress-based projects. Her career has also included roles as a Project Coordinator and Release Manager, where she oversaw the development of in-house plugins and add-ons.

Krupa attended her first 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. in October 2023 and has since tried to contribute to as many as possible. She also participated in the second batch of the Contributor Mentorship Program (CMP), where she learned how to contribute effectively. Krupa successfully completed the program and is now a mentor for the third batch of CMP. In addition to her mentorship role, Krupa is a Global Translation Editor (GTEGeneral Translation Editor General Translation Editor – One of the polyglots team leads in a geographic region https://make.wordpress.org/polyglots/teams/. Further information at https://make.wordpress.org/polyglots/handbook/glossary/#general-translation-editor) for the Gujarati locale. She also volunteers and speaks at WordCamps and meetups.

Krupa is from Jamnagar, Gujarat, and she currently lives in Pune, Maharashtra. Beyond her professional pursuits, Krupa’s journey is characterized by the seamless integration of motherhood and a thriving career. As she continues to grow, Krupa is excited about the future opportunities that lie ahead.

You can read more about Krupa on her profile page.

Congratulations 🥳 to our new reps! I look forward to supporting their move into the team rep role.

Props, @ankit-k-gupta, for peer review of this post.

#team-reps

Pooja Derashri 11:12 am on October 4, 2024
Tags:   

Team Rep Poll Update: Addressing Unusual Voting Activity

We want to inform everyone about an important update regarding the ongoing Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. poll. On October 3, we noticed an unusual pattern of voting, with a large number of votes coming from the same IP address. After investigating, we discovered that some of the votes were generated by bots, which compromised the integrity of the poll.

To address this issue, we’ve taken immediate action by implementing new restrictions to prevent multiple votes from the same IP address. This will ensure that each person can cast vote only once, maintaining fairness for everyone involved.

As part of this process, we have also reset the poll, which means that all previous votes have been erased. If you’ve already voted, we kindly ask that you please resubmit your vote.

Vote Now

Thank you for your understanding and cooperation as we work to keep the voting process transparent and fair!

Link for the old post: Test Team Reps: Submit Your Votes

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

#team-reps

Pooja Derashri 11:33 am on October 2, 2024
Tags:   

Test Team Reps: Submit Your Votes

This election is closed, and I’m contacting the finishers for final steps before making the official announcement.
Thank you, everyone who voted, as well as the nominees who stepped forward for this role!

Important Update: On October 3, we observed a high volume of votes coming from the same IP address in the Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. poll. Upon further investigation, we discovered that bots were involved. As a result, we implemented restrictions, and multiple votes from the same IP will no longer be accepted. We have reset the poll, clearing all previous results. If you voted before, please submit your vote again. Read our announcement post. Thanks

From August 13 to October 1, 2024, the Test team opened nominations for new reps to serve over the 2024-2025 term. The polls are now open and ready for your votes!

What Are Team Reps?

For a refresher on the Test Team Rep role, please see the most recent call for nominations. The Test team will elect two team reps for the next term, to collaborate and share responsibilities.

Who Are the Nominees?

In alphabetical order, this term’s nominees are:

Where Can I Vote? 🗳️

Please cast your votes through this anonymous public poll. You may vote for two nominees, but once you submit your vote, you cannot vote again.

Vote Now

And because many of you are testers and like to break test things 😉, please note that attempting to vote for all three at once will lock out your vote 🙅. Please resist the temptation to test the voting platform!

👉🏻 The poll will remain open for two weeks, until October 11, 00:00 UTC. After that, votes will be tallied and reps selected based on votes received.

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

#team-reps