Report From the TYPO3 Quality Assurance Initiative

 

 

The whole outcome, and current process, is available as an example extension at gitlab.typo3.org and github.com.

This report will only cover the biggest topics, not every single change.

First Stable Release v1.0.0

A first stable public release was done. The extension will follow semantic versioning to align with best practices.

TYPO3 v11 LTS Support

Version v1.1.0 is compatible with TYPO3 v11 LTS. Version v2.0.0 will drop support for TYPO3 v9 LTS in order to support the last two TYPO3 LTS versions.

Presenting Results at TYPO3 Online Days 2021

Oliver Klee gave a presentation titled Automating the Code Quality of Your Extensions at the TYPO3 Online Days 2021, during which he demonstrated our results. The full video is available on YouTube at.

Easier Re-Use of GitLab Jobs

Jobs that build pipelines on GitLab are now split into separate files, available at git.typo3.org.

That allows for easier re-use. Users can easily get an overview, and copy or reference those files.

Code Coverage

A basic version of code coverage was added to the project. We are still working on a better integration with proper coverage reporting as well as detection of a drop in coverage during pipeline execution. The current coverage report combines reports from unit as well as functional tests.

PHPStan

Some developers might already use PHPStan. It is a static code analysis to support developers in writing more robust PHP Code. This tool has already been in use by TYPO3 Core for some time and is now integrated into the extension.

typo3/coding-standards

We switched to the existing composer package typo3/coding-standards which allows us to re-use the official standards without maintaining another custom setup. All developers could focus on real value instead of CGL if all extensions worked this way. Reading would always be the same as all would apply the same CGL.

Thanks to the Team

Let us all say thanks to the Association and community for sponsoring the work. And also thanks to the people who actually did the work who were: ?ukasz Uzna?ski and Oliver Klee.

In total we spent €4,378.25 of our €7,500.00 budget during the year. All the money was spent to compensate for the working time of the two people actively integrating and reviewing all the code.

2022 Outlook

We plan to continue our work with another budget application. The focus in 2022 will shift towards best practices for projects, instead of extensions. We are looking forward to working together with existing teams and joining forces to use demo.typo3.org as best practice for projects.

We will stick to our 100% remote working mode due to the ongoing pandemic. All budget will be spent again on compensating the working time.

Your Feedback

We hope you find the current outcome helpful. You are free to open issues on the repositories, we prefer the GitHub repository for issues. And you are free to join the Slack channel #qa-best-practices.