Completed
Branch AUTOMATED_TESTING (4870f5)
by Gordon
03:01
created

PointsOfInterestLayerTest::testUpdateCMSFields()   A

Complexity

Conditions 2
Paths 2

Size

Total Lines 15
Code Lines 11

Duplication

Lines 0
Ratio 0 %
Metric Value
dl 0
loc 15
rs 9.4286
cc 2
eloc 11
nc 2
nop 0
1
<?php
2
3
class PointsOfInterestLayerTest extends SapphireTest {
1 ignored issue
show
Coding Style Compatibility introduced by
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 testUpdateCMSFields() {
6
		$layer = new PointsOfInterestLayer();
7
		$fields = $layer->getCMSFields();
8
		$root = $fields->fieldByName('Root.Main');
9
		$fields = $root->FieldList();
10
		$names = array();
11
		foreach ($fields as $field) {
12
			$names[] = $field->getName();
13
		}
14
		
15
		error_log(print_r($names,1)); 
16
		$expected = array('Name', 'ShowGuideMarkers', 'DefaultIcon');
17
		$this->assertEquals($expected, $names);
1 ignored issue
show
Bug introduced by
The method assertEquals() does not seem to exist on object<PointsOfInterestLayerTest>.

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...
18
19
	}
20
21
}
22
23
24
class PointsOfInterestLayerTestObjectTO extends DataObject implements TestOnly {
1 ignored issue
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...
Coding Style Compatibility introduced by
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...
25
}