Hallway Hangout: Let’s chat about improving accessibility in the Site Editor

This is a summary of a Hallway Hangout that was wrangled in the #fse-outreach-experiment and #accessibility channels as part of the FSE Outreach Program. Huge props to @alexstine and @joedolson for demoing.

Attendees:

@alexstine @joedolson @richtabor @annezazu @poena @joen @jerryj @sergey @afercia @queerdevperson

Video Recording:

Notes/Links:

Overall demos

To start, we did a brief round of intros for @alexstine and @joedolson before deciding to dive into the actually content to give more time to the topic. Overall, the following demos were done with a screen reader, each marked in the YouTube video with chapters:

  • Manage the navigation menuNavigation Menu A theme feature introduced with Version 3.0. WordPress includes an easy to use mechanism for giving various control options to get users to click from one place to another on a site..
  • Edit 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. to add Site Logo. 
  • Using the Command Palette. 

Overall discussions

Outside of that, two discussions broke out in between demos around the following:

  • Use of inert for disabled blocks with a broader discussion ongoing in GitHub.
  • The number of different modes, along with the usefulness of List View combined with focus mode, and the ways in which edit and navigation mode weren’t created at a time when nested blocks existed. A broader discussion is underway around providing a focused mode for any container block.

Balancing verbosity

Throughout the discussion, there were different mentions of too much verbosity, like upon entering Site View of the Site Editor, compared to moments where there’s a lack of information, like upon selecting 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.. On the flip side, with the Command Palette, what’s announced is incorrect information!

On the discussions of different modes

@alexstine doesn’t like the different modes and finds List View is easier to work with partially because you don’t know where to navigate around in the canvas otherwise with the keyboard. It’s very unpredictable what direction you will be traveling based on what you select. Right now, we’re in a situation where we have too many ways to move around: arrow keys in the canvas, have an edit mode, have a navigation mode, have list view. Can we consolidate? @afercia added context that edit and navigation mode were done when there were no inner blocks. It was a way to simplify navigation between blocks but the structure of the blocks was way simpler. This led to a broader discussion around showing List View for individual blocks, similar to what’s been done with the Navigation block, where you can only see the “tree” of that specific block with the inner blocks. @joen jumped in to talk about design explorations on exactly that where you can use a “focus mode” to zoom in on just that part of the page and have List View for just that part of the system.

Manage navigation menu demo

From the demo, here are a running list of notes in order:

  • Wasn’t able to manipulate the individual items in the Site view. Had to enter into Edit view to make changes.
  • It was hard to know what would trigger editing.
  • Upon getting into Edit View, there was tons of verbosity and ultimately focus loss after trying to edit.
  • @alexstine had to then navigate back to where he was which showed the huge cost that comes with focus loss moments.
  • @alexstine demoed how one can select the navigation block but it’s not clear how to act upon it without knowing how to get to the toolbar view. Keyboard users don’t know that pressing right arrow key would lead to what you need. 
  • Detaching page list is a confusing to understand and is required before you can edit the links– can we update the language? The language is hard to understand in general and also impacts synced patterns currently.
  • After detaching and editing, the navigation block still doesn’t give a lot of information.
    • There’s not a way to get more information about the current link you’re working on (what the URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org is, where it’s pointing to, etc). 
    • Information is more limited here and it’s assuming pre-existing knowledge about the menu. 
  • Open up the panel to save but it doesn’t say what’s in there when you first enter. It would be nice to have more info upon entering the Save section rather than going through each section to learn more.
  • Discard changes is confusing and relates to this larger known issue.
  • If you are in navigation mode and you save the Site editor changes, instead of focusing the save button again, it focuses the first button in navigation mode. 
  • Back button in Site View doesn’t have context around what you’re going back to. 

