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.
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 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.
@hellofromtonya described the purpose of this weekly publication, in short, it includes:
Team agreed that it’s very helpful.
@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.
@hellofromtonya explained that it’s a time for testers to share updates for testing project initiatives. This section has started with:
@hareesh added:
@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:
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:
@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:
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/..
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.
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 described that this is our time together to talk about things for our team: blockers, needs, roadmap, learning, docs, etc.
@boniu91 reminded, that there’s open poll to decide when we’ll be meeting in the future, twice a week:
@hellofromtonya asked to post the answers as comments inside the mentioned post.
@hellofromtonya described what is the goal:
And also what’s the current status:
CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. tests were blocked for over 2 years from running PHPUnit 8 and 9. They are not blocked anymore!!
@pbearne asked if we have any list of backports that needs to be finished
@hellofromtonya write a list of PRs:
There are 2 PRs for backports:
Plus, there’s still work to do in #53904
Also, the backports are waiting for PR 1587 to be fully reviewed and committed, we need to be sure that all paths are covered.
@lucatume offered, that he can take a look
@boniu91 asked if there’s any calendar with future WP Core releases
@francina answered that not yet
@pbearne asked what’s the plan for the @covers
@hellofromtonya answered that the plan for @covers is to address those during the reorganization and namespacing effort.
Why?
That’s when we’ll be thoroughly reviewing each test. At that point, we’ll know what each test is actually covering.
Why wait?
To avoid duplicating effort. We’re focusing first on PHP 8.1 and modernizing for latest PHPUnit. Once that’s done, then we plan to switch to the reorganization, namespacing, covers effort.
@hellofromtonya mentioned that there are many ways of contribution:
For those who don’t know how to build automated tests, you can contribute too:
@boniu91 commented that it would be good to have some kind of document that would describe the possible ways of contribution for new Test Team members.
Team agreed, @francina agreed to lead the effort, @hellofromtonya and @boniu91 offered help.
Test Team is meeting twice a week:
This schedule was discussed while ago, when the team wasn’t crystalized as it’s right now. This is why it’s a good time to ask members of this Team whether the time of meetings is okay, or shall we reschedule it.
Please post in the comments your opinion about that, we’ll be collecting votes until 30th of August and then make a decision.
Thank you for reading!
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.
Announcement starts here.
@hellofromtonya mentioned that two testers were nominated for this position to work together, both of them accepted the nomination, @hellofromtonya @boniu91
Team had no objections to those nominations
@hellofromtonya published and shared previously prepared introductions of newly nominated Test Team Reps
The discussion starts here.
@francina shared her list, people present on the meeting agreed:
@lucatume added, that’s not clear for him:
@hellofromtonya replied to the second point, saying that:
@lucatume expanded the previous (first) point and for the most effective contribution, the following things should be clear:
@hellofromtonya answered, that tickets with needs-unit-tests keyword are the ones for the PHPUnit side of things. We don’t have anything for the e2e tests though.
@lucatume suggested adding needs-e2e-tests keyword and the Team agreed that’d be useful.
@francina mentioned, that the current test setup is Jest + Puppeteer. We need developers to set up a tool for the Team that will make creating e2e tests easy.
Team agreed that it’s not possible to have 100% of automated tests, with no human review.
@francina shared what the Team needs right now to kick off the e2e testing:
@hellofromtonya said, that most likely, the bottleneck will be the group of automation test engineers to do the review, tuning, and maintenance work.
@lucatume explained how the “autogenerating” of e2e tests looks like (here)
@hellofromtonya confirmed the workflow:
Mai mentioned, that generated code can be worse in terms of quality than the one written by a human. Team agreed that it’ll need to be refined and maintained. @hellofromtonya shared improved workflow:
Team agreed to start a pilot initiative:
@lucatume will start creating the prototype
@francina offered reviewing the test handbooks
Here is the agenda for the upcoming Test Team Chat scheduled for 2021-08-03 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/..
A list of last week’s posts and live streams.
Posts:
Live streams:
custom_logo and option site_logoDo 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.
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: @bobbingwide @poena @jcasabona @richtabor @desrosj @paulbigai
Video Recording:
Topics Covered:
If you’re a theme author who has worked with 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. in some capacity, please fill out this theme survey.
#fse-hallway-hangout, #fse-outreach-program, #full-site-editingWith WordPress 5.8 came the official introduction of theme.json to the project allowing you to configure both existing editor settings like enabling custom colors and adopt new ones as they are released. Since this new mechanism is an early step towards a comprehensive style system for the future of WordPress, it’s important to hear from everyone who is currently using 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. to learn more about how folks are using this tool and what might make sense to include in CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. going forward.
If you’re a theme author who has used theme.json or is interested in doing so, please fill out this survey by August 13th to help shape its future.
If you haven’t yet used theme.json, this survey won’t be applicable to you. Thanks in advance for taking the time to share your thoughts! The results will be shared in a recap post.
If you’re curious about theme.json and haven’t had a chance to explore just yet, check out this previous call for testing offering different difficulty levels of flows and the latest WordPress News post on Configuring Theme Design with theme.json.
The meeting took place here in Slack. @hellofromtonya facilitated.
Discussion starts here in Slack.
A rep is an active team member who is reliable and trusted, advocates for and is knowledgeable of one or more areas of testing, and wants to represent, nurture, and grow the team to serve the WordPress project.
Action: @hellofromtonya to publish Call for Nominations once peer review is complete. ✅ Done.
Update: Here’s the post: Test Team Reps: Call for Nominations.
Discussion starts here in Slack.
Broadly testing entire release is hard to capture the feedback. Right? But testing something that has a ticket or Call for Test (CfT) is trackable for not only testers but the Core folks who are working on that thing under test. Sharing how you tested (the test environment, theme, plugins, etc.), steps you did, results, and maybe even a screenshare …. this type of info is valuable.
Commenting: “It works” is not as valuable as a feedback.
Action: @hellofromtonya will start a proposal for discussion:
laying out some guidelines for how testing is captured, what testing is not, and then that will guide everyone to know what a testing contribution is and isn’t.
Discussion starts here in Slack.
The Test Team has been without reps for years (see slack thread). With the team’s revival, it’s time to nominate (and then elect) team reps (i.e. an abbreviation for team representative).
tl;dr
Team reps are responsible for communicating on behalf of the team to the other contributor groups and teams via weekly updates and cross-team chats.
In the WordPress 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. project, each team has on average one or two reps. While some teams have more than two, I propose we stick with electing one to two reps for this term. For the historians out there, this role goes way back to 2012.
It is not called “team lead” for a reason. While people elected as team reps will generally come from the pool of folks that people think of as experienced leaders, remember that the 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. role is designed to change hands regularly.
Team Rep is a leadership role that is mostly administrative in nature; it is not a Lead role. Letting go of the Team Rep title is not a loss of status, just a handing off of responsibilities. Someone who is a leader in a team can lead whether they are doing the team rep job or not.
from Team Reps on Updates
A rep is an active team member who is reliable and trusted, advocates for and is knowledgeable of one or more areas of testing, and wants to represent, nurture, and grow the team to serve the WordPress open source project.
tl;dr
We nominate people in the comments of this post. You can write a comment as simple as “I nominate @the_persons_username.” Self-nominations are welcome by leaving a comment such as “I nominate myself.” If you want to nominate someone in private, please reach out to me (@hellofromtonya) on Slack.
The deadline for nominations is Monday, August 2.
Each person who is nominated will be contacted to discuss qualifications and to accept or decline their nomination.
If you get nominated, please do not feel like you have to say “yes”! It’s okay for you to decline the nomination if you don’t feel like this is the right fit for any reason. “Thank you, but no thank you” 😉
If there are enough accepted nominations that an election is necessary, then we’ll use an anonymous poll for the election (example). The poll will remain open for 2 weeks.
Once the results are done, the new team rep(s) will be announced in a post (example).
Ready? It’s time to nominate people to serve for a year as our Test Team Reps.
If you have any questions, please feel free to ask in the comments. Happy nominating!
