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

Hallway Hangout: All Things Media

This is a summary of a Hallway Hangout that was wrangled in the #fse-outreach-experiment channel as part of the FSE Outreach Program. All were welcome! The intent was to chat about whatever was on folks’ minds as 5.9 is around the corner. Thank you to all who joined.

Attendance: @fcoveram, @annezazu, @bobbingwide @pdclark, @beckej, @paulbigai, @ndiego, @piermario, @paaljoachim, @courane01

Video Recording:

Topics Covered:

  • We kicked off the call talking about a few specific issues and use cases, like copying/pasting an image into an image 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. and being prompted to name an image upon pasting. I couldn’t replicate an issue here after the call but am following up via DM.
  • We dug into rethinking the role of a featured imageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. in a full site editing world, including looking at a few designs.
  • We chatted about the overall pain pointPain point Pain points are “places where you know from research or analytics that users are currently getting hung up and have to ask questions, or are likely to abandon the site or app.” — Design for Real Life and desire for better media management (folders, rename files, etc). With FSE, things that used to be locked away are increasingly getting easier to work with to the point that there’s a feeling of wanting to be able to do everything.
  • We chatted briefly about how Openverse could integrate with the pattern directory and how the media library might be able to integrate with media related patterns. Overall, it feels really high impact to have your own images or an image you’re looking to use baked into a pattern you want to use as well.
  • We talked about how switching themes causes featured image changes in terms of sizing/cropping, which can be a bit annoying to have to refine and an extra step when switching themes.
  • The topic of uploading an image to the photo directory from one’s media library came up as it involves a few steps from how to connect to a WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ profile to a potential way to see all your content in Openverse to how to connect multiple sites to the same profile and more.
  • @beckej was kind enough to share his screen to show off how he uses the Pressbooks 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, which includes attributions in the media library. Since this is already a WordPress solution, it’s great to see how it’s being built and what it might look like. We talked about how perhaps it’s up to the author to choose from a few different style options depending on how they are using an image. Ideally, attributions can also match the theme style so that, upon adding an image, it immediately fits in.
  • We dove into what other tools do well (or poorly) that should be considered as part of WordPress’ media feature. This led to discussing how other services have paid connections (like squarespace) so don’t  have to worry about things like attributions, which inherently makes the job WordPress has a bit harder.
  • The topic of attributions led to talking about how can we make attributions “cool”/the norm? Similar trends have come up with offering captions on videos on social media, an increasing number of folks sharing “props to @xyz profile”, and more folks paying attention to alt text.
  • @paaljoachim shared a previous Google doc of a few screenshots from other services.
  • As the photo directory grows, the question of how we can improve adding alt text to images came up as right now the description field doesn’t nudge things along too much.
  • We discussed how we can do things like show how an image is displayed elsewhere as a way to recognize content creators. Some folks might also not want to use a heavily used image and might purposefully seek out less used ones to have more individuality on their site.
  • We talked through how important that very first moment of using Openverse will be in terms of ease of use and how the attribution flowFlow Flow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it.
    Flow is the actual user experience, in many ways. If you like, you can think of flow as a really comprehensive set of user stories. When you think about user flow, you’re thinking about exactly how a user will perform the tasks allowed by your product.Flow and Context
    works. If it’s magical and does things like matching the theme styles, it could really help with adoption.
  • We ended the call agreeing that the ability to disable Openverse integration will also be important. This has come up with the pattern directory too and feels standard at this point to have this kind of opt in optionality.
  • At some point during the call, Ed also shared a great example of attributions on a site where, at the bottom, there’s a drawer that expands and shows all attributions there. It’s great to see specific examples and how they are being solved as this might influence how something like a gallery might work.

I love the idea of pulling the first image as the featured image if there is no featured image. My role is I work in SUNY, working with students, and that’s something they always forget to do.

@beckej in the comments of the call.

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

Test Team Chat Summary: 12 October 2021

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 summarised last week in tests:

  • Team cleared large number of tickets that needed help.
  •  5.9 e2e strategy session was held and the strategy was set.

5.9 e2e strategy session was a big step forward for WP CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., as:

  • We are getting started with bringing e2e tests to Core.
  • We now have clear boundaries of where e2e tests will live in Core and 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/.
  • We have a process/workflow from idea => PR ready => code review => commit.

@hellofromtonya mentioned, that the next step is to do the same for PHPUnit integration tests. Both of the above will become a 5.9 Test Roadmap

Open Floor

@justinahinon shared his concerns about shipping Playwright to Gutenberg now as it’ll need lots of work. He thinks that it’s better to make this experiment in the Core before.

@hellofromtonya shared her thought that Puppeteer and Playwright might exist in the suite together

@costdev agreed

@hellofromtonya wrote the Bigger Scope which is:

  • Teaching contributors
  • Creating tool that will convert from Puppeteer to Playwright
  • Changing to linters

