Test Failed
Push — master ( 7567e5...7000c2 )
by Jean-Bernard
02:02
created

containerCanBeCreated()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 8
Code Lines 4

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
dl 0
loc 8
rs 9.4285
c 0
b 0
f 0
cc 1
eloc 4
nc 1
nop 0
1
<?php
2
3
/*
4
 * This file is part of the Symfony-Util package.
5
 *
6
 * (c) Jean-Bernard Addor
7
 *
8
 * For the full copyright and license information, please view the LICENSE
9
 * file that was distributed with this source code.
10
 */
11
12
use PHPUnit\Framework\TestCase;
13
use Symfony\Bridge\Twig\TwigEngine;
14
// use Symfony\Bundle\FrameworkBundle\Controller\ControllerResolver; // Do not know how to configure this.
15
use Symfony\Component\DependencyInjection\ContainerBuilder;
16
use Symfony\Component\EventDispatcher\EventDispatcher;
17
use Symfony\Component\HttpFoundation\Request;
18
use Symfony\Component\HttpFoundation\RequestStack;
19
use Symfony\Component\HttpFoundation\Response;
20
use Symfony\Component\HttpKernel\Controller\ArgumentResolver;
21
use Symfony\Component\HttpKernel\Controller\ContainerControllerResolver;
22
use Symfony\Component\HttpKernel\EventListener\ResponseListener;
23
use Symfony\Component\HttpKernel\EventListener\RouterListener;
24
use Symfony\Component\HttpKernel\HttpKernel;
25
use Symfony\Component\Routing\Matcher\UrlMatcher;
26
use Symfony\Component\Routing\RequestContext;
27
use Symfony\Component\Routing\RouteCollectionBuilder;
28
use Symfony\Component\Templating\EngineInterface;
29
use Symfony\Component\Templating\TemplateNameParser;
30
use Symfony\Component\Templating\TemplateNameParserInterface;
31
use SymfonyUtil\Controller\EngineAsArgumentController;
32
use Tests\Component\AppKernel;
0 ignored issues
show
Bug introduced by
This use statement conflicts with another class in this namespace, AppKernel.

Let’s assume that you have a directory layout like this:

