The Test Team helps manage testing and triage across the WordPress ecosystem. They focus on user testing of the editing experience and WordPress dashboard, replicating and documenting bug reports, and supporting a culture of review and triage across the project.
If you’d like to help test Full Site Editing, please join the FSE Outreach Program. You can find current calls for testing for this program here and you can join the fun in #fse-outreach-experiment.
This is a summary of a Hallway Hangout that was wrangled in the #fse-outreach-experiment channel as part of the FSE Outreach Program.
As a reminder, there’s one week left to share your questions about FSE.
Attendance:
Thank you to everyone who took time out of their lives to attend. It’s always lovely to see your faces and have time to chat. @overclokk @karmatosed @get_dave @annezazu @asilver @fabiankaegy @kafleg @mburridge
Video Recording:
Topics Covered:
We mainly focused on three items: the Go/No Go recap, the Site Editing IA concepts, and the Navigation Editor & Block work.
For the Go/No Go, we chatted about items we were excited for, including talking through @karmatosed wonderful patternspiration.com where she’s started to make art-like creations. This spurred the idea of a virtual museum of art made from blocks that yours truly just might try to make a reality.
From there, we moved on to walk through the various early design explorations for the Site Editing IA. This led to a lively discussion alongside walking through both the current experience and the various prototypes. We talked about the changes in colors between the different interfaces, how much friction to add/remove for various pieces, and which might make the most sense for 5.9. @fabiankaegy had some great feedback around including more than just the 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. and footer for the Separate exploration but in a view only manner similar to what currently is available with locking things in patterns.
Finally, we covered the latest on the Navigation Editor 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. work. @get_dave was kind enough to talk through where the project currently stands with focus shifting to the Navigation Block in order to then lay the foundation for the Navigation Editor. A key part of this work right now is “separating the navigation’s presentation from its data in order to make navigations reusable”. This will allow both for easier block theme switching while retaining menu data and for menus to be edited in a template part without creating a local copy. If folks have time, check out these two PRs to help move this important work forward: Save Navigation Block data to a wp_navigation post type and Try using a template part in the navigation block.
Welcome to this week’s edition of Week in Test! This post is a curated list of where you can get involved (i.e. where testers of all skill levels and expertise are needed), learning opportunities, and some reading to keep you informed.
Looking for ways to contribute? The following tickets and patches need contributors.
Who? All contributors (not just developers) who can set up a local testing environment, apply patches, and test per the testing instructions.
The following tickets need testers to manual test and provide feedback (test report):
Who? Any QA or 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. developer contributors who can (or is interested in learning how to) build automated PHPUnit tests.
The following tickets need PHPUnit tests build:
_embed and _fields query parameters in the same querymonthnum query var is set without the year QVWho? Any contributor.
The following new tickets need testers to attempt reproducing the reported issue and then providing a test report with the results:
Props to @boniu91 for peer review.
Welcome to this week’s edition of Week in Test! This post is a curated list of where you can get involved (i.e. where testers of all skill levels and expertise are needed), learning opportunities, and some reading to keep you informed.
Looking for ways to contribute? The following tickets and patches need contributors.
Who? All contributors (not just developers) who can set up a local testing environment, apply patches, and test per the testing instructions.
The following tickets need testers to manual test and provide feedback (test report):
clean_dirsize_cache()Who? Any QA or 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. developer contributors who can (or is interested in learning how to) build automated PHPUnit tests.
The following tickets need PHPUnit tests build:
clean_dirsize_cache()$post in update_post_cache()_embed and _fields query parameters in the same querymonthnum query var is set without the year QVWho? Any contributor.
The following new tickets need testers to attempt reproducing the reported issue and then providing a test report with the results:
get_header_image_tag doesn’t add srcset/sizesReproducing the reported issue is the first step in a new defect ticket’s lifecycle. Why? In order to fix a bug, first step is confirm the bug is reproducible and is due to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. itself (and not a third party like a plugin or theme).
Props to @boniu91 for peer review.
Welcome to this week’s edition of “Week in Test”, a curated list of where you as a contributor can get involved (testers needed), learning opportunities, and some reading to keep you informed.
Looking for ways to contribute? The following tickets and patches need contributors.
Who? All contributors (not just developers) who can set up a local testing environment, apply patches, and test per the testing instructions.
The following tickets need testers to manual test and provide feedback (test report):
clean_dirsize_cache()Who? Any QA or 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. developer contributors who can (or is interested in learning how to) build automated PHPUnit tests.
The following tickets need PHPUnit tests build:
clean_dirsize_cache()$post in update_post_cache()_embed and _fields query parameters in the same querymonthnum query var is set without the year QVWho? Any contributor.
The following new tickets need testers to attempt reproducing the reported issue and then providing a test report with the results:
Reproducing the reported issue is the first step in a new defect ticket’s lifecycle. Why? In order to fix a bug, first step is confirm the bug is reproducible and is due to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. itself (and not a third party like a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party or theme).
Props to @boniu91 for peer review.
Welcome to this week’s edition of “Week in Test”. This post highlights where you as a contributor can get involved (testers needed), learning opportunities, and some reading to keep you informed.
Looking for ways to contribute? The following tickets and patches need contributors.
Who? All contributors (not just developers) who can set up a local testing environment, apply patches, and test per the testing instructions.
The following are tickets and patches that need testers to manual test and provide feedback (test report):
clean_dirsize_cache()Who? Any QA or 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. developer contributors who can (or is interested in learning how to) build automated PHPUnit tests.
The following tickets need PHPUnit tests build:
clean_dirsize_cache()$post in update_post_cache()_embed and _fields query parameters in the same querymonthnum query var is set without the year QVWho? Any contributor.
Since last week, there are 10 new tickets which need testers to attempt reproducing the reported issue and then providing a test report with the results.
Reproducing the reported issue is the first step in a new defect ticket’s lifecycle. Why? In order to fix a bug, first step is confirm the bug is reproducible and is due to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. itself (and not a third party like a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party or theme).
Props to @boniu91 for peer review.
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 originally announced in this post. Thank you to everyone who joined in!
Attendance: @paulbigai @karmatosed @mkaz @get_dave @annezazu @courane01 @shaunandrews @pdclark
Video Recording:
Topics Covered:
Ideas for improvement
Welcome to this week’s edition of “Week in Test”. This post highlights where you as a contributor can get involved (testers needed), learning opportunities, and some reading to keep you informed.
Looking for ways to contribute? The following tickets and patches need contributors.
Who? All contributors (not just developers) who can set up a local testing environment, apply patches, and test per the testing instructions.
The following are tickets and patches that need testers to manual test and provide feedback (test report):
clean_dirsize_cache()Who? Any QA or 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. developer contributors who can (or is interested in learning how to) build automated PHPUnit tests.
The following tickets need PHPUnit tests build:
clean_dirsize_cache()$post in update_post_cache()_embed and _fields query parameters in the same querymonthnum query var is set without the year QVWho? Any contributor.
Since last week, there are at least 18 new tickets which need testers to attempt reproducing the reported issue and then providing a test report with the results.
Reproducing the reported issue is the first step in a new defect ticket’s lifecycle. Why? In order to fix a bug, first step is confirm the bug is reproducible and is due to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. itself (and not a third party like a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party or theme).
Who? Any contributor
🎙 This Friday at 14:00 UTC: come join the live working session.
Watch and learn past working sessions:
Props to @boniu91 for peer review.
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: @poena @richtabor @karmatosed @paulbigai
Video Recording:
Topics Covered:
This post is a summary of the ninth call for testing for the experimental FSE outreach program. During this call for testing, we surpassed 400 members in the channel! I love an excuse to celebrate so please pat yourselves on the back, treat yourself to a favorite dessert, listen to your favorite song, etc to celebrate this neat milestone of community contributions. While we reached this milestone, I do want to note that contributions were lower for this last round than usual so, if you’re sitting back thinking that others have it covered, please instead jump into the next round if you can!
Special thanks to both @mimitips for the Japanese translation and @piermario for the Italian translation.
Shout out to @utz119 @wazeter @alanjacobmathew as first time contributors to a call for testing. Get excited – you now have a testing contributor badge on your WordPress profile!
How far can one go?
Check out @greenshady’s approach (keep in mind he self admittedly “cheated” to get the final look):
@richtabor took on trying to replicate UNG’s header with the following outcome:
High Level Feedback
Here’s what a few folks had to say about the overall experience that can help frame the following detail oriented feedback. Across all of the feedback, the desire for a lighter navigation experience as well as more advanced tools around spacing, bulk adding items, etc. stood out.
I didn’t run into too many issues getting the 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 display decently, but I also know a bunch of tricks to get the editor to do what I need it to do. The end result is ok — but the experience getting there needs a lot of refining yet.
– @richtabor in this comment.
Creating the menu was quite a hassle. Too many clicks especially when creating submenu.
– @alanjacobmathew in this comment.
This was an interesting challenge…I didn’t make anything “beautiful,” however I did find a couple of things while I was trying to do most of this via keyboard-only navigation.
– @bjturner in this comment.
Using 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. still seems the most troublesome area of site editing. I know how much work the development team has put behind the user experience for this feature but cannot help but wonder if there is a point where users can opt into managing its content (the links) via the traditional Nav Menus screen in WordPress. The site editor works fine for the design aspect, but I have yet to feel comfortable using it to manage links.
– @greenshady in this WPTavern post.
After delving deeply into the ins and outs of the navbar – the primary issues all revolve around responsiveness. The coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. issue came down to the navigation bar operating as a separate element (which makes sense for a block) than the rest of what you’d normally consider a complete header. This means that in order to properly size and place the navbar, you have to use a container block like group or columns – which is where alignment starts to get into trouble.
– @wazeter in this comment.
Confirmed bugs
Thanks to clear patterns in feedback due to a larger focus on the navigation block, this is a dedication section to just bugs that were found or confirmed in this test. Those that have been resolved thanks to a release mid-test have been noted below.
General Usability Feedback
At the core of this test, the feedback centered around a combination of small, specific issues and larger problems with the overall settings of different blocks. This made the experience feel less refined and intuitive leading to general confusion when trying to accomplish sometimes simple things, like changing the width of the Search block. In some cases, work is underway actively to address these concerns, as is the case with adding a gap block feature to make it easier to manage the spacing between navigation block items. Some were repeat items and are noted as such below.
I am not able to see any visual difference between Wide width or Full width. Because my browser screen is not wide enough to see the difference. When I widen the browser window then I am able to see the difference. Should the Wide width alignment be response in relation to the browser size window? So the user will be able to see a visual difference in the backend when testing Wide or Full width.
– @paaljoachim in this comment.
I wish there was some way to reduce the default spacing between blocks. For example I want to reduce the space above the 2nd Nav block.
– @alanjacobmathew in this comment.
To add an actual link, users must first add the Page Link block. Then, they can search for a specific page. This two-step process gets me every time.
– @greenshady in this WPTavern post.
For example, adding search to the navbar, and then wanting the search bar to display differently (larger, smaller) with a potentially different background doesn’t work. Individual menu items can’t easily change the background color of a link (e.g. an active color) to align properly with the container element and there are no hover effects (extremely common use cases) without diving into CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. code.
– @wazeter in this comment.
Not quite a bug, but it doesn’t feel polished when the Block hover menu extends past the viewport.
– @bjturner in this comment.
When the first block is extremely near to the editor header, some parts of the block content gets hidden, while the viewport adjusts automatically on both left and right side, the top part remains fixed.
– @alanjacobmathew in this comment.
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) feedback
Thanks to some folks focusing in on what could be done with this test using just keyboard controls, there’s a lovely list of accessibility focused items:
Trying to do keyboard only navigation for working with the navigation block. It’s pretty good, but there’s so many tabs!
– @bjturner in this comment.
Feature requests
While the experience was generally easy enough to follow, a few clear feature requests were raised to streamline the process further:
As mentioned above, an overview issue was shared during this test that explores a more scaled down version of the navigation block to make it easier for simple menus to be created. This will better cover the more common use case for most sites. Since this test explored both a simpler and more complex menu structure, the feature requests reflect each experience.
It just feels too cumbersome to add a custom link today.
– @paaljoachim in this comment.
Creating the menu was quite a hassle. Too many clicks especially when creating submenu.
– @alanjacobmathew in this comment.
This is the first edition of Week in Test. This post highlights where you as a contributor can get involved (testers needed), learning opportunities, and some reading to keep you informed.
Looking for ways to contribute? The following tickets and patches need contributors.
Who? All contributors (not just developers) who can set up a local testing environment, apply patches, and test per the testing instructions.
The following are tickets and patches that need testers to manual test and provide feedback (test report):
Who? Any QA or 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. developer contributors who can (or is interested in learning how to) build automated PHPUnit tests.
The following tickets need PHPUnit tests build:
clean_dirsize_cache()$post` in update_post_cache()Who? Any contributor.
Since last week, there are at least 19 new tickets which need testers to attempt reproducing the reported issue and then providing a test report with the results.
Reproducing the reported issue is the first step in a new defect ticket’s lifecycle. Why? In order to fix a bug, first step is confirm the bug is reproducible and is due to WordPress CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. itself (and not a third party like a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party or theme).
Who? Any contributor
This Friday will be another round of live mob programming session for preparing WordPress for PHP 8.1.
The following are past live working sessions (many more are available):
Props to @boniu91 for peer review.
You must be logged in to post a comment.