AbstractModuleTest::setUp()   A
last analyzed

Complexity

Conditions 1
Paths 1

Size

Total Lines 3
Code Lines 2

Duplication

Lines 0
Ratio 0 %

Importance

Changes 2
Bugs 0 Features 0
Metric Value
c 2
b 0
f 0
dl 0
loc 3
rs 10
cc 1
eloc 2
nc 1
nop 0
1
<?php
2
3
/*
4
 * The MIT License
5
 *
6
 * Copyright 2016 Alejandro Peña Florentín ([email protected]).
7
 *
8
 * Permission is hereby granted, free of charge, to any person obtaining a copy
9
 * of this software and associated documentation files (the "Software"), to deal
10
 * in the Software without restriction, including without limitation the rights
11
 * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
12
 * copies of the Software, and to permit persons to whom the Software is
13
 * furnished to do so, subject to the following conditions:
14
 *
15
 * The above copyright notice and this permission notice shall be included in
16
 * all copies or substantial portions of the Software.
17
 *
18
 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
19
 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
20
 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
21
 * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
22
 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
23
 * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
24
 * THE SOFTWARE.
25
 */
26
27
namespace Tight\Tests;
28
29
/**
30
 * Description of AbstractModuleTest
31
 *
32
 * @author Alejandro Peña Florentín ([email protected])
33
 */
34
class AbstractModuleTest extends \PHPUnit_Framework_TestCase
35
{
36
37
    private $name = "TestModule";
0 ignored issues
show
Comprehensibility introduced by
Consider using a different property name as you override a private property of the parent class.
Loading history...
38
    private $version = "v1.5";
39
    private $module;
40
41
    public function setUp() {
42
        $this->module = new TestModule($this->name, $this->version);
43
    }
44
45
    public function tearDown() {
46
        
47
    }
48
49
    /**
50
     * @test
51
     */
52
    public function testAbstractModuleGetName() {
53
        $this->assertEquals($this->name, $this->module->getModuleName());
54
    }
55
    /**
56
     * @test
57
     */
58
    public function testAbstractModuleGetVersion(){
59
        $this->assertEquals($this->version, $this->module->getModuleVersion());
60
    }
61
    /**
62
     * @test
63
     */
64
    public function testAbstractModuleGetAppConfig(){
65
        $this->assertEquals(\Tight\Tight::getInstance()->getConfig(),$this->module->getAppConfig());
66
    }
67
}
68
69
class TestModule extends \Tight\Modules\AbstractModule
0 ignored issues
show
Coding Style Compatibility introduced by
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...
70
{
71
72
    public function onConfigChange() {
73
        
74
    }
75
76
    public function onLoad() {
77
        
78
    }
79
80
    public function onRemove() {
81
        
82
    }
83
84
}
85