Test Chat Summary: March 12, 2025

On Wednesday 12 March 2025 at 21:30 GMT+5:30, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance

@Krupajnanda, @oglekler, @sirlouen, @vgnavada, @kausaralm, @shiponkarmakar, @pavanpatil1, @narenin, @nikunj8866, @pmbaldha, @mukesh27

2. Looking for Volunteers

  • @vgnavada volunteered to take notes on this meeting.

3. Announcements

  • Call for testing post is out. Please help test WordPress 6.8
  • Beta 2 release of WordPress 6.8 is now available for testing.
  • The BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3 release of WordPress 6.8 is scheduled for next Tuesday, March 18th. Please check the detailed overview of the release schedule for WordPress 6.8.  Don’t miss the Release Party in #core to test and provide feedback! :dart:
  • 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/ 20.4 was released on Wednesday, March 5th. Check out the milestone for the issues that were part of the 0.4 release.

4. Test Team Updates

5. Focal Group Updates

  • We are in the 6.8 release cycle and only 2 weeks from our first RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. release.
  • Check out what to expect in the WordPress 6.8 release: Roadmap to 6.8

6. Questions/Blockers

@sirlouen questioned about the testing suggestions doc: https://docs.google.com/document/d/1Q7Kzs-78XvrAjnjG_MhBJR6bSBk80rvzwnV90iYTjhg/edit?tab=t.0

7. Call for testers/visibility

8. Open Floor

The discussion started with an invitation for participants to share thoughts or raise topics for discussion. New contributors were directed to the bookmarks folder in the channel for helpful resources.

Key Points Discussed:

  1. Addressing Ethical Practices in Testing:
    • @vgnavada: Highlighted the issue of copying someone else’s test case, including the exact screenshot and text copy, and presenting it as their own, pointing out the unethical nature of this practice.
    • @sirlouen: Stated that the other user likely reused the same steps to confirm the patch without taking the time to do the work again from scratch. He described this as poor testing practice, as it would have been better to try different approaches to expand the testing cases.
    • @oglekler: Acknowledged that such issues hadn’t been caught before but noted that it should be looked into now. While copying someone else’s work is demotivating, She reassured that it wouldn’t benefit the person doing it and advised not to worry too much about it.
    • @krupajnanda: Expressed understanding of the concern and emphasized that copying someone else’s work, especially when it involves significant effort, is not the right way to contribute. She suggested that more eyes should be on each ticket to offer different perspectives and solutions.

  2. Bridging the Gap: Improving Collaboration Between QA and Development Teams
    • Challenges Identified: @sirlouen mentioned the often it observed that patches get approved with minimal verification, which can lead to unexpected issues down the line. When tickets don’t clearly outline use cases, it can slow down testing and create confusion. We need a clear mechanism for this situation to be resolved.
    • Proposed Solutions: Introduce a needs-use-cases tag to ensure clear reporting and smoother testing to encourage detailed testing reports and context from committers.
    • Next Steps: @mukesh27 supported the ideas and suggested a blog post to drive awareness and change.

9. Next Meeting 

10. Closing Remarks

The meeting wrapped up with a reminder to participants that discussions and questions are always welcome in the Test Team channel. The community is encouraged to continue contributing and collaborating outside of scheduled meetings.

  • @krupajnanda thanked @sirlouen for their feedback and assured them that the team would work on resolving the gaps identified. She acknowledged the active participation of the team during the meeting and emphasized that team members can raise questions or start discussions anytime in the Test Team channel.

Takeaways

The main takeaway is that better teamwork, clear communication, and accountability between QA and development teams are key to success. When both sides work together with honesty, transparency, and shared responsibility, things run more smoothly and lead to better results.

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#core-test, #summaries

Test Chat Summary: 12th February 2025

On Wednesday, February 12, 2025, at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@krupajnanda, @nazmul111, @kausaralm, @huzaifaalmesbah, @shiponkarmakar, @sumitbagthariya16, @oglekler, @pavanpatil1, @lumiblog and @narenin (async).

2. Looking for Volunteer

  • February 26: Test Chat Meeting Facilitator: Volunteer Needed 
  • February 26: Test Chat Meeting Recap Notes: Volunteer Needed

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

  • We are in the WordPress 6.8 release cycle and only a few weeks away from the BetaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. release.
  • Check what to expect in WordPress 6.8 release: Roadmap to 6.8

6. Questions/Blockers

No questions/blockers were reported by the members.

7. Call for Testers/Visibility

8. Open Floor

Will you be joining us on the Contributors Day at WCAsia 2025? Remote/In-person? Tell us in this thread.

9. Next Meeting 🗓

The next meeting will be on Wednesday, February 12, 2025, at 07:00 PM GMT+3, held on #core-test!

