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.
Short explanation for first time attendees
@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.
Week in Test introduction
@hellofromtonya described the purpose of this weekly publication, in short, it includes:
- Parts of the core where testing help is needed this week
- Learning and reading opportunities
Team agreed that it’s very helpful.
Last week’s Team update introduction
@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.
Focal group updates
@hellofromtonya explained that it’s a time for testers to share updates for testing project initiatives. This section has started with:
- 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. 8.1 fixes are underway
- Modernization to Latest PHPUnit project is nearly finished. Backporting is next, then dev note
- PHPUnit Test modernization is ongoing
- The latest version of jQuery UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. was recently merged to Core. Need a lot of testing.
@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:
- Local machine setups
- How to do different types of testing
- How to create test reports
Team agreed that this documentation should be present in Make Test website, Make Core should only refer to it.
@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:
- Start with Docker
- Setups on Make Test with reference in Make Core
- Figure out the doc info structure / strategy
- Doc for different OS: Windows, Mac, and Linux
- Link to tooling’s official docs
- Get feedback from contributors
People with different OS will be essential for the successful meeting.