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.
If you’d like to help test Full Site Editing, please join the FSE Outreach Program. You can find current calls for testing for this program here and you can join the fun in #fse-outreach-experiment.
Here is the agenda for the upcoming Test Team meeting scheduled for 2021-06-08 13:00.
This meeting is held in the #core-test channel in the Making 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/..
The following posts are calls for testing (CfT):
Do you have something to propose for the agenda? Please leave a comment below.
Can’t make the meeting? Share anything relevant for the discussion in a comment below.
The following is a summary of the bi-weekly Test Team triage meeting that occurred on 2021-06-01 13:00. A full transcript can be found here in the #core-test channel in the Make WordPress Slack. Meeting was moderated by @hellofromtonya.
Triage meetings are held every other Tuesday at 13:00 UTC. Reference to triage meetings announcement.
Following links were shared:
@hellofromtonya shared tickets #34012 and #16773 are scheduled for testing.
@francina shared that she didn’t work on #39827 but it’s still in her queue. @boniu91 to send a copy of the premium 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 license for testing.
<!--more--> is still relevant@francina and @justinahinon raised creating a P2 to announce adoption of Jest + Puppeteer as the e2e setup for Core and need for handbook updates. This is a follow-up to a previous P2 by @francina.
Action: Create a draft for team review
@francina raised suggestion to restart the team’s meetings.
Team agreed to do these meetings same day and time but on alternating Tuesdays starting next week.
Action: @hellofromtonya to add to meetings calendar. Done ✅
Action: @hellofromtonya to gather topics from team and create agenda for 1st team meeting
The following is a summary of the bi-weekly Test Team triage meeting that occurred on 2021-05-28 13:00. A full transcript can be found here in the #core-test channel in the Make WordPress Slack. Meeting was moderated by @hellofromtonya.
Triage meetings are held every other Tuesday at 13:00 UTC. Reference to triage meetings announcement.
Following links were shared:
Started triage session using this ticket query report. During the meeting, this report was refined to this report.
needs-testing-info keyword. Done ✅Trac link https://core.trac.wordpress.org/ticket/50924
needs-testing keyword be removed?dev-feedback keywordThe following is a summary of the bi-weekly Test Team triage meeting that occurred on 2021-05-04 13:00. A full transcript can be found here in the #core-test channel in the Make WordPress Slack. Meeting was moderated by @hellofromtonya.
Triage meetings are held every other Tuesday at 13:00 UTC. Reference to triage meetings announcement.
Team planned to triage each 5.8 ticket marked as needs testing to determine if:
Once the session started, shifted to discuss keywords and workflows for collective understanding.
Started reviewing ticket 37255 which has these testing keywords:
has-patch means it has code to be testedneeds-testing indicates a call for manual testing needs-testing-info means it needs step-by-step instructions of how to test it. Here’s where the comment asking for those instructions.This ticket is not in a testable state. Team decided to discuss the meaning and usage of the keywords as well as how this team will know when it’s ready to be tested.
Discussed needs-testing keyword:
needs-testing keyword should be removed until all the testing details are added. has-testing-info requirement.Discussed workflow to know when a ticket is ready for Test Team action:
ready-to-testhas-patch needs-testing has-testing-info.Team decisions:
@hellofromtonya shared the needs-testing-info script she used during 5.6 @hellofromtonya shared the needs-testing-info script she used during 5.6 and 5.7 cycles:
Please provide need more information to help testers manually test the patch (including at Test Scrubs):
– What are the steps to test?
– Are there any testing dependencies, such as a 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 or script?
– What is the expected behavior after applying the patch?
Team briefly discussed. Ran out of time.
Meeting went past the planned hour. @hellofromtonya wrapped up by encouraging further async discussion and Q&A.
Thanks to everyone who attended!
Last week, the Test Team agreed to do bi-weekly test triage sessions. These meetings will happen every other Tuesday at 13:00 UTC (starting this week).
Next test triage meeting will be held on 2021-05-04 13:00 in the #core-test on 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/.. Come join to triage with the team.
The meetings are now in the calendar.
In context of bug repositories such as 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 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/, triage means sorting, labeling, and closing duplicate incoming issues and testing means manually testing bug reports, questions, and feature requests.
Triage & Testing Issues in Test Team’s handbook
The goals are:
There are multiple “testable” states in a ticket’s lifecycle including these (keyword shown in parentheses):
has-testing-info)has-patch)needs-testing)has-testing-info)has-patch)needs-unit-tests)has-testing-info)Props to @francina for peer review.
This is a summary of a Hallway Hangout that was wrangled in the #fse-outreach-experiment channel as part of the FSE Outreach Program. Thank you to everyone who joined in! If you’re keen to join an effort like this in the future, please join the 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/. channel.
Attendance: @mkaz @annezazu @sabrinazeidan
Video Recording:
Topics Covered:
Next Steps:
@annezazu found a small bug with the navigation block where changing global styles typography changes the typography of the placeholder text and will report it!
The Test Team gathered at the table for 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/. at WCUS 2019. We talked about the various ways people can test and where to go to test things out. After this, we split into groups and wrote usability testing scripts. Once scripts were written, we took some time to install a local WordPress setup and began testing 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/ issues labeled with needs-testing.
@dll416, @suziwilson, @dickmoomaw, Allie Brock, @brezocordero, @chrisp, @c3zh, @christopher-pollock, @royho, @mapk, @jg-visual
These scripts will be used in future usability testing scenarios that help inform the design and development direction in Gutenberg.
Thank you, everyone, for your wonderful contributions today! Keep testing all the things!
Here’s the agenda for Tuesday’s NUX working group chat in the #core-flow channel on Slack.
This is the sixth weekly chat for the 4.2 NUX working group. Just as a reminder, group discussions are open to anyone who would like to attend and participate. So please, join us!
Time/Date: Tuesday March 17 2015 19:00 UTC
DST Reminder:The Time/Date link above should display the correct time for you, whether you’re in DST or not. If you’re in Daylight Saving Time, the meeting will be an hour later than usual for you until March 31st.
Chat Leader: @DrewAPicture
Topic: Reviewing Welcome Panel 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.Flow is the actual user experience, in many ways. If you like, you can think of flow as a really comprehensive set of user stories. When you think about user flow, you’re thinking about exactly how a user will perform the tasks allowed by your product.Flow and Context
reports
Here’s the agenda for Tuesday’s NUX working group chat in the #core-flow channel on Slack.
This is the fifth weekly chat for the 4.2 NUX working group. Just as a reminder, group discussions are open to anyone who would like to attend and participate. So please, join us!
Time/Date: Tuesday March 10 2015 19:00 UTC
DST Reminder: If you changed over to Daylight Saving Time over the weekend, the NUX chat will be an hour later for you, though still 19:00 UTC.
Chat Leaders: @DrewAPicture
Topic: Working Meeting: Examining Welcome Panel Flows
Flow is the actual user experience, in many ways. If you like, you can think of flow as a really comprehensive set of user stories. When you think about user flow, you’re thinking about exactly how a user will perform the tasks allowed by your product.Flow and Context, check out the recap posted over the weekend and leave a comment with the flow you’d like to work on.
Here’s the agenda for today’s NUX working group chat in the #core-flow channel on Slack.
This is the fourth weekly chat for the 4.2 NUX working group. Just as a reminder, group discussions are open to anyone who would like to attend and participate. So please, join us!
Time/Date: Tuesday March 3 2015 19:00 UTC
Chat Leaders: @DrewAPicture
Topic: Welcome Panel: Narrowing Focus (continued)
Flow is the actual user experience, in many ways. If you like, you can think of flow as a really comprehensive set of user stories. When you think about user flow, you’re thinking about exactly how a user will perform the tasks allowed by your product.Flow and Contextand identify several things:
