This is a TYPO3 distribution which I use to manually test my extensions:
- feuserextrafields (once it supports TYPO3 13LTS)
- oelib (once it supports TYPO3 13LTS)
- onetimeaccount (once it supports TYPO3 13LTS)
- seminars (once it supports TYPO3 13LTS)
- tea (once it supports TYPO3 13LTS)
This distribution uses ddev.
ddev start
ddev composer install
ddev install-typo3There are two commands available for dumping the database and for importing the
dump to and from the file dump.sql:
ddev db-dump
ddev db-importThe dump includes (and hence overwrite on import) FE users and FE user groups, but not BE users or BE user groups. (So it is safe to add BE users and then run the import.)
To test a local copy of an extension in this distribution, you can do one of the following (or a combination):
- Put the extension folders in
src/extensions/. - Mount the extension directories via Docker. For this, create the file
.ddev/docker-compose.packages.yamlas a copy of.ddev/docker-compose.packages.yaml.templateand modify it to your needs.
The DDEVd documentation provides very good step-by-step instructions for the Docker setup in PhpStorm.
After that, you need to configure the PhpStorm templates for PHPUnit tests:
- Configuration file:
config/UnitTests.xml - Environment variables:
typo3DatabaseUsername=root;typo3DatabaseHost=db;TYPO3_PATH_WEB=public/;typo3DatabaseName=typo3_test;typo3DatabasePassword=root
Also, config/UnitTests.xml is the configuration file for unit tests,
while config/FunctionalTests.xml is the corresponding file for functional
tests.
- Backend:
ddev launch typo3
- Frontend (DE):
ddev launch
- Frontend (EN): https://typo3-testing-10-4-en.ddev.site:8081/
- MailHog:
ddev launch -m
Backend admin: admin / Password1!
Install tool password: Password1!
Frontend users:
attendee/attendeeeditor/editormanager/manageradmin/password(with all three of the above roles combined)