@costdev reminded, that we need to agree on standard for writing e2e with Playwright

@hellofromtonya mentioned that she’s working on the Webfonts APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. The API will handle the theme.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. webfonts. There are some tickets that need unit/integration tests:

  • https://core.trac.wordpress.org/ticket/52252
  • https://core.trac.wordpress.org/ticket/47642
  • https://core.trac.wordpress.org/ticket/49985

If anyone’s interested in writing tests please leave comment either on Slack or in ticket itself.

Hallway Hangout: Pattern Party Testing Walkthrough (6 October)

This is a summary of a Hallway Hangout that was wrangled in the #fse-outreach-experiment channel as part of the FSE Outreach Program. It was intended to be a casual walkthrough of the current call for testing with @sparklingrobots taking the lead sharing their screen. Big thank you for being brave enough to meander around the call for testing publicly.

As a reminder, there is still 1 week left to participate so please join in if you can.

Attendance:

 Thank you to everyone who attended 🙂 @karmatosed @mkaz @shaunandrews @paaljoachim @annezazu @sparklingrobots @richtabor

Video Recording:

Feedback Overview

Throughout the session, some specific issues were noted as problem areas to follow up on, including some previous reported and some new:

  • It’s not clear when you are adding a theme 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. outside of the Query 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. vs within. In this case, it was confusing when the Post Comment Count block wasn’t properly displaying the number of comments and it wasn’t clear the issue was that it needed to be within the loop. There’s an open issue to discuss this general phenomenon.
  • She had a desire to change the post excerptExcerpt An excerpt is the description of the blog post or page that will by default show on the blog archive page, in search results (SERPs), and on social media. With an SEO plugin, the excerpt may also be in that plugin’s metabox. length, which has an open enhancement issue.
  • There was an issue with the post title overflowing outside the bounds of a Query Loop block pattern. Need to replicate and open an issue!
  • There was a strange Inserter issue where you couldn’t find any theme blocks based on the current block you were selecting. Need to replicate and open an issue!
  • The call for testing itself needed to have updated instructions as you need to install 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/ first before activating a block theme. This was updated live on the call.

Outside of specific points of feedback about the experience, there were also high level themes that became apparent as @sparklingrobots made her way:

  • They were confused about where various settings were expected to be, sometimes seeking out the block toolbar and other times the block 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.. For example, it was unclear at a glance how to change width of overall query and how to change the number of posts displayed.
  • The placeholders for various theme blocks were underwhelming and often not informative enough to know quite how to customize.
  • She was confused by how by selecting one Query Loop pattern, they instead ended up with two Query Loops! This is part of one of the default patterns included in the Query Loop block and could cause confusion long term when thinking about having more complex patterns.
  • There was a desire for more dimension controls for various blocks including the Columns Block and Post Comments block. This is under active iteration!

We ended the call talking about how the future of the Query Loop block powering more user friendly variations, an integrated block pattern library, an overhaul of the IA of the various design tools, & more will help ease this current experience. For now though, we’re in an in between state where loads can still be learned to improve the default tools themselves.

Next Steps

@annezazu will follow up next week after she returns (she’s out Thurs/Fri) to replicate and open issues.

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

Test Team Chat Summary: 28 September 2021

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 introduced agenda of the meeting and shared a post that describes where the testers are needed during the week. At the end of introduction, Team Test Update was shared.

The team was able to decrease the numbers of tickets.

Modernizing to the Latest PHPUnit

@hellofromtonya described how this changes impact CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. testers. Anyone that’s running the PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. test suite or buil automated integration tests, should read the dev note.

For running the PHP test suite with Docker, nothing changes in your workflow:

npm install
npm run build:dev
npm run env:start
npm run env:install

and for running the tests:

npm run test:php

for running a specific group:

npm run test:php -- --group groupname

When not using Docker to test, then there are extra steps. The handbook and Dev Note provide the details.

5.9 Test Roadmap

In 5.9 release, Test Team will introduce the roadmap.

Everyone agreed that it’s necessary and help with the process of analyse and future improvement. @hellofromtonya also mention that we’ll implement a longer term vision, called North Star.

@justinahinon shared his document that is a great roadmap for automate tests focal group.

Focal Groups

@hellofromtonya shared an idea to have 5 separate focal groups in Test Team, each will need folks to shepherd the group:

If anyone is interested in being a co-lead of any group, it’s definitely possible and the Team is looking forward for new members.

@hellofromtonya shared expectations:

  • Shepherd your focal group – meaning be active in it, help contributors, know the status, help move work forward, stay aligned to the roadmap, and help to develop the roadmap
  • Each week – share an update for your group (can go in the team’s update)
  • When blocked or need more help, 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.” Team Reps or another group for help

Last words

