On Thursday, 26 March at 17:00 GMT+3, <test-chat> started in #core-test facilitated by @r1k0. The agenda can be found here.
1. Attendance
In attendance was: @ozgursar @nikunj8866 @huzaifaalmesbah @mbigul @mohkatz @sonaliprajapati @juanmaguitar @mosescursor @mehrazmorshed (async) @sumitsingh (async)
2. Volunteer
This week’s facilitator was @r1k0
This week’s note-taker was @r1k0
3. Test Team Discussions
Review the current handbook PRs before publishing
The team discussed the progress of the handbook PR for the new documentation page and shared review updates. Initial feedback from @nikunj8866 noted that he had reviewed it and left some comments. He also pointed out that it would benefit from an additional review before publishing.
@r1k0 said he will leave a review, as it seemed good to him.
@ozgursar mentioned that it has corrected parts of the PR based on the feedback provided earlier.
@huzaifaalmesbah added they will review the PR today after work.
@nikunj8866 raised an issue that the new page still needed to be added to the handbook-manifest.json file so that it would appear in the handbook navigation.
@ozgursar asked @nikunj8866 where the new page should be placed, as it relates to another PR opened by @huzaifaalmesbah.
The team agreed that the most appropriate location would be under “Get set up testing”, with the page to be added there for now as the last item.
@r1k0 requested that the conversation be continued on GitHub 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 by the repository owner. https://github.com/ to discuss the page creation and placement further.
The team also checked in on the progress of another handbook PR for a new documentation page.
@r1k0 mentioned he will take a closer look at it today and share his thoughts.
@mosescursor reviewed the PR and provided feedback.
@ozgursar Reviewed and helped co-author the PR.
@huzaifaalmesbah agreed to address the requested changes. After that, the page will be ready for publishing.
Proposed new handbook pages
The team discussed a proposal for adding new handbook content related to database inspection during testing.
@ozgursar pointed out it usefullness for testers, and asked where it fits best.
@nikunj8866 agreed that this page is necessary.
@r1k0 suggested it would fit better as part of the “Get Set Up for Testing” section, and @nikunj8866 also suggested including it as a subsection in the “Get Set Up for Testing”, not as a separate page.
In addition to the proposed method, @r1k0 suggested referencing alternative database access options, such as command-line access or plugins.
There was also interest in confirming how well the proposed setup would work with wp-env, @juanmaguitar confirmed that Docker additions should play nicely with wp-env.
@huzaifaalmesbah suggested grouping similar Docker-related setup options under a broader override-related section, which could help organize related documentation more clearly.
@r1k0 requested that team members add more comments to the GitHub issue to help refine the new page.
The team also discussed another proposed addition of a new page (Add Trac Keyword Triage Guide for Test Team Members) to the Test Handbook. There was general agreement to continue the discussion around implementation details in a pull request, which will help move the proposal forward and allow for more focused feedback.
@ozgursar suggested that the page could include a link to a related Chrome extension as an additional resource for contributors.
@juanmaguitar pointed out a related Meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket that is highlighted for discussion: #8202, which explores incorporating some of the plugin 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.’s functionality directly into Trac.
@r1k0 encouraged contributors to share feedback in the Trac ticket.
Finally, @r1k0 raised the issues below for further contribution and discussion, and encouraged new contributors to share feedback or open pull requests to push the issues forward.
4. Open Floor
@juanmaguitar shared plans to publish a Make WordPress post about the WordPress Contributor Toolkit (Electron), highlighting its goal of reducing friction for code contributors, particularly first-timers. The tool, developed by the creator of WP Playground, is also intended to support Test tables at Contributor Days. Feedback and assistance to promote the tool at Contributor Days were welcomed.
@juanmaguitar welcomed everyone to a “Bug Scrub Session” scheduled in #core but was later postponed due to a timing conflict with the WordPress 7.0 RC2 release party.
5. Announcements
WordPress Ecosystem Announcements
Test Team Announcements
Call for Testing
6. Other Meetings
Props to @huzaifaalmesbah, @ozgursar and @nikunj8866 for helping review this article and offering feedback.
#test-chat-summary
You must be logged in to post a comment.