The Test Team helps manage testing and triage across the WordPress ecosystem. They focus on user testing of the editing experience and WordPress dashboard, replicating and documenting bug reports, and supporting a culture of review and triage across the project.
Meeting started by explaining Note takers and Facilitators so people can take up the roles.
Note takers are simply people who summarize the happening of the Test Chat and they always publish a test Chat summary like this one here.
Facilitators are simply people that chair or facilitate a test team chat. These follow the agenda that is proposed and ensure that every one gets a voice. A sample Meeting is like the one held here.
These 2 can be done by the same person in the same instant however we encourage multiple people to do it to increase on the proof reading and collaboration
Update on Test Handbook: New pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92) are available; contributors can update content via GitHubGitHubGitHub 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/ issues.
@sirlouen got to a conclusion that currently we don’t have enough resources to have the wheel moving
all the areas mentioned above require a good thought and a suggestion to expand the team was brought up.
Previously, mentorship was insufficient so now a full training was advised. A program in the test team that will bring in Champions
A call for as many people as possible was made. People that will be committed to the program and see it through
@nikunj8866 sighted it as a great learning opportunity for anyone who wants to become a future Test Team representative.
@sirlouen added that it won’t only make team reps but also Power Members.
@sirlouen will pause current Handbook activity in preparation for the program in the next 2 weeks. Announcement made here highlighting the requirements to join and all the information about the program.
We usually have 2 meetings held every week. This is the last test-chat meeting for this year and Tomorrow’s patch testing session will be the last for this year.
Hello and welcome to another edition of Week 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:
Merging of Test Handbook in GithubGitHubGitHub 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/
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
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 CoreCoreCore 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:
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 (204) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, the provide a bug reproduction report:
Update on Test Handbook: New pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92) are available; contributors can update content via GitHub issues.
The following tickets (0) 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.
Nothing this week
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 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:
None this week
Profile Badge Awards 🎉
Congratulations to the recipients of the Test Contributor Badge 🎉
Note-taker and facilitator selection for the next meeting We encourage all members to contribute to the team chat, and we now welcome Note Takers and Facilitators. This is a great time to get involved in the coreCoreCore is the set of software required to run WordPress. The Core Development Team builds WordPress. test team. Have you recently joined, and you don’t know where to go? Start here (No Skills Required)
Update on Test Handbook: New pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92) are available; contributors can update content via GitHubGitHubGitHub 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/ issues.
Open Floor
Got a topic? Add in comments below, or bring it up live during the chat.
Hello and welcome to another edition of Week 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:
Merging of Test Handbook in GithubGitHubGitHub 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/
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
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 CoreCoreCore 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:
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 (205) have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, the provide a bug reproduction report:
Update on Test Handbook: New pages for Feature & Enhancement Testing (#90), E2E Testing (#91), and Patch Testing Scrubs (#92) are available; contributors can update content via GitHub issues.
The following tickets (1) 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.
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:
Hello and welcome to another edition of Week 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:
Collaboration: add blockBlockBlock 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.-level comments:
Merging of Test Handbook in GithubGitHubGitHub 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/
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
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 CoreCoreCore 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 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:
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 have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, the provide a bug reproduction report:
The following tickets (13) 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.
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:
Nothing to test yet this week
Profile Badge Awards 🎉
Congratulations to the recipients of the Test Contributor Badge 🎉 @fakhriaz – Kindly find the Contribution Guidelines here
Hello and welcome to another edition of Week 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:
Collaboration: add blockBlockBlock 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.-level comments:
Merging of Test Handbook in GithubGitHubGitHub 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/
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
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 CoreCoreCore 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 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:
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 have been reviewed and milestoned, and need testers to check the instructions and manually test if the issue is reproducible, the provide a bug reproduction report:
The following tickets 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.
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:
Nothing to test yet this week
Profile Badge Awards 🎉
Congratulations to the recipients of the Test Contributor Badge 🎉 None this week. Please keep contributing. – Kindly find the Contribution Guidelines here
if you are going to be doing the testing report.
You must be logged in to post a comment.