mirror of
https://github.com/FriendsOfTYPO3/tea.git
synced 2024-11-15 15:36:12 +01:00
Mirror of TYPO3 Extension tea, managed by the Best Practice Team
https://typo3.org/community/teams/best-practices
71bc7e137d
This change adopts the well known runTests.sh from TYPO3 core
and related extensions as basic scripts and test execution
center. Main benefit of this implemenation is, that these
commands are behaving the same on all systems and ci, thus
increasing interoperability and easier transforming of commands
between systems - which ease the way to rerun or debug failed
tests locally after detected in ci (GitHub Actions, Gitlab CI).
Available suits and options are aligned to this project needs,
and will be updated if needed. To display available commands:
```shell
Build/Scripts/runTests.sh -h
```
Generic tasks and options (incomplete):
* `-s composerInstall` normal install, for code quality checks
* `-s composerInstallLowest` and `-s composerInstallHighest` to
install dependencies with lowest and highest possibilities for
all dependencies, based on selected php-version, core-version
and so on. This helps to build fast a wide range of testing
matrix for unit- and functional tests
* `-p <7.4|8.0|8.1|8.2>` defines which php version is used for
executed php and composer scripts, like unit or functional
tests, composer installs and so on
* ensure support for following databases for functional tests:
- postgres <10|11|12|13|14> default: 10
- mysql <5.5|5.6|5.7|8.0> default: 5.5
- mariadb <10.2|10.3|10.4|10.5|10.6|10.7> default: 10.2
- sqlite
This can be controlled with a couple of options:
-d <sqlite|mariadb|mysql|postgres>
-a <mysqli|pdo_mysql> (for -d mysql or -d mariadb)
-i <10.2|10.3|10.4|10.5|10.6|10.7> (for -d mariadb)
-j <5.5|5.6|5.7|8.0> (for -d mysql)
-k <10|11|12|13|14> (for -d postgres)
* selection of core can be choosen with the `-t` flag,
also only v11 currently available. This is already
a preparation for multi-core testing or for further
version shiftings.
* included cgl (php cs fixer) with dryrun as suite
* add phpstan and phpstan generate baseline suites
Resolves #94
|
||
|---|---|---|
| .ddev | ||
| .github | ||
| .gitlab | ||
| Build | ||
| Classes | ||
| Configuration | ||
| Documentation | ||
| Resources | ||
| Tests | ||
| tools | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitattributes | ||
| .gitignore | ||
| .php-cs-fixer.php | ||
| .phpstorm.meta.php | ||
| .prettierrc.js | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| composer.json | ||
| ext_emconf.php | ||
| ext_localconf.php | ||
| ext_tables.sql | ||
| LICENSE | ||
| package.json | ||
| phive.xml | ||
| phpcs.xml | ||
| phpstan-baseline.neon | ||
| phpstan.neon | ||
| README.md | ||
| stylelint.config.js | ||
Example TYPO3 extension for code quality checks and automated tests
This TYPO3 extension, based on Extbase and Fluid, is an example of best practices in automated code checks, unit/functional/acceptance testing and continuous integration.
You can also use this extension to manage your collection of delicious teas.
Presentation at the TYPO3 Online Days 2021
At the TYPO3 Online Days 2021, Oliver Klee held a session where her presented our approach for automating the code quality of extensions.
Slides
Video recording
