Test Chat Summary: 15 August 2023

On 15 August 2023 at 16:00 UTC<test-chat> started in #core-test.

Announcements 📣

  • Test Team at WCUS 2023: The WCUS 2023 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/. is less than a week away! Check out this post for information, and to share your questions and thoughts.
  • Admin Design Kickoff: The Design Team share early thoughts on how WP admin could be reimagined. Join the discussion to help shape this important part of WordPress.
  • What’s new in Gutenberg 16.4? (9 August): Download and test the latest feature updates in the 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 get a peek at what the future holds for editor updates to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..
  • FSE Program Testing Call #25: Let’s start from the beginning: Get in on this latest call for testing before the feedback window closes on August 23.
  • WordPress 6.3 “Lionel”: And finally, WordPress 6.3 was released last week. When submitting bug reports, please consider the official test report guidelines, and remember that the WordPress Beta Tester plugin has a handy “Report a Bug” button that works even if you’re running the 6.3 release version 🎉.

And we received one participant-submitted announcement:

Open Floor 💬

WCUS 2023 Contributor Day

Volunteers were asked to step forward to help facilitate the Test table, both in person and remotely 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/.. @ironprogrammer volunteered to help lead in person at the event, but at the time of this writing there was no clear lead for coordinating contributors online in Slack. Contributors wishing to help are asked to comment below or raise their hand in Slack.

The remote session for Contributor Day is scheduled to begin at 2023-08-24 10:00 EDT in the #contributor-day channel. For more details, see the Test Team at WCUS 2023 post.

Test Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. Nominations

It was shared that the nomination process for the next Test Team Reps would begin soon, and team members were encouraged to help identify and nominate individuals who might be a good fit for the role (even themselves). [Ed. note: the 2023-24 call for nominations has been published.]

Next Meeting 🗓

The next scheduled meeting is on 22 August 2023 at 16:00 UTC for <test-triage> in #core-test.

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!

Props @boniu91 for peer review of this post.

#fse-outreach-experiment, #meeting-notes

Test Chat Summary: 23 May 2023

On 23 May 2023 at 16:00 UTC<test-chat> started in #core-test.

Announcements 📣

  • Core Editor Improvement: Smoother Site Editing: See some of the latest updates to the editor, including revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. history for styles, templates, and template parts.
  • WP Briefing: Episode 56: What to Know About WordPress Playground: Learn more about experiments surrounding the ever-growing WordPress Playground, and what coding and testing accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) opportunities this exciting project is making possible.
  • What’s new in Gutenberg 15.8? (May 17): Get the latest scoop on what’s recently shipped in 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/.
  • WordPress 6.2.2 Security Release: This rapid-response security release addresses a shortcodes regression from 6.2.1, and further improves security around this feature.
  • FSE Program Testing Call #23: Rapid Revamp: Follow along with this #fse-outreach-experiment to test features planned for the 6.3 release. With clear instructions on setup and what to test, both experienced and new contributors to testing will find this an interesting way to test and explore new features.

And last, but not least:

  • WordPress’s 20th Anniversary: WordPress turns 20 this Saturday, 27 May! Celebrate this historic milestone with others from around the WordPress world!

@oglekler also invited everyone to take part in the Day 15: #WP20 From Blogs to Blocks campaign.

Open Floor 💬

wp-now Package

@ironprogrammer drew attention to the recent release of wp-now (npm package), part of the WordPress Playground project. He noted that wp-now works with Node.js, and could be a possible replacement for wp-env. He gave an example of having navigated to 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 source directory and running wp-now start, which quickly launched a new WordPress site to test the plugin.

@ironprogrammer mentioned that the utility could be a fast way for contributors to get set up for testing or development, and referred to WCEU as a possible testing ground for test contributors to try it out.

@oglekler provided a link to a MeetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. event that featured Playground, occurring shortly after Test Chat.

