The automated testing team is responsible for different kind of tests which can be run in an automated way. Mainly they are executed when authors offer code changes on Github. Here a few intersting stats about the current status:
Code style checks do help to have a unique code style accross the whole code base.
Integration and unit tests are low lewel code tests, which are testing parts of our code.
System tests are real browser tests and do test the
...Duration: 20mins
...Present: Herman, Benjamin, Martin, Shirielle, Olivier
Objective:
Joomla Health Checker, PBF and GSoC updates.
Item discussed:
- Health Checker: Creation of PRs towards the 6.2-dev branch to collect feedback Check joomla-projects/HealthChecker.
Next Meeting: 2026-04-06 1500 UTC
Attendees: Anja de Crom, Claudia Weber-Lenck,Dan Atrill, Emmanuel Lemor, Brian Teeman, Christiane Maier-Stadtherr, Viviana Menzel, Serge Billon, Herman Peeren
This was a chat meeting to go collect ideas for the April issue. After the idea-collecting, we had a lively discussion about AI. Some of us don't care if a text is AI generated or not, others (including me) prefer content written by humans for humans. In our guidelines we clearly state authors can't use AI to write their content for them. So the idea was to discuss what we can and can't use it for. No verdict has been reached yet for that one, although we heard several people say
...Period: July 2024 - March 2026 Author: Phil Walton Date: 25 March 2026
Since the last report (June 2024), the CMS Maintenance Team has continued its weekly Wednesday meetings, reviewing and processing pull requests across the Joomla CMS repository. This report provides a factual summary of PR activity over the 21-month period.