Test Team Meeting Agenda for June 8, 2021

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

Blog Posts

The following posts are calls for testing (CfT):

Agenda

  • Test Badges Proposal: currently scoped for the FSE Outreach Program. Topics:
    • Does it apply for only this outreach program?
    • Should the Test Team have a team badge program for all testing activities including outreach call for testing programs? Or should each program have its own criteria and process?
    • Open discussion on the proposal
  • State of the Test Handbook
  • e2e setup with Jest + Puppeteer
  • Open floor

Open Floor

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.

#agenda

Test Team triage meeting summary – June 1, 2021

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.

Announcements

Following links were shared:

Review of Action Items

@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.

Ticket Triage

Ticket #13822

  • Status: ready for testing but may be impacted by new nav 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. feature
  • Action: park this ticket and will reassess once new nav block feature is ready

Ticket #39589

  • Status: needs testing to reproduce issue with current WP version
  • Action: @boniu91 will test. Done
  • Followup: @boniu91 tested and found still an issue

Ticket #39603

  • Status: likely needs refresh, unit tests need improvement, needs performance testing
  • Action: @hellofromtonya will take this one

Ticket #31354

  • Status: not ready for testing as discussion ongoing (though stalled out)
  • Action: none

Ticket #12104

  • Status: needs a refresh and may need unit tests
  • Action: @hellofromtonya to comment on ticket. Done

Ticket #30499

  • Status: not ready for testing as discussion ongoing
  • Action: none

Ticket #25349

  • Status: needs testing but may not relevant today
  • Action: check if <!--more--> is still relevant

Ticket #40006

  • Status: skip as it’s awaiting review
  • Action: none

Ticket #37674

  • Status: skip as it’s a close candidate
  • Action: @desrosj will close the ticket. Done

Ticket #12104

  • Status: needs a refresh and may need unit tests
  • Action: @hellofromtonya to comment on ticket. Done

Ticket #31798

  • Status: needs consideration against the block editor and may not be applicable today ??
  • Action: none

Ticket #11477

  • Status: close candidate but followup items need tickets
  • Action: @francina taking this ticket to check if corresponding tickets were created

Ticket #40525

  • Status: needs a code review before ready for testing
  • Action: none

Open Floor

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 2e2 P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/.

@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

Restart Team Meetings

@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

#meeting-notes, #summaries

Test Team triage meeting summary – May 18, 2021

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.

Summary

Following links were shared:

Started triage session using this ticket query report. During the meeting, this report was refined to this report.

Ticket #50683

  • Status: not ready for testing as there are no testing instructions
  • Action: @boniu91 will ask for testing info and add needs-testing-info keyword. Done
  • @francina observed that the reporter has been responsive when pinged

Ticket #37110

  • Skipped as no actionable changes for 5.8 to test
  • Action: none

Ticket #50924

Trac link https://core.trac.wordpress.org/ticket/50924

  • @Daria noted that there are no “how to reproduce” instructions, steps could be determined by the team, and would want to confirm with the reporter
  • Action: @Daria will write up the instructions and then ask the reporter to confirm. Done

Ticket #50781

  • Status: not ready for testing as discussions are still ongoing
  • @boniu91 noted that the steps to reproduce are clear but that discussions are still ongoing
  • @boniu91 asked: should the needs-testing keyword be removed?
    • @hellofromtonya explained that removing it would mean losing the tracking to know the ticket will need to be tested when ready
    • Agreed to keep it
  • Action: none

Ticket #42140

  • Status: not ready for testing or testing instructions as discussions ongoing
  • How to tell? dev-feedback keyword
  • Refined query report to exclude tickets with this keyword
  • Action: none

Ticket #34012

Ticket #16773

  • Status: needs a refresh and unit tests
  • Action: @hellofromtonya took this one since its 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. http://php.net/manual/en/intro-whatis.php. version based, needs a refresh, and needs tests.
  • Update: Ticket is a duplicate and was closed.