#meeting-notes

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#summaries

Test Chat Summary: 29th January 2025

On Wednesday, January 29, 2025, at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@krupajnanda, @huzaifaalmesbah, @oglekler, @kausaralm, @sumitbagthariya16, @narenin, @dhruvang21, @pavanpatil1, and @lumiblog

2. Looking for Volunteer

  • February 12: Test Chat Meeting Facilitator – Volunteer Needed 
  • February 12: Test Chat Meeting Recap Notes – Volunteer Needed
  • Remote Table leads for WCAsia. Please check this guide for more details on what to expect as a Test Table Lead.
  • A volunteer to work on Call for testing WordPress 6.8 release. For more details, check out the guide: How to Facilitate a Call for Testing

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

The members reported no updates.

6. Questions/Blockers

No questions/blockers were reported by the members.

7. Open Floor

There was no issue to discuss. 

8. Next Meeting 🗓

The next meeting will be on Wednesday, February 12, 2025, at 07:00 PM GMT+3, held on #core-test!

#meeting-notes

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#summaries

Test Chat Summary: December 18, 2024

On Wednesday, December 18, 2024, at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance

@krupajnanda, @n8finch, @mayanktripathi32, @lumiblog, @mobarak, @hage, @oglekler, @shanemuir, @narenin, @sirlouen, @patrickl, and Narendra Sishodiya

2. Looking for Volunteers

3. Announcements 📣

  • WordCamp Asia 2025 Contributor Day: The Test Team is seeking leads for the Contributor Day table at WordCamp Asia, which will take place on February 20, 2025. Please express interest in the thread if you plan to attend WCAsia in person or can assist remotely.
  • WordPress 6.7.2:  No release date is currently planned for WordPress 6.7.2. Please review the next minor releaseMinor Release A set of releases or versions having the same minor version number may be collectively referred to as .x , for example version 5.2.x to refer to versions 5.2, 5.2.1, 5.2.3, and all other versions in the 5.2 (five dot two) branch of that software. Minor Releases often make improvements to existing features and functionality. milestone for 6.7.2 and check the associated tickets for ways to contribute.
  • WordPress 6.8 Release Cycle:  The team is currently working on the WordPress 6.8 release cycle.
  • Proposals for Major Releases in 2025:  A proposal for 2025 has been drafted. Review the post for more details.
  • Write Books With the Block Editor:  We are currently discussing how to use the 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. editor to write books.
  • State of the Word 2024: The State of the WordState of the Word This is the annual report given by Matt Mullenweg, founder of WordPress at WordCamp US. It looks at what we’ve done, what we’re doing, and the future of WordPress. https://wordpress.tv/tag/state-of-the-word/. 2024 session focuses on Legacy, Innovation, and Community.

4. Test Team Updates

5. Focal Group Updates

No updates were reported during the Meeting.

6. Questions/Blockers

The members reported no blockers or questions.

7. Open Floor

The discussion started with an invitation for participants to share thoughts or raise topics for discussion. New contributors were directed to the bookmarks folder in the channel for helpful resources.

Key Points Discussed:

  1. Improving Test Results Trustworthiness:
    • @OGlekler raised the need to enhance trust in test results, suggesting that test case coverage be included as proof in reports.
    • @krupajnanda agreed and emphasized the importance of detailing scenarios covered in testing fixes/PRs to reduce regression risks and improve clarity on the scope of fixes.
    • @OGlekler shared an example from a workplace discussion, noting the value of systematic reporting and documenting test cases.
  2. Forum for Brainstorming Ideas:
    • @SirLouen proposed having a persistent space, like a forum or blog post, to brainstorm and collect broader feedback on such topics.
    • The group agreed that creating a collaborative Google Doc to collect ideas and present the issue without initial bias could be effective.
  3. Next Steps:
    • @krupajnanda committed to sharing a collaborative Google Doc link for feedback collection.
    • The group agreed to publish a finalized document on the team blog and invite input from other teams and contributors.

Resources:

The open floor concluded with a call for participants to contribute their ideas, ensuring diverse perspectives are incorporated.

8. Next Meeting 🗓

9. Closing Remarks

The meeting wrapped up with a reminder to participants that discussions and questions are always welcome in the Test Team channel. The community was encouraged to continue contributing and collaborating outside of scheduled meetings.

Highlights:

  • @krupajnanda thanked everyone for their participation and emphasized the community spirit of Test Team contributors.
  • @OGlekler extended gratitude to the team, wishing everyone a great end to the year and an inspiring start to 2025.

Takeaways

  • Keep engaging in discussions within the channel.
  • Use this time of year to reflect, recharge, and prepare for exciting contributions in the new year.
  • Remember to bring family and friends into the WordPress journey!

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#core-test, #meeting-notes, #summaries