Team agreed that we need a bit of advertisment of our group.

Test Team Chat Agenda for 28 Sep 2021

Here is the agenda for the upcoming Test Team Chat scheduled for 2021-09-28 13:00.

This meeting is held in the #core-test channel in the Making WordPress slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Highlights

Agenda

  • Changes to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.’s PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. test suite -> What does this mean for test?
  • 5.9 Test Roadmap
  • Focal group updates
  • Any blockers?
  • Open floor

Open Floor

Do you have something to propose for the agenda? Please leave a comment below.

Can’t make the meeting? Share anything relevant for the discussion in a comment below.

Props: @boniu91 for peer review.

#agenda, #build-test-tools

5.9 End-to-End (e2e) Working Strategy Session Agenda – RESCHEDULED for 6 Oct 2021

With efforts in progress to introduce end-to-end (e2e) testing in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., this working session brings folks together to collectively define the big picture goals and what to accomplish during the 5.9 cycle (i.e. roadmap). These goals can then serve as the North Star 🌟 to guide contributors for maximizing impact.

When: RESCHEDULED for 2021-10-06 10:00
Where: Zoom call (link will be shared in the Making WordPress slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. #core-test channel prior to the start of the session)
Topic: Strategize e2e goals for the 5.9 release cycle

Agenda

  • Define big picture goals of what to accomplish during the 5.9 cycle
  • Identify and prioritize areas of Core that could most benefit from e2e tests
  • Discuss if any 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/ tests can be ported over to Core
  • Strategize stepping stones
  • Identify key areas of contributor needs and responsibilities

Resources

Props to @justinahinon for proofreading.

#agenda, #build-test-tools

Test Team Chat Summary: 14 September 2021

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.

Short explanation for first time attendees

@hellofromtonya reminded, that this bi-weekly meeting is where people who test WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. gather to discuss important things regarding test contribution. Testing includes manual testing, attempting reproduce reported issues, and automated testing.

You can find the agenda meeting here.

Week in Test introduction

@hellofromtonya described the purpose of this weekly publication, in short, it includes:

  • Parts of the core where testing help is needed this week
  • Learning and reading opportunities

Team agreed that it’s very helpful.

Last week’s Team update introduction

@hellofromtonya reminded that it’s a Team update, an overview of what has happeed last week. It also includes stats that are related to our team.

The Team agreed that the queue of the items that need testers’ attention is long.

Focal group updates

@hellofromtonya explained that it’s a time for testers to share updates for testing project initiatives. This section has started with:

  • PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php. 8.1 fixes are underway
  • Modernization to Latest PHPUnit project is nearly finished. Backporting is next, then dev note
  • PHPUnit Test modernization is ongoing

@hareesh added:

  • The latest version of jQuery 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. was recently merged to Core. Need a lot of testing.

Documentation strategy

@francina opened this discussion, asking what instructions we want to give. The main reason was related to setting up environment.

@hellofromtonya proposed to create a docs empowering everyone to contribution, we need clear entry points for:

  • Local machine setups
  • How to do different types of testing
  • How to create test reports

Team agreed that this documentation should be present in Make Test website, Make Core should only refer to it.

@hellofromtonya mentioned, that PHPUnit docs page lacks a reference to where contributors can set up their local machines. That should be a priority.

@francina @juhise @hellofromtonya agreed that the Team should start documenting the steps for Docker testing environment and later repeat the same pattern for other solutions. On of the concerns is that screenshot are getting outdated very quickly.

@mkaz shown 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’s development site setup instructions based on wp-env. Team agreed that all projects should be pointing to one place where everything related to development environment is stored and maintained.

@hellofromtonya proposed a step-by-step instrctions of creating documentation for different types of test environments:

  • Start with Docker
  • Setups on Make Test with reference in Make Core
  • Figure out the doc info structure / strategy
  • Doc for different OS: Windows, Mac, and Linux
  • Link to tooling’s official docs
  • Get feedback from contributors
  • Refine
  • Repeat

@francina proposed working session with setting up environments. It’s going to happen on 2021-09-23 14:00

People with different OS will be essential for the successful meeting.

@boniu91 shared a reminder that on 2021-09-17 13:15 the Test Scrub is going to happen taking care of the following tickets:

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

Test Team Chat Agenda for 14 Sep 2021

Here is the agenda for the upcoming Test Team Chat scheduled for 2021-09-14 13:00.

This meeting is held in the #core-test channel in the Making WordPress slackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/..

Agenda

  • Week in Test: where you can contribute and learn this week
  • Review last week’s Team update
  • Focal group updates
  • Open floor

Open Floor

Do you have something to propose for the agenda? Please leave a comment below.

Can’t make the meeting? Share anything relevant for the discussion in a comment below.

Props: @boniu91 for peer review.

#agenda, #build-test-tools