Ticket #52050

Ticket #39827

  • Status: ready to test but …
  • @boniu91 noted it needs a 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 to test it
  • @francina asked if this is plugin territory and not coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • Action: @francina to check if they have a license to the premium plugin

#meeting-notes, #summaries

Test Team triage meeting summary – May 4, 2021

The 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.

Summary

Team planned to triage each 5.8 ticket marked as needs testing to determine if:

  • it is in a testable state
  • if yes, ask for volunteers to:
    • do the manual test
    • if needed, write automated tests.

Once the session started, shifted to discuss keywords and workflows for collective understanding.

Testing Keyword Combinations

Started reviewing ticket 37255 which has these testing keywords:

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:

  • @hellofromtonya shared:
    • currently means => “it’ll need manual human testing once it’s ready” but doesn’t necessarily mean it’s ready right now for this testing.
    • can be added at any point in a ticket’s lifecycle.
    • Core Handbook defines it as: “One or more people are needed to test the solution”, but does not indicate when the keyword should be added.
  • Discussed removing keyword until it’s ready for testing:
    • @mai21 asked if the needs-testing keyword should be removed until all the testing details are added.
    • @francina added it “should be added only when it satisfied the has-testing-info requirement.
    • @hellofromtonya wondered how we’d know if a developer or maintainer wants the ticket to be manually tested if the keyword removed until ready.

Discussed workflow to know when a ticket is ready for Test Team action:

  • Discussed if a new keyword is needed such as ready-to-test
  • @boniu91 noted that “it’s pretty easy to sort the tickets in tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. using tags” and a ticket ready to test is noted as has-patch needs-testing has-testing-info.
  • @justinahinon suggested to make a P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. post once the team agrees on how to add the tags/keywords

Team decisions:

Asking for testing info

@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.

Wrap up

Meeting went past the planned hour. @hellofromtonya wrapped up by encouraging further async discussion and Q&A.

Thanks to everyone who attended!

#meeting-notes, #summaries

Bi-Weekly Test Team Triage Meetings

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.

What is triage for the Test Team?

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:

  • to evaluate where each ticket is in its lifecycle and what the next step is to get it closer to a testable state
  • when in a testable state, to validate the patch/PR works as expected and, if applicable, provide feedback on the experience

When is a ticket in a testable state?

There are multiple “testable” states in a ticket’s lifecycle including these (keyword shown in parentheses):

  • Ready to reproduce the reported issue
  • Ready to manual test the patch
    • State:
      • has a patch (has-patch)
      • is marked for testing (needs-testing)
      • has “how to reproduce” instructions, if defect ticket
      • has “how to test” the patch instructions (has-testing-info)
    • Trac reports: with all the above states || without the testing info
  • Ready to build the automated tests
    • State:
      • has a patch (has-patch)
      • does not have automated tests (needs-unit-tests)
      • has “how to reproduce” instructions, if defect ticket
      • has “how to test” the patch instructions (has-testing-info)
    • Trac reports: with all the above states | without the testing info

Props to @francina for peer review.

Hallway Hangout: Discussion on Full Site Editing Issues/PRs/Designs (29 April)

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:

  • We kicked off the call going through the latest summary post on building a restaurant header and some of the feedback items that came up there including talking about the navigation 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., list view, and more.
  • We talked in depth about the Navigation Block, including showing a demo of the mobile responsive menu that’s in progress. This will be part of the next call for testing so stay tuned!
  • We discussed the theory behind the click through to edit pattern with template part blocks and viewed the current design/development in progress.
  • We reviewed the Enhancing select mode overview issue, talked about what Select mode is for, and touched on a few other medium sized projects.
  • List View was brought up while talking about more tools to use within the Site Editor leading to a discussion around using the persistent List View (always keeping it up) and general discoverability of the tool itself.
  • The conversation about List View led nicely into discoverability of the toolbar items themselves and this recent exploration from a designer about moving more document attributes into the top bar in the post editor to help mimic some of what’s to come in the Site Editor.
  • Finally, we plugged a few posts/docs including: the Full Site Editing Overview document in the dev handbook, the refinements to the core editor toolbar, and the latest call for questions.

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!

