Issues in RegisterTest.php - Fixed Issues - Inspection of "resolve" - slince/upload - Measure and Improve Code Quality continuously with Scrutinizer

Completed

Push — master ( 2bd67e...423e5d )

by Taosikai

created 2017-04-14 08:00 UTC

Tests/RegisterTest.php (1 issue)

Labels

Best Practice 1

Severity

Minor 1

Upgrade to new PHP Analysis Engine

These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more

<?php
namespace Slince\Upload\Tests;

use PHPUnit\Framework\TestCase;
use Slince\Upload\Registry;

class RegisterTest extends TestCase
{
    function testPolyfill()

    {
        $this->assertTrue(class_exists(Registry::class));
    }
}


1			<?php
2			namespace Slince\Upload\Tests;
3
4			use PHPUnit\Framework\TestCase;
5			use Slince\Upload\Registry;
6
7			class RegisterTest extends TestCase
8			{
9			function testPolyfill()
			0 ignored issues – show Best Practice introduced 2017-04-14 07:38 UTC by Report Bug Copy Issue Report Show Similar Issues like this 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...
10			{
11			$this->assertTrue(class_exists(Registry::class));
12			}
13			}
14

slince / upload

Push — master ( 2bd67e...423e5d )

Tests/RegisterTest.php (1 issue)

Labels

Severity

Introduced By

Upgrade to new PHP Analysis Engine

Duplication Side-by-Side

Filter issues like