CIPageTest::testPositive() - Code Metrics - gordonbanderson/SilverStripeExampeModuleCI - Measure and Improve Code Quality continuously with Scrutinizer

CIPageTest::testPositive() A
last analyzed 2016-01-19 05:27 UTC

↳ Parent: CIPageTest

Complexity

Conditions	1
Paths	1

Size

Total Lines	7
Code Lines	4

Duplication

Lines	0
Ratio	0 %

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

<?php

 class CIPageTest extends SapphireTest
namespace YourVendor;

class YourClass { }
{
    public function setup()
    {
        $this->Page = new CIPage();
class MyClass { }

$x = new MyClass();
$x->foo = true;
        parent::setup();
    }

    public function testZero()
    {
        $this->assertEquals(

            0,
            $this->Page->doubleNumber(0)
        );
    }

    public function testNegative()
    {
        $this->assertEquals(

            -4,
            $this->Page->doubleNumber(-2)
        );
    }

    public function testPositive()
    {
        $this->assertEquals(

            4,
            $this->Page->doubleNumber(2)
        );
    }
}



1			<?php
2
3			class CIPageTest extends SapphireTest
			0 ignored issues – show Coding Style introduced 2016-01-06 06:50 UTC by Report Bug Copy Issue Report Line indented incorrectly; expected 0 spaces, found 1 Loading history... Coding Style Compatibility introduced 2016-01-06 06: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...
4			{
5			public function setup()
6			{
7			$this->Page = new CIPage();
			0 ignored issues – show Bug introduced 2016-01-06 08:30 UTC by Report Bug Copy Issue Report The property `Page` does not exist. Did you maybe forget to declare it? In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { } $x = new MyClass(); $x->foo = true; Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass { public $foo; } $x = new MyClass(); $x->foo = true; Loading history...
8			parent::setup();
9			}
10
11			public function testZero()
12			{
13			$this->assertEquals(
			0 ignored issues – show Bug introduced 2016-01-06 08:30 UTC by Report Bug Copy Issue Report The method `assertEquals()` does not seem to exist on `object<CIPageTest>`. This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces. This is most likely a typographical error or the method has been renamed. Loading history...
14			0,
15			$this->Page->doubleNumber(0)
16			);
17			}
18
19			public function testNegative()
20			{
21			$this->assertEquals(
			0 ignored issues – show Bug introduced 2016-01-06 08:30 UTC by Report Bug Copy Issue Report The method `assertEquals()` does not seem to exist on `object<CIPageTest>`. This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces. This is most likely a typographical error or the method has been renamed. Loading history...
22			-4,
23			$this->Page->doubleNumber(-2)
24			);
25			}
26
27			public function testPositive()
28			{
29			$this->assertEquals(
			0 ignored issues – show Bug introduced 2016-01-06 08:30 UTC by Report Bug Copy Issue Report The method `assertEquals()` does not seem to exist on `object<CIPageTest>`. This check looks for calls to methods that do not seem to exist on a given type. It looks for the method on the type itself as well as in inherited classes or implemented interfaces. This is most likely a typographical error or the method has been renamed. Loading history...
30			4,
31			$this->Page->doubleNumber(2)
32			);
33			}
34			}
			0 ignored issues – show Coding Style introduced 2016-01-06 06:50 UTC by Report Bug Copy Issue Report Line indented incorrectly; expected 4 spaces, found 0 Loading history... Coding Style introduced 2016-01-06 06:50 UTC by Report Bug Copy Issue Report Closing brace indented incorrectly; expected 1 spaces, found 0 Loading history...
35

gordonbanderson / SilverStripeExampeModuleCI

CIPageTest::testPositive() A last analyzed 2016-01-19 05:27 UTC

Complexity

Size

Duplication

Duplication Side-by-Side

Filter issues like

CIPageTest::testPositive() A
last analyzed 2016-01-19 05:27 UTC