@ironprogrammer then shared his plans to draft wp-now setup instructions to propose for addition to the Test Handbook, and asked the team to try out the utility and report any blockers or challenges they encounter.

@boniu91 asked if PRs and patches could be applied to sites running on wp-now. @ironprogrammer confirmed having tested with plugin repos, but that testing with the wordpress-develop repo would be important before recommending it for broader Test Team use.

Next Meeting 🗓

The next scheduled meeting is on 30 May 2023 at 16:00 UTC for <test-triage> in #core-test.

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!

Props @costdev for peer review of this post.

#meeting-notes

Test Chat Summary: 9 May 2023

On 9 May 2023 at 16:00 UTC<test-chat> started in #core-test.

Announcements 📣

  • WP Briefing: Episode 55: Happy Anniversary, WordPress!: Celebrating 20 years this month, take a look back on how WordPress has been shaped by its amazing open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL. community.
  • FSE Program Build a Block Theme Summary: Check out the highlights from the most recent block theme experiment.
  • WordPress 6.2.1 Planning: This 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. brings an important bugfix to 6.2. Consider taking part in testing the RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. (today) or the final release next week.
  • Let’s talk: WordPress Core & Artificial Intelligence: Have you been following recent happenings in the world of AI and LLMs? Contribute to the discussion around how these important technologies fit with the WordPress open source project.

And a reminder:

Focal Groups 🧪

E2E

@ironprogrammer highlighted that the PR to prerelease Playwright test utils — aka @wordpress/e2e-test-utils-playwright — has been merged, and is slated for release with 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/ 15.8 🎉. He noted that this facilitates inclusion of the package in other test suites, and expressed hope that it would eventually contribute toward improved E2E coverage in WordPress.

@oglekler wondered how well Playwright worked in WP admin, outside of the editor context. She referred to reports of Quick Edit rows disappearing after an update, and whether an E2E test could help identify this.

@ironprogrammer clarified that the release of the @wordpress/e2e-test-utils-playwright package was in response to several requests from community members who wished to use it, and encouraged continued exploration regarding previous discussions about Cypress.

Next Meeting 🗓

The next scheduled meeting is on 16 May 2023 at 16:00 UTC for <test-triage> in #core-test.

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!

Props @juhise for peer review of this post.

#meeting-notes

Test Chat Summary: 25 April 2023

On  25 April 2023 at 16:00 UTC <test-chat> started in #core-test.

There was no agenda preceding the chat.

Announcements 📣

Focal Groups 🧪

E2E

@ironprogrammer asked @oglekler if there was an update from the last chat’s E2E discussion, and they would follow-up later.

Open Floor 💬

@ironprogrammer invited/reminded the team to consider submitting topics and/or applying to the 2023 WordPress Community Summit, emphasizing that ideas and input from underrepresented community members is especially important to summit discussions.

Next Meeting 🗓

The next scheduled meeting is on 2 May 2023 at 16:00 UTC  for <test-triage> in #core-test.

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!

Props to @costdev for peer review of this post.

#meeting-notes

Test Chat Summary: 11 April 2023

On April 11, 2023 at 16:00 UTC <test-chat> started on #core-test.

There was no agenda preceding the chat.

Announcements 📣

Focal Groups 🧪

@ironprogrammer re-introduced this section as pertaining to Test Team discussions from 2021. Because contributorship has changed a lot since then, he asked that contributors interested in representing a particular focal group reach out to @boniu91 or @ironprogrammer (himself). He also noted that the team can adjust the focal groups to align with current needs, particularly if it would help inspire greater collaboration.

E2E

@oglekler noted their positive experience with Cypress, an open-source testing tool which uses Mocha and jQuery, and can be run headless. @ironprogrammer asked if it was compatible with the current WordPress E2E standard, Playwright, and suggested that discussion with other E2E contributors be held to discuss further.

@ironprogrammer suggested that a follow-up Make/Test post be considered to gauge interest on possible focal group rep interest, particularly for E2E.

