Test Failed
Push — master ( bc5b04...424213 )
by Hannes
03:21
created

NamespaceNameSpec::it_is_initializable()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 3
Code Lines 1

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 1
eloc 1
nc 1
nop 0
dl 0
loc 3
rs 10
c 0
b 0
f 0
1
<?php
2
3
declare(strict_types = 1);
4
5
namespace spec\hanneskod\readmetester\Name;
6
7
use hanneskod\readmetester\Name\NamespaceName;
8
use hanneskod\readmetester\Name\NameInterface;
9
use PhpSpec\ObjectBehavior;
0 ignored issues
show
Bug introduced by
The type PhpSpec\ObjectBehavior was not found. Maybe you did not declare it correctly or list all dependencies?

The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g. excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:

filter:
    dependency_paths: ["lib/*"]

For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths

Loading history...
10
use Prophecy\Argument;
0 ignored issues
show
Bug introduced by
The type Prophecy\Argument was not found. Maybe you did not declare it correctly or list all dependencies?

The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g. excluded_paths: ["lib/*"], you can move it to the dependency path list as follows:

filter:
    dependency_paths: ["lib/*"]

For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths

Loading history...
11
12
class NamespaceNameSpec extends ObjectBehavior
13
{
14
    function let()
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
15
    {
16
        $this->beConstructedWith('namespace');
17
    }
18
19
    function it_is_initializable()
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
20
    {
21
        $this->shouldHaveType(NamespaceName::CLASS);
0 ignored issues
show
Bug introduced by
The constant hanneskod\readmetester\Name\NamespaceName::CLASS was not found. Maybe you did not declare it correctly or list all dependencies?
Loading history...
22
    }
23
24
    function it_is_a_name()
25
    {
26
        $this->shouldHaveType(NameInterface::CLASS);
0 ignored issues
show
Bug introduced by
The constant hanneskod\readmetester\Name\NameInterface::CLASS was not found. Maybe you did not declare it correctly or list all dependencies?
Loading history...
27
    }
28
29
    function it_contains_a_namespace()
30
    {
31
        $this->getNamespaceName()->shouldReturn('namespace');
32
    }
33
34
    function it_does_not_contain_a_short_name()
35
    {
36
        $this->shouldThrow(\RuntimeException::CLASS)->during('getShortName');
0 ignored issues
show
Bug introduced by
The constant RuntimeException::CLASS was not found. Maybe you did not declare it correctly or list all dependencies?
Loading history...
37
    }
38
39
    function it_does_not_contain_a_complete_name()
40
    {
41
        $this->shouldThrow(\RuntimeException::CLASS)->during('getName');
0 ignored issues
show
Bug introduced by
The constant RuntimeException::CLASS was not found. Maybe you did not declare it correctly or list all dependencies?
Loading history...
42
    }
43
}
44