Changing Site Icon demo

  • This worked fairly smoothly once he found where the template parts are.
  • He went into Templates first before going to Patterns based on his experience working with templates.
  • While going through the Template section, @alexstine noted that it might be worth considering not having each template as individual tab stops. 
  • Having a summary of “My patterns: zero, theme patterns: 19” upfront when entering this section would be helpful. 
  • Empty state could be improved which relates to a current open issue on that topic.
  • Confusing to have template parts under patterns rather than templates. This is due to being in an in-between state with template parts. 
  • @alexstine struggled to open up the Header pattern and, upon opening it, lost focus same as before with the navigation block. 
  • Being able to rename group blocks would be a huge help but it’s unclear how that’s announced. This is currently a feature slated for 6.4 so let’s get some testing in place!
  • Ran into a problem where the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. is open once you select a block in the Post Editor but in the Site Editor, it doesn’t open, causing you to need to do a lot of navigating to get it open. 
  • Alex demoed the editable list view for the navigation block in the sidebar, where all inner blocks of navigation block are there. 
  • A larger discussion around showing heading level occurred, along with the lack of document overview in the Site Editor. Instead, we discussed showing the heading level icon along with the text in List View.
  • It would be good to get a solid pattern in place for this experience considering work is underway for adding text to paragraph and list blocks in List view.

Using the command palette:

  • Need to fix naming of the prompt which matches this previously opened issue.
  • Searching within the Command Palette doesn’t share how many results are shown.
  • When going through the results for the command palette, numbers are read off but only shows 5/5 and it’s hard to know to keep going since more than 5 were listed.
  • Doesn’t announce enough results found and there’s an incorrect number of announcements. 
  • Need more 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) testing at the start before these features are implemented. 
  • A third party library was used so it’s tricky to keep BC when addressing problems. 

Inert usage 

  • Broader discussion and demo of inert was done with the Comments block
  • When selected, it only announced “selected” because this form is specified as inert. 
  • Using inert makes something non interactive which is something we do desire (aka folks won’t try to submit a form) but if we’re using a technique that causes it to not exist for one group of people, it’s inactive and absent. There’s no parity between the experiences. For screen reader users, there’s no preview. 
  • This entire discussion is very similar to how to hide content, like using display:none. Anytime you say something is inert and if it were invisible, it’s fine and has no impact. 
  • In this case though, we’re using inert to reflect a preview state while that preview state is nonexistent for screen readers.

Follow up issues:

I (@annezazu) will follow up to open each of these but welcome folks to help me out here as anyone has time 🙂

  • Focus loss after entering edit mode for the navigation block and for header template part. 
  • Update detach language for navigation block and synced patterns.
  • Add more information when you open up the save panel without needing to go through each section. 
  • Open bug for when you are in navigation mode and you save the Site editor changes, instead of focusing the save button again, it focuses the first button in navigation mode. 
  • Back button in Site View needs to provide more context around what it’s going back to.
  • Heading in List View doesn’t indicate the heading level – show heading level in list view and have aria label show heading level. 
  • Consider not having each template be a tab stop when in the Site Editor > Template view.
  • Provide a summary upon entering the pattern section (ex: “My patterns: zero, theme patterns: 19”).
  • Open sidebar upon block selection in the Site Editor to prevent labor of navigating to get it open (match experience in Post Editor).
  • Bug with Command Palette announcements for results. 
#fse-hallway-hangout

Hallway Hangout: Let’s chat about the WordPress 6.4 & Evolving the FSE Outreach Program

This is a summary of a Hallway Hangout that was wrangled in the #fse-outreach-experiment channel as part of the FSE Outreach Program.

Video Recording:

Notes/Links:

When I was the only one in attendance, I decided to still record an update on both WordPress 6.4 and the FSE Outreach Program. To do so, I went through the Evolving the FSE Outreach Program post and went through various top 6.4 related items. Anything starred is not yet merged:

From there, I went through the Roadmap to 6.4 post in more detail, explaining what isn’t going to make it and has been punted.

#fse-hallway-hangout, #fse-outreach-program

Test Chat Summary: 29 August 2023

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

Announcements 📣

  • WordPress 6.3.1 Maintenance Release: This update fixes a handful of CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and 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 items, details of which can be found in the previous RC1 announcement.
  • 6.4 Release Parties Schedule and Hosts: The release squad is looking for volunteers to fill various roles required for each milestone’s <release-party>. Raise your hand, or be kind and share this post with folks you think can help out. Thanks!
  • The Future of WordPress & What’s Next for Gutenberg: Watch these presentations from WCUS 2023 to see what’s in store for 6.4 and beyond.