Test Handbook

@ironprogrammer gave a brief update on the Test Handbook, noting that a new 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/. page was under final review. The page will provide new Test Team contributors a good place to start at WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. events. He encouraged contributors to share the page at future WordCamp Contributor Day events, and to raise suggestions for improvement in the #core-test channel, or to create a PR in the handbook’s official GitHub repo.

Next Meeting 🗓

The next scheduled meeting is on April 18, 2023 at 16:00 UTC  for <test-triage> in #core-test.

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!

Props to @costdev for peer review of this post.

#meeting-notes

Test Chat Summary: 28 March 2023

On March 28, 2023 at 16:00 UTC <test-chat> started on #core-test.

There was no agenda preceding the chat.

Are you interested in hosting a <test-scrub>? The Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

Announcements 📣

@ironprogrammer pointed out that the release process helps ensure that issues like the regression noted above can be identified and resolved prior to general release.

And a shout out was given to @juhise for running last week’s Test Team Triage, as well as thanks to everyone else who attended! 🎉

Open Floor 💬

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 Dependencies

@afragen requested 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. testing for the Plugin Dependencies feature plugin, noting that @azaozz was looking for “newish” user feedback for the plugin dependency activation workflow. The instructions provided by Andy included two steps: installing the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins., and then installing a separate plugin with a dependency.

@costdev and @afragen explained that providing only basic instructions might better measure how easy or difficult the workflow is to users in discovering the process organically — i.e. how to successfully install the dependent plugin without outside guidance.

@costdev outlined the feedback desired from testers, and @ironprogrammer asked where the feedback should be provided. Additional discussion along with @afragen lead to the decision to create a new call for testing post. [Editor’s Note: The CFT for the above has been posted to Make/CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..]

Next Meeting 🗓

The next scheduled meeting is on April 4, 2023 at 16:00 UTC  for <test-triage> in #core-test.

#meeting-notes

Test Chat Summary: 14 March 2023

On 14 March 2023 at 16:00 UTC , <test-chat> started on #core-test.

There was no agenda preceding the chat.

Are you interested in hosting a <test-scrub>? The Test Team needs you! Check out Leading Bug Scrubs for details, or inquire in #core-test for more info.

Announcements 📣

  • FYI: Navigation section of new Site Editor experienced removed for 6.2 RC 2 — after careful discussion, this feature has been removed from 6.2 in order to give it time to mature in the 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/ 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.
  • What’s new in Gutenberg 15.3? (13 March) — see what’s in store for the plugin!
  • WP Briefing: Episode 51: Is Routine a Rut? — Josepha discusses the utility of consistency, how it can highlight notable changes, and allow us to spend more time on the important stuff.
  • WordPress 6.2 Release Candidate Phase — as a reminder, WordPress 6.2 is in the “release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.” (RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.) phase, and Tonya helps clarify the “dos and don’ts” in this post.
  • WordPress 6.2 Field Guide — check out the 6.2 Field Guide for important development and extender updates in this release.

Open Floor 💬

@afragen called for awareness of the Rollback Update Failure and Plugin Dependencies plugins, so that they might land in 6.3-alpha. @ironprogrammer noted that both features could improve the user experience in WordPress.

@afragen also asked for testing of #53323: Place Hello Dolly in containing folder, so that this plugin follows documented best practices.

Improved Release Testing

@costdev mentioned that improved release testing has been discussed in #core, and asked if anyone had thoughts on how the number of testers might be increased during the Alpha/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./RC phases. @ironprogrammer noted that this has been suggested as a 2023 WordPress Community Summit topic, but that short term options are needed.

