oliverklee/seminars

TYPO3 extension that allows you to create and manage a list of seminars, workshops, lectures, theater performances and other events, allowing front-end users to sign up. FE users also can create and edit events.

TYPO3 extension seminars

, _(*1)

This TYPO3 extension allows you to create and manage a list of seminars, workshops, lectures, theater performances and other events, allowing front-end users to sign up., _(*2)

Most of the documentation is in ReST format in the Documentation/ folder and is rendered as part of the TYPO3 documentation., _(*3)

Compatibility with TYPO3 12LTS/12.4

A TYPO3-12LTS-compatible version of this extension is available via an early-acces program., _(*4)

Give it a try!

If you would like to test the extension yourself, there is a DDEV-based TYPO3 distribution with this extension installed and some test records ready to go., _(*5)

Staying informed about the extension

If you would like to stay informed about this extension (including compatibility with newer TYPO3 versions), you can subscribe to the author's newsletter., _(*6)

Running the tests locally

You will need to have a Git clone of the extension for this with the Composer dependencies installed., _(*7)

Running the unit tests

On the command line

To run all unit tests on the command line:, _(*8)

composer ci:tests:unit

To run all unit tests in a directory or file (using the directory Tests/Unit/Model/ as an example):, _(*9)

.Build/vendor/bin/phpunit -c Configuration/UnitTests.xml Tests/Unit/Model/

In PhpStorm

First, you need to configure the path to PHPUnit in the settings:, _(*10)

Languages & Frameworks > PHP > Test Frameworks, _(*11)

In this section, configure PhpStorm to use the Composer autoload and the script path .Build/vendor/autoload.php within your project., _(*12)

In the Run/Debug configurations for PHPUnit, use an alternative configuration file:, _(*13)

Configuration/UnitTests.xml, _(*14)

Running the functional tests

You will need a local MySQL user that has the permissions to create new databases., _(*15)

In the examples, the following credentials are used:, _(*16)

• user name: typo3
• password: typo3pass
• DB name prefix: typo3_test (optional)
• DB host: localhost (omitted as this is the default)

You will need to provide those credentials as environment variables when running the functional tests:, _(*17)

• typo3DatabaseUsername
• typo3DatabasePassword
• typo3DatabaseName

On the command line

To run all functional tests on the command line:, _(*18)

typo3DatabaseUsername=typo3 typo3DatabasePassword=typo3pass typo3DatabaseName=typo3_test composer ci:tests:functional

To run all functional tests in a directory or file (using the directory Tests/Functional/Authentication/ as an example):, _(*19)

typo3DatabaseUsername=typo3 typo3DatabasePassword=typo3pass typo3DatabaseName=typo3_test .Build/vendor/bin/phpunit -c Configuration/FunctionalTests.xml Tests/Functional/Authentication/

In PhpStorm

First, you need to configure the path to PHPUnit in the settings:, _(*20)

Languages & Frameworks > PHP > Test Frameworks, _(*21)

In this section, configure PhpStorm to use the Composer autoload and the script path .Build/vendor/autoload.php within your project., _(*22)

In the Run/Debug configurations for PHPUnit, use an alternative configuration file:, _(*23)

Configuration/FunctionalTests.xml, _(*24)

Also set the following environment variables in your runner configuration:, _(*25)

• typo3DatabaseUsername
• typo3DatabasePassword
• typo3DatabaseName

Running the legacy functional tests

Running the legacy tests works exactly the same as running the functional tests, except that you run the tests in Tests/LegacyFunctional/ instead of Tests/Functional/. You'll still need to use the configuration file Configuration/FunctionalTests.xml, though., _(*26)