Focal Group Updates 🗣️

Handbook

There is an open PR to add a Test Team Rep page to the handbook. Reviews are welcome, which can be comments/reviews on the PR, or a pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” in #core-test if something needs more discussion.

Open Floor 💬

FSE Outreach Program Update

[This discussion started here.]

It has been proposed that the #fse-outreach-experiment begin the process of spinning down its user testing aspect (i.e. the program’s calls for testing) by the time WordPress 6.4 ships. In place of testing efforts, focus would shift to emphasize wider adoption of the Site Editor through hallway hangouts, dev documentation efforts, and other adoption-focused initiatives on the path toward wrapping up Phase 2 of the WordPress Project Roadmap.

Because the FSE Outreach Program has considerable overlap with Test Team efforts, program leadership has requested input from Test Team contributors with questions or concerns around the proposed shift. This follows other shared feedback from current program participants.

It was stressed that changes in the outreach program be handled carefully and slowly, and to capture opportunities for feedback. The next step is to compile initial feedback and thoughts around this change to share in a Make/Test post for wider input.

Calls for Testing

Current contributors in the #fse-outreach-experiment have expressed a desire to continue testing in a format adapted from or similar to the outreach program. Structured ad hoc calls for testing from within the Test Team are similar, and would provide an opportunity for continued contribution through testing. [Ed. note: the Test Team should also consider adopting things that worked for FSE CfTs to improve the experience for all testers.]

A possible source for CfT topics could be pulled from roadmap posts (for example), or otherwise collected in an ideas backlog (for example). Some pertinent links for CfTs can be found at:

Work is ongoing for documenting processes in the Test Team. The Handbook project can be found at https://github.com/wordpress/test-handbook.

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

[This discussion started here.]

The Call for Nominations for the next Test Team Reps is underway. Test Team members’ help is needed to nominate or volunteer for this role, to help represent the team to the wider project.

If you have a nominee in mind, or questions about the role, please comment on the post, ask in #core-test, or reach out directly to @ironprogrammer in 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 stepped forward with an offer to help mentor volunteers for this role. It was also noted that serving as a rep offers an excellent opportunity to gain a broader perspective of how Test Team interacts with other teams, and that while it isn’t a “lead” role, there are some leadership-focused skills that reps develop in the process.

Please submit nominations by Thursday, August 31 Friday, September 22, end of day (UTC).

Next Meeting 🗓

The next scheduled meeting is on 5 September 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 @annezazu for peer review of this post.

#fse-outreach-experiment, #meeting-notes

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

Hallway Hangout: Let’s chat about the Site Editor & 6.3

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!

Attendance:

@karmatosed @paaljoachim @beckej @scruffian @annezazu @piermario @james-roberts

Video Recording:

Notes:

We kicked off the hallway hangout going over various places to stay up to date on what’s happening:

  • Phase 2 overview issue: tracking the high level, larger projects for 6.3.
  • Phase 2 board: tracking the high level projects alongside medium projects that ladder into the larger work.
  • UX and Polish board: tracking smaller, developer ready items that help polish the experience. This is a great place for folks who want to dive in to help without needing to stay up to date on the larger projects.

From there, we discussed the larger topic of reintroducing content editing to the site editor, including where hints in the interface should be, the need to have strong user stories around using this functionality, and ensuring clarity between template and post editor. We very briefly touched on how there will be expanded Detail views of page, template, template part, styles without going into much detail. 

We then jumped into evolving the wp:pattern block and how that ties in with work to add UI to save patterns and having a library to store patterns alongside reusable blocks. This included watching a video demo about syncing patterns and going through details of sync, partial sync, unsync. Later on, we discussed being able to see a hierarchy of styles and knowing which make up a pattern. 

With Ben on the call, we went over the focuses for 6.3 for navigation, including: adding back the navigation section to the Site Editor, improved link control, and using slugs to reference menus. We talked about the problem with how you can repeatedly import classic menus, leading to lots of extra menus, and discussed the need to see where menus are used when they are listed out so you know which to delete. 

We ended on some interesting technical happenings that lead to some powerful UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing./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. options:

Lots of work has momentum right now so stay tuned for much of it to be tested! 

#fse-hallway-hangout

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