@costdev asserted that collaboration with MarComms (#marketing) would be key to finding ways to pull in more contributors for testing. He asked where we might extend reach/awareness, and what motivates users to become testers.

@afragen suggested that managed hosting providers, such as WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/, might facilitate RC testing by working with opt-in site owners. @costdev agreed that this would help environment testing, but that there is a lack of feature-specific testing and reporting. He asked what tools might be offered to make this easier.

“Report an Issue” Link

@costdev’s question spawned a long thread discussing ideas to simplify issue reporting for pre-release builds, the outcome of which is described below.

  • @afragen offered the WordPress Beta Tester plugin as a place to experiment with the “Report an issue” concept. [Editor’s note: This plugin currently reflects 3000+ active installs.]
  • Admin bar link: “Report an issue”.
  • On plugin activation/update, add a tooltip to the admin bar link: “Found an issue? Report it here”, to promote awareness.
  • The link leads to a new tab in Beta Tester, which displays basic — but important — environment information consistent with what is suggested for test reports, some of which has been written/tested by @costdev in a separate plugin. The information would be formatted for inclusion in a 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 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/ ticket.
  • Provided this initial scope, users would be able to copy this information for use in a new issue or reproduction report.
  • @afragen also noted updates may be needed for Apple Silicon support.

Next Meeting 🗓

The next scheduled meeting is on 21 March 2023 at 16:00 UTC for <test-triage> in #core-test.

Thank you props to @costdev for review of this post.

#meeting-notes

Field Notes from WCEU 2022 Contributor Day

Olá! We’d like to express our gratitude to everyone who stopped by the Test Team (or CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.:Test) table at this year’s WCEU Contributor Day 🙇. Your ideas, perspectives, and open discussions help foster initiatives critical to testing WordPress. Thank you to everyone who participated!

Participants at the event covered the following topics (some of which were also referred to #core-test in Slack):

Test Report Templates

  • In the proposed Test Reports guidelines, clarify how the green checkmark (✅) and red “X” (❌) emoji should be used in reports: expected vs unexpected.
  • Break out the report templates into subpages under a main “Test Report” description in the Test Handbook to improve readability.
  • Proposal to provide ticket creation templates for TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. issue reporting, similar to Gutenberg Issues (e.g for Bugs vs Enhancements).
    • @todo Investigate whether Trac supports pre-populated template options, for initial post and/or comments.

Easier Test Contributions

  • Improve/update the Test Handbook guidance for creating a local WordPress environment.
  • The desire for ephemeral test environments (no local installLocal Install A local install of WordPress is a way to create a staging environment by installing a LAMP or LEMP stack on your local computer. needed) to test PRs and patches. Some ideas:
    • Create a Core-targeted version of gutenberg.run.
      • Would need to support both PRs and individual Trac patch attachments.
    • Utilize a service similar to that used for calypso.live.
  • Add Test Handbook guidance for applying patches from GitHubGitHub GitHub 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/ or Trac, covering the various “best practice” methods.
  • Reiterate the importance of different environment flavors across the test contributor group (Docker/wp-env, VVV, Laravel Valet, Local, etc). There shouldn’t be a preference for “the best” or “one way” to run/test WordPress, since it should reflect the real-world variation across the WordPress community.
  • Assign a new week-in-test categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. to Week in Test posts, for easier filtering of “where to start” in testing (currently grouped under the more generic summary category).

End-to-End (E2E) Testing

  • Questions as to where to begin E2E testing in WordPress:
  • It was noted that it’s common for E2E tests to fail intermittently, which can confuse and hamper development. This is often attributed to unexpected delays in DOM updates.
  • Consider that E2E testing can passively validate accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) (“a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)”) as a beneficial byproduct.
  • Add E2E section to Week in Test to increase awareness of this aspect of WordPress testing.

Tuesday Meetings Time Change

  • It was suggested that Tuesday meetings for <test-chat> and <test-triage> be shifted from 17:00 to 16:00 UTC to allow broader participation from European contributors. Please share your vote or thoughts here.

Props to @boniu91 for peer review of this post.

#meeting-notes

Test Team Chat Summary: 15 March 2022

