WordPress.org

Weekly Meetings (Calendar)

Bi-Weekly Test Team Chat: Tuesdays 11:00 UTC

Bi-Weekly Test Team Triage: Tuesdays 11:00 UTC

You can join these meetings from the #core-test Slack channel.

Please drop by any time 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/. with questions or to help out.

In the Test Team, we are planning to create a handbook page to provide criteria for earning the Test Team Badge. After discussions, we have finalized the criteria listed below to earn the Test Team Badge. There are a few recommendations that we should consider before incorporating them into the handbook.

If you would like a badge on 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 that acknowledges your contributions to the Test Team, the following criteria must be met:

Test Contributor Badge

To earn a Test Contributor Badge, you must have completed at least one of the following:

Submitted a test report comprising at least 3 tickets for testing instructions, issue reproduction, or patch testing either on WordPress or 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/. Please note that reports can be submitted, whether it’s on TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. or 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 be the repository owner. https://github.com/.
Reported an issue on Core Trac or the Gutenberg GitHub repo which has been fixed and merged into a WordPress release.
Submitted unit or end-to-end tests that have been merged.
Contributed to a Test handbook PR that has been merged.
Participated in ZIP package builds or default theme tests during a #core <release-party>.
Participated in a Contributor DayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. (as a table lead, providing technical support, or assisting with onboarding).
Suggested a thoughtful idea aimed at improving testing processes in any way, which gets implemented.

Test Team Badge

If you have served as a Test 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. or Test Lead in any 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. of WordPress, you are eligible for the Test Team badge.

How to Request a Test Team Badge?

If you meet the criteria mentioned above, you can request a badge using this link. You will have to include details that demonstrate you have met the criteria mentioned above.

Upon request, a Test Team Rep will confirm your contribution(s) and assign you a badge. There will be a monthly review of contributions, and badges will be awarded at that time. The Test Team will post updates on newly awarded profile badges on the Test Team blog.

Call for feedback.

What do you think of the suggested criteria? Please leave your thoughts on this post by Friday, 22 March 2024.

Tapan Kumer Das 6:10 pm on March 9, 2024

Well, that’s a clear guideline. I think this will help new contributors. 🙂
ironprogrammer 10:41 pm on March 11, 2024

Thank you for putting this together, @ankit-k-gupta and @webtechpooja!

Submitted a test report comprising at least 3 tickets…

It would be nice to have more feedback on the suggestion to increase the number of qualifying test reports from one (1) to three (3). Personally, I have mixed feelings about this. I would like to encourage repeat contributions, but consider that a single props on a fixed TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket qualifies as a CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. contribution. Submitting a detailed reproduction or patch report seems that it should qualify here. I also want to note that in addition to WordPress/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/, test contributions should be acceptable for other projects the Test Team touches.

Reported an issue on Core Trac or the Gutenberg 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 be the repository owner. https://github.com/ repo…

Taking the time to report an issue in Trac or GitHub is very valuable to the project, and reporters should be applauded. However, I question whether this should automatically qualify for a Test badge, even if patched/merged. It may be difficult to differentiate between a report based on a user’s testing activity, versus noticing something wasn’t right and filing the issue without details/context (or possibly submitting a duplicate issue).

If this is accepted as a qualifying criterion, then perhaps we could include a stipulation that detailed testing instructions be provided in the report, to make it easier for subsequent testing. Additionally, if the count of qualifying test reports increases (first bullet), then I feel the count of submitted tickets should mirror that minimum for parity.

If you have served as a Test 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. or Test Lead in any 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. of WordPress…

For the Test Team badge, I believe that Test contributors who have consistently provided positive impacts to the team should also be eligible. This would allow for recognition of folks who have been highly active in the team, or demonstrated leadership in one or more Test areas, even if they have not served as rep or release leadRelease Lead The community member ultimately responsible for the Release.. Eligibility doesn’t mean automatic assignment; such nominations could be reviewed by current team members and discussed during team chat.
Olga Gleckler 1:47 pm on March 26, 2024

I think ‘Participated in ZIP package builds’ is not enough to get a tester’s badge. Possibly, badges for parties needs to be eliminated; there are props for this. It will be great if there is a way to give badges for testing automatically based on test reports on tickets with commits.
Ankit K Gupta 5:16 am on April 25, 2024

Thanks for your insight, @ironprogrammer and @oglekler. Your suggestions have been addressed, and the handbook page is now live.
FahimMurshed 9:27 am on April 25, 2024

Thank you for sharing this post. I’m eager to join the Test team and contribute. While I’m enthusiastic about contributing, I would greatly appreciate it if there were any video tutorials available to aid in my understanding.

Welcome

Weekly Meetings (Calendar)

Test Team Profile Badge – Your Feedback Needed!

Test Contributor Badge

Test Team Badge

How to Request a Test Team Badge?

Call for feedback.

Welcome

Weekly Meetings (Calendar)

Test Contributor Badge

Test Team Badge

How to Request a Test Team Badge?

Call for feedback.

Share this: