rozbehsharahi/tester3

Testing-Framework for TYPO3

v1.1.0 2024-01-24 23:25 UTC

Requires

• php: ^7.4 || ^8.0
• ext-json: *
• phpstan/phpstan: ^1
• phpunit/phpunit: ^9 || ^10
• typo3/cms-backend: ^11.5 || ^12
• typo3/cms-core: ^11.5 || ^12
• typo3/cms-extensionmanager: ^11.5 || ^12
• typo3/cms-felogin: ^11.5 || ^12
• typo3/cms-fluid-styled-content: ^11.5 || ^12
• typo3/cms-frontend: ^11.5 || ^12
• typo3/cms-install: ^11.5 || ^12
• typo3/cms-lowlevel: ^11.5 || ^12
• typo3/cms-rte-ckeditor: ^11.5 || ^12
• typo3/cms-tstemplate: ^11.5 || ^12

MIT

• Rozbeh Chiryai Sharahi

README

Tester3 is an approach for a more simple integration of functional tests for TYPO3 pages. I simple find TYPO3's testing-framework a bit messy.

This extension is currently work in progress.

The idea is to be able to create an encapsulated test-app scope on every test, which can than be filled with data and tested against.

Every scope has its own sqlite-database, site-config and typo3-settings and leads ideally to full determinism.

Installation

composer require --dev rozbehsharahi/tester3

Usage

use Rozbehsharahi\Tester3\Builder\FunctionalScopeBuilder;

class FunctionalScopeBuilderTest extends TestCase
{
    private FunctionalScopeBuilder $scopeBuilder;

    public function setUp(): void
    {
        $this->scopeBuilder = (new FunctionalScopeBuilder())
            ->withVendorPath(__DIR__ . '/../../vendor');
    }

    public function testCanCreateScopeAndAccessibleHomepage(): void
    {
        $scope = $this->scopeBuilder->build();

        self::assertSame('root page', $scope->getRecord('pages', 1)['title']);
        self::assertSame(200, $scope->request('/')->getStatusCode());
    }
}

Todos

• Write docker env for contribution
• Test on TYPO3 11
• Introduce CI-testing
• Introduce phpstan
• Introduce code-sniffer
• More tests
• setup test database only once before all tests and then copy to every scope (performance)