Completed
Branch master (078ac8)
by Pierre-Henry
35:09
created

DesignTest   A

Complexity

Total Complexity 4

Size/Duplication

Total Lines 34
Duplicated Lines 0 %

Coupling/Cohesion

Components 1
Dependencies 4

Importance

Changes 0
Metric Value
c 0
b 0
f 0
dl 0
loc 34
rs 10
wmc 4
lcom 1
cbo 4

4 Methods

Rating   Name   Duplication   Size   Complexity  
A setUp() 0 6 1
A testSetFlashMsgWithDefaultType() 0 6 1
A testSetFlashMsgWithErrorType() 0 6 1
A testSetFlashMsgWithWrongType() 0 6 1
1
<?php
0 ignored issues
show
Coding Style Compatibility introduced by
For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 17 and the first side effect is on line 11.

The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.

The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.

To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.

Loading history...
2
/**
3
 * @author           Pierre-Henry Soria <[email protected]>
4
 * @copyright        (c) 2017, Pierre-Henry Soria. All Rights Reserved.
5
 * @license          GNU General Public License; See PH7.LICENSE.txt and PH7.COPYRIGHT.txt in the root directory.
6
 * @package          PH7 / Test / Unit / Framework / Layout / Html
7
 */
8
9
namespace PH7\Test\Unit\Framework\Layout\Html;
10
11
@session_start();
0 ignored issues
show
Security Best Practice introduced by
It seems like you do not handle an error condition here. This can introduce security issues, and is generally not recommended.

If you suppress an error, we recommend checking for the error condition explicitly:

// For example instead of
@mkdir($dir);

// Better use
if (@mkdir($dir) === false) {
    throw new \RuntimeException('The directory '.$dir.' could not be created.');
}
Loading history...
12
13
use PH7\Framework\Layout\Html\Design;
14
use PH7\Framework\Session\Session;
15
use PH7\Framework\Config\Config;
16
17
class DesignTest extends \PHPUnit_Framework_TestCase
18
{
19
    private $oDesign;
20
    private $oSession;
21
    private $oConfig;
22
23
    protected function setUp()
24
    {
25
        $this->oConfig = Config::getInstance();
26
        $this->oSession = new Session;
27
        $this->oDesign = new Design;
28
    }
29
30
    public function testSetFlashMsgWithDefaultType()
31
    {
32
        $this->oDesign->setFlashMsg('Hey You!');
33
        $this->assertEquals('Hey You!', $this->oSession->get('flash_msg'));
34
        $this->assertEquals('success', $this->oSession->get('flash_type'));
35
    }
36
37
    public function testSetFlashMsgWithErrorType()
38
    {
39
        $this->oDesign->setFlashMsg('Wrong Message!', Design::ERROR_TYPE);
40
        $this->assertEquals('Wrong Message!', $this->oSession->get('flash_msg'));
41
        $this->assertEquals('error', $this->oSession->get('flash_type'));
42
    }
43
44
    public function testSetFlashMsgWithWrongType()
45
    {
46
        $this->oDesign->setFlashMsg('blabla', 'wrong_type');
47
        $this->assertEquals('blabla', $this->oSession->get('flash_msg'));
48
        $this->assertEquals('', $this->oSession->get('flash_type'));
49
    }
50
 }
51