Duplicate code is one of the most pungent code smells. A rule that is often used is to re-structure code once it is duplicated in three or more places.
Common duplication problems, and corresponding solutions are:
1 | <?php |
||
10 | class SiteConfigTest extends SapphireTest |
||
|
|||
11 | { |
||
12 | protected static $fixture_file = 'SiteConfigTest.yml'; |
||
13 | |||
14 | protected static $illegal_extensions = array( |
||
15 | 'SilverStripe\\CMS\\Model\\SiteTree' => array('SiteTreeSubsites'), |
||
16 | ); |
||
17 | |||
18 | public static function setUpAfterClass() |
||
19 | { |
||
20 | // Fix issue with tests failing without CMS module |
||
21 | if (!class_exists('SilverStripe\\CMS\\Model\\SiteTree')) { |
||
22 | unset(static::$illegal_extensions['SilverStripe\\CMS\\Model\\SiteTree']); |
||
23 | } |
||
24 | |||
25 | static::setUpAfterClass(); // TODO: Change the autogenerated stub |
||
26 | } |
||
27 | |||
28 | View Code Duplication | public function testCanCreateRootPages() |
|
41 | |||
42 | public function testCanViewPages() |
||
47 | |||
48 | public function testCanEdit() |
||
60 | |||
61 | View Code Duplication | public function testCanEditPages() |
|
74 | } |
||
75 |
You can fix this by adding a namespace to your class:
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.