Test Chat Summary: 4th December 2024

On Wednesday, December 4, 2024, at 07:00 PM GMT+3, <test-chat> started in #core-test facilitated by @krupajnanda. The agenda can be found here.

1. Attendance 

@krupajnanda, @noruzzaman, @sainathpoojary, @ankitkumarshah, @sarthaknagoshe2002, @oglekler, @mayanktripathi32, @shanemuir, @sirlouen, @narenin (async), @lumiblog (async), and @hage

2. Looking for Volunteer

  • December 11: Test Triage Facilitator: Volunteers Needed
  • December 18: Test Chat Meeting Facilitator: Volunteers Needed 
  • December 18: Test Chat Meeting Recap Notes: Volunteers Needed

3. Announcements 📣

4. Test Team Updates

5. Focal Group Updates

The members reported no updates.

6. Questions/Blockers

No questions/blockers were reported by the members.

7. Open Floor

@sirlouen mentioned that he had been thinking about testing reports after following several conversations in TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/.. He expressed curiosity about the extent to which developers appreciate such reports, noting that he had observed developers re-testing and commenting on information that was already clear in the reports.

@oglekler suggested that sometimes the reports might lack sufficient information and proposed that improvements could be made by ensuring all possible test cases are accounted for and explicitly checked.

@sirlouen wondered if they should inquire what information developers find useful or if the reports might be too convoluted, leading developers to disregard them.

@krupajnanda added that it would be important to observe if this pattern was specific to certain tickets owned by the same developer or spread across different developers. If so, improvements to the parameters shared in the reports would be necessary.

@sirlouen concluded by stating that he would monitor and log these occurrences over time to gather precise information, acknowledging that this behaviour might only apply to a few developers and that he wasn’t following all categories of reports.

8. Next Meeting 🗓

The next meeting will be on Wednesday, December 18, 2024, at 07:00 PM GMT+3, held on #core-test!

#meeting-notes

Thank you, @krupajnanda, for the peer review and for helping me write this post. 

Are you interested in helping write Test chat summaries like this one? Volunteer at the start of the next <test-chat> and earn some props!

#summaries

5.9 End-to-End (e2e) Strategy Session Summary

A working session was held today to discuss big picture goals and what to accomplish during the 5.9 cycle.

Where e2e tests live: 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/ vs. CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

Consensus reached as to where e2e tests will live within each repository:

  • Core: non-Gutenberg features, UIs, and UXUX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. including:
    • new stuff being built during a release cycle
    • existing interfaces such as CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings., login, 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 and theme installation/activation, interaction with list tables, settings page, etc.
  • Gutenberg: its functionality being built within its repository

5.9 Core e2e focus areas

All recent major changes to Core with user facing functionalities are top priorities to receive e2e tests as part of WordPress 5.9. These areas are:

  • The application passwords feature
  • The uploading of new versions of plugins/themes feature
  • The plugin dependency project
  • The updater project
  • Twenty Twenty-Two theme

Porting tests from Gutenberg to Core

tl;dr:

  • Tests that test Gutenberg’s functionality will remain in its repository and not be ported to Core
  • Core specific tests (such as login) can be moved to Core

Along with the previous areas to test, the following priority would be to port some Core tests that are currently implemented in Gutenberg (e2e-test-utils package). Concerned tests are those related to the login feature.

The next step after this would be to improve the login tests to make them more performant. This includes for instance cookie based authentication across all tests in Core and Gutenberg.

Other Roadmap Items

These items are not necessarily part of 5.9 Goals. However, these are part of the bigger picture Test Roadmap.

  • Documentation: The goal is to help contributors quickly contribute to testing.
    • Test Handbook: Clearly document multiple workflows for folks to pick their onramp into testing
    • README: #53550 get its PR reviewed and merged
  • Visual Regression: #49606 is an experiment to allow local vision regression testing.
    • From these learnings, plans can be crafted for how to build it into an automated CI process.
    • The challenges for the CI are storage of the artifacts and unreliability of testing these across different environments. A third party service may be possibility to explore in the future.
  • Is Core a good experimental sandbox for Playwright?

Proposal to migrate to Playwright for e2e tests

tl;dr:

  • Not a blocker to build Core’s e2e tests
  • Requires changes in e2e-test-utils package (maintained by Gutenberg)
  • Needs a migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. plan

All agreed Playwright for e2e tests would indeed have a lot of advantages for both Core and Gutenberg. However, consideration must be given for breaking changes and impacts for extenders using the test utils. Kai noted the utils could be made compatible with both Puppeteer and Playwright, meaning no breaking changes.

Also, a migration plan will need to be discussed on developed once the test utils are ready for Playwright. Part of this plan is to figure out how to change Gutenberg and Core as well as how to upgrade existing, not yet committed patches/PRs. The how and when is yet to be determined.

