EnforcementTest::testInvalidEnforce() - Code Metrics - Inspection of "Merge pull request #2 from Dgame/analysis-qrvvrg" - Dgame/php-ensurance - Measure and Improve Code Quality continuously with Scrutinizer

Test Failed

Retried Inspection

Branch — master (5e8424)

by Randy

created 2017-04-30 20:48 UTC

EnforcementTest::testInvalidEnforce() A

↳ Parent: EnforcementTest

Complexity

Conditions	1
Paths	1

Size

Total Lines	7
Code Lines	4

Duplication

Lines	0
Ratio	0 %

Importance

Changes

Metric	Value
cc	1
eloc	4
nc	1
nop	0
dl	0
loc	7
rs	9.4285
c	0
b	0
f	0

<?php

use Dgame\Ensurance\Exception\EnsuranceException;
use PHPUnit\Framework\TestCase;
use function Dgame\Ensurance\enforce;

class FooException extends Exception
namespace YourVendor;

class YourClass { }
{
}

class EnforcementTest extends TestCase
namespace YourVendor;

class YourClass { }
{
    public function testValidEnforce()
    {
        enforce(true)->orThrow('That is not true?!');
    }

    public function testInvalidEnforce()
    {
        $this->expectException(EnsuranceException::class);
        $this->expectExceptionMessage('That is false');

        enforce(false)->orThrow('That is false');
    }

    public function testInvalidEnforceWithException()
    {
        $this->expectException(FooException::class);
        $this->expectExceptionMessage('That is false');

        enforce(false)->orThrow(new FooException('That is false'));
    }
}

1			<?php
2
3			use Dgame\Ensurance\Exception\EnsuranceException;
4			use PHPUnit\Framework\TestCase;
5			use function Dgame\Ensurance\enforce;
6
7			class FooException extends Exception
			0 ignored issues – show Coding Style Compatibility introduced 2017-04-30 20:50 UTC by Report Bug Copy Issue Report PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions. You can fix this by adding a namespace to your class: namespace YourVendor; class YourClass { } When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries. Loading history...
8			{
9			}
10
11			class EnforcementTest extends TestCase
			0 ignored issues – show Coding Style Compatibility introduced 2017-04-30 20:50 UTC by Report Bug Copy Issue Report PSR1 recommends that each class should be in its own file to aid autoloaders. Having each class in a dedicated file usually plays nice with PSR autoloaders and is therefore a well established practice. If you use other autoloaders, you might not want to follow this rule. Loading history... Coding Style Compatibility introduced 2017-04-30 20:50 UTC by Report Bug Copy Issue Report PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions. You can fix this by adding a namespace to your class: namespace YourVendor; class YourClass { } When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries. Loading history...
12			{
13			public function testValidEnforce()
14			{
15			enforce(true)->orThrow('That is not true?!');
16			}
17
18			public function testInvalidEnforce()
19			{
20			$this->expectException(EnsuranceException::class);
21			$this->expectExceptionMessage('That is false');
22
23			enforce(false)->orThrow('That is false');
24			}
25
26			public function testInvalidEnforceWithException()
27			{
28			$this->expectException(FooException::class);
29			$this->expectExceptionMessage('That is false');
30
31			enforce(false)->orThrow(new FooException('That is false'));
32			}
33			}

Dgame / php-ensurance

Branch — master (5e8424)

EnforcementTest::testInvalidEnforce() A

Complexity

Size

Duplication

Importance

Duplication Side-by-Side

Filter issues like