digitalrevolution/phpunit-extensions

A library for phpunit utility and support classes

v1.5.2 2024-09-24 17:16 UTC

Requires

• php: ^8.1
• phpunit/phpunit: ^9.5.24 || ^10.0 || ^11.0

Requires (Dev)

• digitalrevolution/phpunit-file-coverage-inspection: ^2.0
• phpmd/phpmd: ^2.12
• phpstan/extension-installer: ^1.2
• phpstan/phpstan: ^1.9.1
• phpstan/phpstan-phpunit: ^1.2.2
• phpstan/phpstan-strict-rules: ^1.5
• phpstan/phpstan-symfony: ^1.2.16
• roave/security-advisories: dev-latest
• squizlabs/php_codesniffer: ^3.7
• symfony/form: ^6.0||^7.0
• symfony/framework-bundle: ^6.0||^7.0
• symfony/security-core: ^6.0||^7.0
• symfony/twig-bundle: ^6.0||^7.0
• symfony/validator: ^6.0||^7.0

Suggests

• symfony/form: Symfony form component is required for testing the controller createForm methods
• symfony/framework-bundle: Symfony framework bundle is required for the AbstractControllerTestCase
• symfony/security-core: Symfony security component is required for testing authentication/authorization related methods
• symfony/twig-bundle: Symfony twig bundle is required to test rendering templates/forms

Conflicts

• symfony/form: <6.0
• symfony/framework-bundle: <6.0
• symfony/security-core: <6.0
• symfony/twig-bundle: <6.0

MIT

README

PHPUnit extensions

Utility classes to make unit testing life easier.

Features

withConsecutive

In PHPUnit 10 withConsecutive method was removed. To still be able to migrate existing codebases a replacement method:

PHPUnit <= 9.5:

$mock->method('myMethod')->withConsecutive([123, 'foobar'], [456]);

PHPUnit >= 9.6:

$mock->method('myMethod')->with(...consecutive([123, 'foobar'], [456]));

Symfony controller tests

Testing a Symfony controller internally invokes the dependency container. A utility class to mock these classes more easily.

use DR\PHPUnitExtensions\Symfony\AbstractControllerTestCase;

class MyControllerTest extends AbstractControllerTestCase 
{    
    public function myTest(): void 
    {
        $this->expectDenyAccessUnlessGranted('attribute', null, true);
        $this->expectGetUser(new User());
        $this->expectCreateForm(TextType::class);
        
        ($this->controller)();    
    }
    
    public function getController() {
        return new MyController();    
    }    
}

Methods

• expectGetUser
• expectDenyAccessUnlessGranted
• expectCreateForm
• expectAddFlash
• expectGenerateUrl
• expectRedirectToRoute
• expectForward
• expectRender

Symfony ConstraintValidator tests

TestCase for testing Symfony ConstraintValidators.

use DR\PHPUnitExtensions\Symfony\AbstractConstraintValidatorTestCase;

class MyConstraintValidatorTest extends AbstractConstraintValidatorTestCase 
{    
    public function testValidate(): void
    {
        $this->expectBuildViolation($constraint->message, ['parameter' => 123])
            ->expectSetCode(789)
            ->expectAtPath('path')
            ->expectAddViolation();

        $this->validator->validate(123, $this->constraint);
    }
    
    protected function getValidator(): ConstraintValidator
    {
        return new MyConstraintValidator();
    }

    protected function getConstraint(): Constraint
    {
        return new MyConstraint();
    }
}

Methods

• assertHandlesIncorrectConstraintType
• expectNoViolations
• expectBuildViolation(): ConstraintViolationBuilderAssertion

ConstraintViolationBuilderAssertion

• expectSetInvalidValue
• expectSetPlural
• expectSetCode
• expectSetCause
• expectSetTranslationDomain
• expectSetParameters
• expectSetParameter
• expectSetParameterWithConsecutive
• expectAtPath
• expectAddViolation

ResponseAssertions trait

The ResponseAssertions trait provides a set of assertion methods designed to streamline the testing of Symfony HTTP responses. This trait includes methods for verifying the status code, response message content and specific types of responses such as JSON responses

Methods

• assertJsonResponse
• assertResponse
• assertResponseIsSuccessful
• assertResponseIsRedirection
• assertResponseIsClientError
• assertResponseIsServerError

About us

At 123inkt (Part of Digital Revolution B.V.), every day more than 50 development professionals are working on improving our internal ERP and our several shops. Do you want to join us? We are looking for developers.