#fse-hallway-hangout, #fse-outreach-program, #full-site-editing

WCUS 2019 Contributor Day

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.

The team included

Test table at WCUS 2019 Contributor Day

@dll416, @suziwilson, @dickmoomaw, Allie Brock, @brezocordero, @chrisp, @c3zh, @christopher-pollock, @royho, @mapk, @jg-visual

Issues/PRs that were tested

Scripts created for usability testing

  1. Create a new post.
  2. Title the post: “Gutenberg Recipe”
  3. Add a text 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. describing the recipe:
    “This is a test recipe of a delicious pie. We love pies as they are tart and sweet at the same time.”
  4. Add a two-column block for the ingredients.
  5. In the first column, type “Crust”. Then add a bulleted list:
    • 1 ½ cup cookie crumbs
    • ¼ cup sugar
  6. In the second column, type “Curd”. Then add a bulleted list:
    • 1 (12 ounce) package of cranberries
    • 1/2 cup Sugar
    • 1 orange, zested
  7. Add a single-column block titled “Directions”
  8. In the block add a numbered list:
    1. Preheat oven to 350 degrees F. Spray a 9-inch two-piece tart pan with cooking spray.
    2. In a medium bowl, stir together cookie crumbs, sugar, stevia, salt, and butter. Press mixture evenly in bottom and up sides of tart pan. Bake until set, about 15 minutes.
    3. In a medium saucepan, combine cranberries, sugar, stevia, and orange zest and juice. Bring to a simmer over medium-high heat and cook until cranberries burst, about 8 minutes.

  1. Go to Posts->Add New
  2. Add a title to the post
  3. Click + to add a 3 columns block
  4. On the first column add a headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. block and an image block
  5. On the second column, add an image
  6. On the third column add text
  7. Resize the image on the second column to make it larger (any size)
  8. Add a fourth column by clicking the Block Navigation icon on the upper left of the editing page.
  9. Add a slideshow in the fourth column.
  10. Click Preview to see how your post appears
  11. Publish the post (private if you want)

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!

#contributors, #wcus

4.2 NUX Group Agenda, March 17, 2015

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

Welcome Screen Final from 2 24 2015 NUX meeting

  1. Last week and the week before, we sought volunteers to examine each of the flows out of the Welcome Panel.
  2. This week, we’ll go over any of the reports that came in about the various flows, check the comments on the above-linked recap post.

#4-2, #nux

4.2 NUX Group Agenda, March 10, 2015

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

  1. Last week we sought volunteers to examine each of the flows out of the Welcome Panel.
  2. This week, we’ll use the meeting time as a working meeting to continue documenting those flows. If you haven’t yet volunteered to document a 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
    , check out the recap posted over the weekend and leave a comment with the flow you’d like to work on.
  3. Next week, group members will report back with their findings and recommendations

#4-2, #nux

4.2 NUX Group Agenda, March 3, 2015

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)

  1. Last week we decided on a better list of links for three columns of the Welcome Panel: Settings, Appearance, and Content. @liljimmi was kind enough to adjust the mockups to match (see below).
  2. Welcome Screen Final from 2 24 2015 NUX meeting

  3. This week, we’ll be narrowing the focus to those individual flows. The goal would be to have at least one team member “own” each 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
    and identify several things:
    • The importance of highlighting that flow for new users in the Welcome Panel
    • What is currently good or bad, or could be improved
    • Bonus: Whether this is a “Day 1” link and if so, what should replace it?
  4. Next week, group members will report back with their findings and recommendations

#4-2, #agenda, #nux