As there is still work to do to prepare for Playwright, the team agreed to continue with the roadmap to build e2e tests in Core.

Props @hellofromTonya for peer review and proofreading.

#build-test-tools, #core-test, #summaries

Test Team Chat Summary: 20 July 2021

The meeting took place here in Slack. @hellofromtonya facilitated.

Discussion: Team Reps

Discussion starts here in Slack.

  • @lucatume asked “Who is this call open to?” Answer: all Test Team members
  • @lucatume asked “What are the responsibilities?” Answer: mostly administrative reporting duties including:
    • Gathering feedback and then writing the agenda for the biweekly team chat (example)
    • Facilitating test triage (example) and team chat (example)
    • Writing regular team recaps and posting them in Updates
    • Keeping an eye on the moving parts of the team to be able to report for quarterly updates (example)
  • Team discussed qualifications and refined them to be:

A rep is an active team member who is reliable and trusted, advocates for and is knowledgeable of one or more areas of testing, and wants to represent, nurture, and grow the team to serve the WordPress project.

Action: @hellofromtonya to publish Call for Nominations once peer review is complete. Done.

Update: Here’s the post: Test Team Reps: Call for Nominations.

Discussion: Team and Contributor Badges

Discussion starts here in Slack.

  • Reference: FSE Outreach Program badges proposal
  • Team discussed and agreed to use CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. Team’s model for awarding Test Contributor badge: 1 contribution = a badge
  • What is a test contribution?
    • @lucatume suggested to first define what is not a test contribution?
    • Do Release Party and Contributor Days participation count?
    • @hellofromtonya noted:

Broadly testing entire release is hard to capture the feedback. Right? But testing something that has a ticket or Call for Test (CfT) is trackable for not only testers but the Core folks who are working on that thing under test. Sharing how you tested (the test environment, theme, plugins, etc.), steps you did, results, and maybe even a screenshare …. this type of info is valuable.

Commenting: “It works” is not as valuable as a feedback.

Action: @hellofromtonya will start a proposal for discussion:

laying out some guidelines for how testing is captured, what testing is not, and then that will guide everyone to know what a testing contribution is and isn’t.

Update: Autogenerate e2e Tests Initiative

Discussion starts here in Slack.

#build-test-tools, #meeting-notes, #summaries

Test Team Chat Summary: 13 July 2021

The meeting took place here in Slack. @hellofromtonya facilitated.

This was the team’s first team chat in a year or more.

Discussion: What’s the team’s purpose?

@lucatume asked “what’s the purpose of the group?” Great question!

A healthy discussion happened around the history of the team and what role we serve in the project. The discussion starts here in the slack thread.

Some highlights are captured here:

  • Tonya shared the team’s history:
    • “The team is deeply rooted in validating and surfacing issues with user experience and usability. That’s where it started and lived in the space of testing workflows, screens, results, etc. through manual testing with users. Over the years, more and more testing has come to WordPress in the form of automated tests.”
    • “rebooting it [the team] to be all things QA and testing including triage, education, outreach, documentation, and expanding to multi-dimensional testing (automated testing, manual testing, usability – user – testing, and environment testing).”
  • Charter statement:
    • Tonya then shared “we as a team can formulate the actual charter statement. But here’s what I’m thinking (open to discussion):
    • “to create a high quality feedback loopLoop The Loop is PHP code used by WordPress to display posts. Using The Loop, WordPress processes each post to be displayed on the current page, and formats it according to how it matches specified criteria within The Loop tags. Any HTML or PHP code in the Loop will be processed on each post. https://codex.wordpress.org/The_Loop. into the project to continuously improve and elevate the quality and usability of WordPress”
  • Is the charter statement too generic?
    • @lucatume raised that it felt too generic as the terms “quality” and usability can different meanings.
    • @boniu91 shared “I think they need to be some kind of generic. We’re looking at WordPress from many different angles and point of views while testing.”

Action Item: Tonya to publish a vision of the team’s big picture of how the team can serve the project.

Discussion: Why did the team go dormant?

@lucatume asked why the team went dormant. The slack thread starts here.

Some of the reasons given include:

  • Testing and quality know-how
  • Interest in driving the team
  • Clear path for how QA and testing can serve the project

Discussion: autogenerating e2e tests

@lucatume raised a discussion about how to autogenerate e2e tests from written step-by-step processes or recording the actual testing process. The slack thread starts here.

The team agreed this is a great idea to help anyone contribute to testing.

Action item: @lucatume will work with @justinahinon and others to identify an auto-generator tool.

#build-test-tools, #meeting-notes, #summaries

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. https://www.php.net/manual/en/preface.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