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

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 it’s 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

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