!!! Original Repository on: https://codeberg.org/kiesi/t3static !!!

Mirror only on Github: https://github.com/thomaskieslich/t3static

Collection of Tools to Test, Lint, Fix, and Upgrade multiple TYPO3 Extensions in a Monorepo. The rules are simple to bring the code in the individual extensions up to the same level.

This is to have the most uniform code standards possible for projects with many custom extensions. It can recognise and fix simple problems in the code. Use in continuous integration pipelines is possible. A special goal of this tool collection is to test TYPO3 extensions without great effort and adjustments in the code. This Tool has its own node_modules and vendor Settings and Folders.

Download the package as zip to your project root and unzip. Rename the Folder to t3static. You can move the folder to a subfolder like tests/t3static, but then you must change the TEST_PATH in .env File.

1. Add this to your root .gitignore

   # t3static https://github.com/thomaskieslich/t3static
   /t3static

2. Clone the Repository

git clone [email protected]:thomaskieslich/t3static.git

You can just run ./t3static/run dockeror ./t3static/run local. If .env not exists a copy from .env.dist will be created. If used Tools (composer, npm) not exist, they will be installed automatically.

If you want to change the configuration before the first run, copy t3static/.env.dist

Run inside a docker container (recommended). So you can run the Tools independently of your local php and node versions. It builds the docker image once for use in all Projects.

./t3static/run-docker

If Tools Versions are changed, you should rebuild the Docker Image with:

./t3static/run-docker --rebuild

Your local Environment should have these versions: php 8.3 - 8.4 node v22 - v24 composer 2 Test run quicker, but not so stable.

./t3static/run-local

To Rebuild Tools, just delete node_modules and vendor Folder and rerun.

• Load Environment Variables
• Install Script
• Load tests from the includes Folder
• Define Test Options and Groups

Available groups (usage -t GROUP)

• frontend
• misc
• php
• typo3

For single tests have a look into the includes folder. The files are based on the group names.

Here are the configuration files for the single tests from the includes folder. If you want to override, make a copy like config-override and change the CONFIGURATION_PATH in the .env file.

Here the results from some tests are written (php-stan,…)

You can run test groups like:

./t3static/run-docker -t frontend
./t3static/run-docker -t misc
./t3static/run-docker -t php
./t3static/run-docker -t typo3

or single tests like (more tests defined in t3static):

./t3static/run-docker -t css
# fix it
./t3static/run-docker -t css-fix

./t3static/run-docker -t rector
./t3static/run-docker -t typo3scan

or multiple, comma-separated Tests like

./t3static/run -t css,js

./t3static/run -t fractor,rector

choose test
-t ***testname***

set Extensionname (folder name)
-p ***extension

list all available test types
--list-tests

If you don’t define the test and the package as arguments or in the .env file, a prompt will ask you what to update. You may omit neither, both, or just one of the arguments. The priority order is:

1. CLI argument
2. .env file
3. Prompt

./t3static/run-docker

==> PACKAGE_NAME is empty.

==> Please choose a folder:

  1) package_1
  2) package_2
  3) sitepackage
Enter number (1-3):

==> TEST_TYPE is empty.

==> Please choose a test:

  1) all
  2) backend
  3) composer
  4) css
  ...
Enter number (1-x):

Frontend Tests

Misc Tests

PHP Tests

TYPO3 Tests

• Prettier for Styles and JavaScript
• linter for SQL
• Override Single Configurations
• add Tests to github actions