Recently, at a WordPress Kolhapur Community Meetup, Makarand Mane hosted an insightful session where Krupa Nanda, a representative of the WordPress Core Testing Team, explained how anyone can contribute to testing WordPress releases. This blog post summarizes that session for beginners interested in the process of testing WordPress and contributing meaningfully even without coding experience.
Watch the Full Session here:
Makarand shared his experience organizing WordCamp events and leading contribution series that involved multiple WordPress teams. His goal was to increase involvement in WordPress contributions, especially core testing, which happens behind every WordPress version release. He introduced Krupa as the expert who would guide attendees through the process of contributing to the WordPress Core Testing Team.
Understanding the WordPress Testing Team
Krupa started by explaining the purpose of the Testing Team: to test WordPress core versions major or minor before they are released. She mentioned that the team communicates primarily through Slack channels, where different teams interact. Test Team members join weekly meetings, including “Test Chat” for discussions and “Triage” sessions focused on issue prioritization. You can join these meetings from the #core-test Slack channel.
For newcomers, Krupa advised exploring the WordPress Testing Handbook carefully. This handbook explains testing workflows, terminology, meeting schedules, and how unit and functional tests are conducted. Even attending two or three test meetings can help beginners understand the process.
Setting Up and Using Tools for Testing
Krupa highlighted two main environments for testing:
- Playground: An online vanilla WordPress setup accessible quickly without complex installation. It allows testers to replicate issues and test fixes within minutes. However, it has some limitations and less flexibility than a local environment.
- Local Environment: Testers can clone the WordPress repository, set up Docker, Node.js, and other dependencies on their system for a full-fledged testing environment. Though this setup takes more time initially, it offers greater flexibility and control than the Playground.
She demonstrated an example where a bug related to post categories was replicated and then tested both on Playground and a local environment. The process involved creating posts, assigning categories, and verifying whether posts displayed correctly by category highlighting the hands-on nature of testing.
Reporting and Managing Issues
Krupa explained how to report bugs using dedicated reporting tools and plugins. WordPress provides a Test Report Plugin that standardizes bug reports, making the process faster and clearer. Contributors should specify test environments, WordPress versions, themes, and whether the issue occurs on particular devices or browsers.
Before creating a new issue, it’s crucial to search to avoid duplicates. If the issue is already reported, contributors can add their replication details or new information in comments to assist triagers.
Using tags or keywords in issues is important for filtering and prioritizing. Krupa mentioned key tags like:
- Needs Testing: Issue requires testing confirmation.
- Needs Testing Information: Additional test environment info required.
- Has Testing Information: Test environment details have been provided.
- Has Screenshot: Visual proof of bug before or after fix.
Triage volunteers review issues, streamline the process, and help move tickets closer to resolution by organizing priorities.
Testing Fixes and Pull Requests
Testing is not just about reporting bugs but also confirming fixes. When a pull request (PR) is submitted to fix an issue, testers:
- Replicate the reported bug.
- Apply the fix from the PR.
- Verify if the problem is resolved.
- Test across different browsers/devices to ensure the fix does not introduce new issues.
- Confirm that related functionalities remain unaffected.
Developers are responsible for including unit tests with their fixes to ensure code quality, while QA testers focus on end-to-end testing.
Krupa showed how to clone a specific PR branch from GitHub to test fixes locally. This rigorous check helps maintain WordPress core quality.
Best Practices and Tips for New Contributors
- Start by joining Test Team meetings on Slack and get familiar with the culture.
- Observe for a few sessions if you are new to understand workflows before actively contributing.
- Use the Testing Handbook as a primary resource.
- Focus on meaningful contributions. Avoid repeatedly commenting on already confirmed and fixed bugs.
- Report bugs with clear replication steps, environment details, and screenshots.
- Use correct tags and keywords in reports to help triage efficiently.
- Participate in triage sessions if interested in organizing and prioritizing issues.
- Be patient when setting up local environments. Once set, restarting is easy and doesn’t require full reinstallation.
- Use the Playground for quick checks but prefer local setups for thorough testing.
- Don’t hesitate to ask questions in Slack or reach out to experienced team members like Krupa for guidance.
Final Thoughts
The WordPress Core Testing Team welcomes contributors of all skill levels. Testing is vital to ensure WordPress remains stable and user-friendly for millions. By following the steps shared by Krupa and engaging in the Test Team meetings, anyone can make meaningful contributions.
Whether you are a developer, tester, or someone new to open-source contribution, testing is a great gateway to get involved. Thanks to volunteers like Krupa and Makarand, the process becomes approachable and rewarding.
If you want to watch the full session, you can find the video on YouTube: WordPress TestiContribution series 10 : Contributing #WordPress Test Team by Krupa Nandang Team Contribution Guide.
Feel free to dive in and start contributing to WordPress core testing today!
