jaroslavtyc/drd-plus-health

View on GitHub
tests/Health/TreatmentBoundaryTest.php

Summary

Maintainability
A
0 mins
Test Coverage

Avoid using static access to class '\DrdPlus\Health\TreatmentBoundary' in method 'I_can_not_use_negative_value'.
Open

        TreatmentBoundary::getIt(-1);

StaticAccess

Since: 1.4.0

Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

Example

class Foo
{
    public function bar()
    {
        Bar::baz();
    }
}

Source https://phpmd.org/rules/cleancode.html#staticaccess

Avoid using static access to class '\DrdPlus\Health\TreatmentBoundary' in method 'I_am_stopped_by_specific_exception_on_invalid_value'.
Open

        TreatmentBoundary::getIt('Why you ask me?');

StaticAccess

Since: 1.4.0

Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

Example

class Foo
{
    public function bar()
    {
        Bar::baz();
    }
}

Source https://phpmd.org/rules/cleancode.html#staticaccess

Avoid using static access to class '\DrdPlus\Health\TreatmentBoundary' in method 'I_can_create_treatment_boundary'.
Open

        $treatmentBoundary = TreatmentBoundary::getIt($value = 0);

StaticAccess

Since: 1.4.0

Static access causes unexchangeable dependencies to other classes and leads to hard to test code. Avoid using static access at all costs and instead inject dependencies through the constructor. The only case when static access is acceptable is when used for factory methods.

Example

class Foo
{
    public function bar()
    {
        Bar::baz();
    }
}

Source https://phpmd.org/rules/cleancode.html#staticaccess

The method I_can_not_use_negative_value is not named in camelCase.
Open

    public function I_can_not_use_negative_value(): void
    {
        $this->expectException(\DrdPlus\Health\Exceptions\TreatmentBoundaryCanNotBeNegative::class);
        $this->expectExceptionMessageMatches('~-1~');
        TreatmentBoundary::getIt(-1);

CamelCaseMethodName

Since: 0.2

It is considered best practice to use the camelCase notation to name methods.

Example

class ClassName {
    public function get_name() {
    }
}

Source

The method I_am_stopped_by_specific_exception_on_invalid_value is not named in camelCase.
Open

    public function I_am_stopped_by_specific_exception_on_invalid_value(): void
    {
        $this->expectException(\DrdPlus\Health\Exceptions\TreatmentBoundaryCanNotBeNegative::class);
        $this->expectExceptionMessageMatches('~Why you ask me?~');
        TreatmentBoundary::getIt('Why you ask me?');

CamelCaseMethodName

Since: 0.2

It is considered best practice to use the camelCase notation to name methods.

Example

class ClassName {
    public function get_name() {
    }
}

Source

The method I_can_create_treatment_boundary is not named in camelCase.
Open

    public function I_can_create_treatment_boundary(): void
    {
        $treatmentBoundary = TreatmentBoundary::getIt($value = 0);
        self::assertSame($value, $treatmentBoundary->getValue());
    }

CamelCaseMethodName

Since: 0.2

It is considered best practice to use the camelCase notation to name methods.

Example

class ClassName {
    public function get_name() {
    }
}

Source

There are no issues that match your filters.

Category
Status