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.
@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
@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
@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
If anyone’s interested in writing tests please leave comment either on Slack or in ticket itself.