Completed
Branch AUTOMATED_TESTING (6eabf7)
by Gordon
14:03
created

MapAPITest::testgetGoogleMap()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 3
Code Lines 1

Duplication

Lines 0
Ratio 0 %
Metric Value
dl 0
loc 3
rs 10
cc 1
eloc 1
nc 1
nop 0
1
<?php
2
3
class MapAPITest 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
	public function testsetKey() {
5
6
	}
7
8
9
	public function testsetIncludeDownloadJavascript() {
10
11
	}
12
13
14
	public function testsetShowInlineMapDivStyle() {
15
16
	}
17
18
19
	public function testsetAdditionalCSSClasses() {
20
21
	}
22
23
24
	public function testsetMapStyle() {
25
26
	}
27
28
29
	public function testsetDelayLoadMapFunction() {
30
31
	}
32
33
34
	public function testsetDivId() {
35
36
	}
37
38
39
	public function testsetDirectionDivId() {
40
41
	}
42
43
44
	public function testsetSize() {
45
46
	}
47
48
49
	public function testsetIconSize() {
50
51
	}
52
53
54
	public function testsetLang() {
55
56
	}
57
58
59
	public function testsetZoom() {
60
61
	}
62
63
64
	public function testsetInfoWindowZoom() {
65
66
	}
67
68
69
	public function testsetEnableWindowZoom() {
70
71
	}
72
73
74
	public function testsetEnableAutomaticCenterZoom() {
75
76
	}
77
78
79
	public function testsetCenter() {
80
81
	}
82
83
84
	public function testsetMapType() {
85
86
	}
87
88
89
	public function testsetAllowFullScreen() {
90
91
	}
92
93
94
	public function testsetLatLongCenter() {
95
96
	}
97
98
99
	public function testsetDisplayDirectionFields() {
100
101
	}
102
103
104
	public function testsetDefaultHideMarker() {
105
106
	}
107
108
109
	public function testgetGoogleMap() {
110
111
	}
112
113
114
	public function testgetContent() {
115
116
	}
117
118
119
	public function testgeocoding() {
120
121
	}
122
123
	public function testaddMarkerByCoords() {
124
125
	}
126
127
128
	public function testaddMarkerByAddress() {
129
130
	}
131
132
133
	public function testaddArrayMarkerByCoords() {
134
135
	}
136
137
138
	public function testaddMarkerAsObject() {
139
140
	}
141
142
143
	public function testconnectPoints() {
144
145
	}
146
147
148
	public function testforTemplate() {
149
150
	}
151
152
153
	public function testaddArrayMarkerByAddress() {
154
155
	}
156
157
158
	public function testaddDirection() {
159
160
	}
161
162
163
	public function testaddKML() {
164
165
	}
166
167
168
	public function testaddLine() {
169
170
	}
171
172
173
	function testjsonRemoveUnicodeSequences() {
0 ignored issues
show
Best Practice introduced by
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...
174
175
	}
176
177
178
	public function testgenerate() {
179
180
	}
181
182
183
	function testprocessTemplateJS() {
0 ignored issues
show
Best Practice introduced by
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...
184
185
	}
186
187
188
	function testprocessTemplateHTML() {
0 ignored issues
show
Best Practice introduced by
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...
189
190
	}
191
192
}
193