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.

Explanation for first time attendees, what is the Test Team Chat?

@hellofromtonya described that this is our time together to talk about things for our team: blockers, needs, roadmap, learning, docs, etc.

Reminder about the poll related to schedule fo our meetings

@boniu91 reminded, that there’s open poll to decide when we’ll be meeting in the future, twice a week:

• Tuesday meeting
• Friday test scrub session

@hellofromtonya asked to post the answers as comments inside the mentioned post.

Update: Modernize to Latest PHPUnit work

@hellofromtonya described what is the goal:

• Run on the latest PHPUnit version
• Use the PHPUnit Polyfills to shim backwards for backwards-compatibility (which enables 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. cross-version testing using the matching PHPUnit version)
• etc

And also what’s the current status:

• All supported PHP versions are now running with their matching PHPUnit version 
• Old workarounds are removed 
• Tests are running on PHP 8.1 
• The test suite’s assertions and expectations have been updated to PHPUnit 9.x 
• Backports are in progress
• Dev Note is in progress and should be out very soon

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:

• WP 5.2 to 5.8 – PR 1588
• <= WP 5.1 – PR 1589
• Backport for wp_readonly() – PR 1590

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

Open Floor

@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.

Ways of contribution

@hellofromtonya mentioned that there are many ways of contribution:

• On the PHP side of things, there’s about ~10% code coverage in the automated tests.
• Adding more unit and integration tests will also help the e2e effort too.
• Once we get the tests modernized, then comes: improving the docs

For those who don’t know how to build automated tests, you can contribute too:

• Help identify if there’s a test for a function or public method
• If not, create a new ticket for it

@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.

#build-test-tools