.
|-- OtherDir
|   |-- Bar.php
|   `-- Foo.php
`-- SomeDir
    `-- Foo.php

and let’s assume the following content of Bar.php:

// Bar.php
namespace OtherDir;

use SomeDir\Foo; // This now conflicts the class OtherDir\Foo

If both files OtherDir/Foo.php and SomeDir/Foo.php are loaded in the same runtime, you will see a PHP error such as the following:

PHP Fatal error:  Cannot use SomeDir\Foo as Foo because the name is already in use in OtherDir/Foo.php

However, as OtherDir/Foo.php does not necessarily have to be loaded and the error is only triggered if it is loaded before OtherDir/Bar.php, this problem might go unnoticed for a while. In order to prevent this error from surfacing, you must import the namespace with a different alias:

// Bar.php
namespace OtherDir;

use SomeDir\Foo as SomeDirFoo; // There is no conflict anymore.
Loading history...
33
34
/**
35
 * @covers \SymfonyUtil\Controller\EngineAsArgumentController
36
 */
37
final class EngineAsArgumentInKernelControllerTest extends TestCase
0 ignored issues
show
Coding Style Compatibility introduced by
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...
38
{
39
    public function testCanBeCreated()
40
    {
41
        $this->assertInstanceOf(
42
            // ...::class, // 5.4 < php
0 ignored issues
show
Unused Code Comprehensibility introduced by
50% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
43
            'Symfony\Component\HttpKernel\Kernel',
44
            new AppKernel('dev', true)
45
        );
46
    }
47
48
    public function testKernelInterface()
49
    {
50
        $this->assertInstanceOf(
51
            // ...::class, // 5.4 < php
0 ignored issues
show
Unused Code Comprehensibility introduced by
50% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
52
            'Symfony\Component\HttpKernel\KernelInterface',
53
            new AppKernel('dev', true)
54
        );
55
    }
56
57
    public function testFrameworkReturnsResponse()
58
    {
59
        $this->assertInstanceOf(
60
            // Response::class, // 5.4 < php
61
            'Symfony\Component\HttpFoundation\Response',
62
            (new AppKernel('dev', true))->handle(Request::create('/', 'GET'))
63
        );
64
    }
65
66
    public function containerCanBeCreated()
67
    {
68
        $this->assertInstanceOf(
69
            // ...::class, // 5.4 < php
0 ignored issues
show
Unused Code Comprehensibility introduced by
50% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
70
            'Symfony\Component\DependencyInjection\ContainerBuilder',
71
            $this->container()
72
        );
73
    }
74
75
    public function testKernelInterface()
76
    {
77
        $this->assertInstanceOf(
78
            // ...::class, // 5.4 < php
0 ignored issues
show
Unused Code Comprehensibility introduced by
50% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
79
            'psr\Container\ContainerInterface',
80
            $this->container()
81
        );
82
    }
83
84
    /*
0 ignored issues
show
Unused Code Comprehensibility introduced by
47% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
85
    public function testComponentReturnsResponse()
86
    {
87
        $requestStack = new RequestStack();
88
        $routes = new RouteCollectionBuilder(); // Because I know how to use it.
89
        $routes->add('/', EngineAsArgumentController::class, 'index'); // .'::__invoke'
90
        //^ It should be tested if the actually used controller resolver can resolve this!
91
        //^ Returns Symfony/Component/Routing/Route .
92
        $dispatcher = new EventDispatcher();
93
        $dispatcher->addSubscriber(new RouterListener(
94
            new UrlMatcher(
95
                $routes->build(),
96
                new RequestContext()
97
            ),
98
            $requestStack
99
        ));
100
        $dispatcher->addSubscriber(new ResponseListener('UTF-8'));
101
102
103
        $this->assertInstanceOf(
104
            // Response::class, // 5.4 < php
105
            'Symfony\Component\HttpFoundation\Response',
106
            (new HttpKernel(
107
                $dispatcher,
108
                new ContainerControllerResolver($c),
109
                $requestStack,
110
                new ArgumentResolver()
111
            ))->handle(Request::create('/', 'GET'))
112
        );
113
    }
114
    */
115
116
    private function container()
117
    {
118
        $c = new ContainerBuilder();
119
        // https://symfony.com/doc/current/service_container.html
120
121
        $c->autowire(TemplateNameParser::class)
122
            ->setAutoconfigured(true)
123
            ->setPublic(false);
124
        $c->setAlias(TemplateNameParserInterface::class, TemplateNameParser::class);
125
126
        $c->autowire(Twig_Loader_Array::class, Twig_Loader_Array::class)
127
            ->setArgument('$templates', ['index.html.twig' => 'Hello Component!'])
128
            ->setAutoconfigured(true)
129
            ->setPublic(false);
130
        $c->setAlias(Twig_LoaderInterface::class, Twig_Loader_Array::class);
131
132
        $c->autowire(Twig_Environment::class, Twig_Environment::class)
133
            ->setAutoconfigured(true)
134
            ->setPublic(false);
135
        $c->setAlias(Twig\Environment::class, Twig_Environment::class);
136
137
        $c->autowire(TwigEngine::class)
138
            ->setAutoconfigured(true)
139
            ->setPublic(false);
140
        $c->setAlias(EngineInterface::class, TwigEngine::class);
141
142
        // Unit Testing
143
        // $c->autowire('test.client', Client::class)
0 ignored issues
show
Unused Code Comprehensibility introduced by
59% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
144
        //     ->setPublic(true); // Public needed!
0 ignored issues
show
Unused Code Comprehensibility introduced by
63% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
145
146
        //Controllers
147
        $c->autowire(EngineAsArgumentController::class)
148
            ->setAutoconfigured(true)
149
            ->addTag('controller.service_arguments')
150
            ->setPublic(false);
151
152
        return $c;
153
    }
154
}
155
156
// http://api.symfony.com/3.3/Symfony/Bridge/Twig/TwigEngine.html
157
// http://api.symfony.com/3.3/Symfony/Bundle/TwigBundle/TwigEngine.html
158