The meeting started 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/. here.

@hellofromtonya made a summary of last week in Test:

  • Team agreed to first prioritize getting the @covers reviewed and committed as quickly as possible
    • @costdev and Tonya planned to do a deep review of @pbearne‘s PR
    • Then 6.0 took priority last week as Colin joined the 6.0 Release Squad
  • @Puja‘s e2e test was committed
  • Test Handbook – Team agreed to plan out how transform the handbook into a tool that empowers contributors to quickly get started testing.
  • PHPUnit Test Suite Restructuring – Team agreed to plan out how to restructure

@Ugyen asked if there’ll be a 5.9.3 release before 6.0, @audrasjb confirmed 5.9.3 release in the upcoming weeks.

@pbearne refreshed the @covers PR

@hellofromtonya agreed to move forward with the batch approach to make a review and commit process easier for this big PR

@tykoted joined his first meeting

@hellofromtonya reminded about the need of having one or two people that would lead the Test Handbook project. Together with @boniu91 agreed that summary post will be a good place to promote this opportunity.

@justinahinon described that moving e2e tests to Playwright in 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/ is going quite well. He’s also working together with @juhise on moving existing tests to Playwright

@hellofromtonya reminded why we are in the process of switching to the Playwright

@pbearne offered Tugboat as a tool that could help the Test Team, he’ll provide more details soon.

Test Team is looking for a volunteer or two as lead(s) to shepherd Test Handbook forward. If you’re interested in this role, please leave a meesage.

#meeting-notes

Test Team Chat Summary: 1 March 2022

The meeting started 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/. here. With no agenda, the chat was open floor discussions.

6.0 Focus

@costdev asked: What projects or specific goals are targeted for 6.0? @hellofromtonya replied that 6.0 roadmap of the key features and refinements to be built for this major releaseMajor Release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality.. The Test Team will support that effort.

4 Proposed Initiatives

Team discussed other projects and goals not necessarily specific to 6.0:

  • Initiative 1: Audit and reorganize the testing suite – which includes @covers and #53010.
  • Initiative 2: Ensure all patches ready for commit have test.
  • Initiative 3: Grow the e2e test suites.
  • Initiative 4: Testing Handbook – needs a lot of work to empower anyone to quickly get testing.

@hellofromtonya shared a bigger picture framework / thinking for testing:

Tests express the intended and expected behavior of how the code should and shouldn’t behave under different conditions. When tests do this, they are a wonderful source for learning.

Testing itself fuels the 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. back into the development process to know what does and doesn’t work as expected.

How?

  • Get more people involved in testing -> meaning the handbook, tooling, and code examples need to empower anyone to get testing.
  • Properly test both the expected (happy) and unexpected (unhappy) behavior in code at different levels > meaning tests need to be audited to ensure they are doing this and that the key areas have the tests needed to provide the feedback early enough.
  • Get the tests organized, readable, and usable.

The goals aren’t to build more tests. Rather, the goals are to build the tests that are needed to validate the code works as expected under different conditions to further help improve the user experience and get feedback fed back into the development cycles.

Where to start? What to prioritize?

Team discussed whether to start with planning the test suite reorganization or getting the @covers tags added / corrected.

The team decided to prioritize the @covers tags in order to ensure the code coverage reports are accurate to point to where more work is needed.

Team then discussed how to divide the auditing work to finish the @covers PR and get it merged.

Test Handbook

Restructuring the handbook raises the potential for more team members to work on the other initiatives. Since it feeds the numbers, confidence and accuracy of the team, it helps with everything else. Coverage reports won’t help increase the number of test team contributors, so I’m tempted to say that our first big drive should be to work on the handbook. If there’s things that need to be done in advance of handbook entries, such as establishing a new structure for the tests, that should be done in order to help 1) achieve the goal of restructuring and 2) provide information for the handbook entries.

by @costdev

Props to @boniu91 for proofreading.

#meeting-notes