1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
|
<html>
<head>
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Simple Test documentation for testing HTML forms</title>
<link rel="stylesheet" type="text/css" href="docs.css" title="Styles">
</head>
<body>
<div class="menu_back">
<div class="menu">
<h2>
<a href="index.html">SimpleTest</a>
</h2>
<ul>
<li>
<a href="overview.html">Overview</a>
</li>
<li>
<a href="unit_test_documentation.html">Unit tester</a>
</li>
<li>
<a href="group_test_documentation.html">Group tests</a>
</li>
<li>
<a href="server_stubs_documentation.html">Server stubs</a>
</li>
<li>
<a href="mock_objects_documentation.html">Mock objects</a>
</li>
<li>
<a href="partial_mocks_documentation.html">Partial mocks</a>
</li>
<li>
<a href="reporter_documentation.html">Reporting</a>
</li>
<li>
<a href="expectation_documentation.html">Expectations</a>
</li>
<li>
<a href="web_tester_documentation.html">Web tester</a>
</li>
<li>
<span class="chosen">Testing forms</span>
</li>
<li>
<a href="authentication_documentation.html">Authentication</a>
</li>
<li>
<a href="browser_documentation.html">Scriptable browser</a>
</li>
</ul>
</div>
</div>
<h1>Form testing documentation</h1>
<div class="content">
<p>
<a class="target" name="submit">
<h2>Submitting a simple form</h2>
</a>
</p>
<p>
When a page is fetched by the <span class="new_code">WebTestCase</span>
using <span class="new_code">get()</span> or
<span class="new_code">post()</span> the page content is
automatically parsed.
This results in any form controls that are inside <form> tags
being available from within the test case.
For example, if we have this snippet of HTML...
<pre>
<form>
<input type="text" name="a" value="A default" />
<input type="submit" value="Go" />
</form>
</pre>
Which looks like this...
</p>
<p>
<form class="demo">
<input type="text" name="a" value="A default">
<input type="submit" value="Go">
</form>
</p>
<p>
We can navigate to this code, via the
<a href="http://www.lastcraft.com/form_testing_documentation.php">LastCraft</a>
site, with the following test...
<pre>
class SimpleFormTests extends WebTestCase {
<strong>
function testDefaultValue() {
$this->get('http://www.lastcraft.com/form_testing_documentation.php');
$this->assertField('a', 'A default');
}</strong>
}
</pre>
Immediately after loading the page all of the HTML controls are set at
their default values just as they would appear in the web browser.
The assertion tests that a HTML widget exists in the page with the
name "a" and that it is currently set to the value
"A default"
</p>
<p>
We could submit the form straight away, but first we'll change
the value of the text field and only then submit it...
<pre>
class SimpleFormTests extends WebTestCase {
function testDefaultValue() {
$this->get('http://www.my-site.com/');
$this->assertField('a', 'A default');<strong>
$this->setField('a', 'New value');
$this->clickSubmit('Go');</strong>
}
}
</pre>
Because we didn't specify a method attribute on the form tag, and
didn't specify an action either, the test case will follow
the usual browser behaviour of submitting the form data as a <em>GET</em>
request back to the same location.
SimpleTest tries to emulate typical browser behaviour as much as possible,
rather than attempting to catch missing attributes on tags.
This is because the target of the testing framework is the PHP application
logic, not syntax or other errors in the HTML code.
For HTML errors, other tools such as
<a href="http://www.w3.org/People/Raggett/tidy/">HTMLTidy</a> should be used.
</p>
<p>
If a field is not present in any form, or if an option is unavailable,
then <span class="new_code">WebTestCase::setField()</span> will return
<span class="new_code">false</span>.
For example, suppose we wish to verify that a "Superuser"
option is not present in this form...
<pre>
<strong>Select type of user to add:</strong>
<select name="type">
<option>Subscriber</option>
<option>Author</option>
<option>Administrator</option>
</select>
</pre>
Which looks like...
</p>
<p>
<form class="demo">
<strong>Select type of user to add:</strong>
<select name="type">
<option>Subscriber</option>
<option>Author</option>
<option>Administrator</option>
</select>
</form>
</p>
<p>
The following test will confirm it...
<pre>
class SimpleFormTests extends WebTestCase {
...
function testNoSuperuserChoiceAvailable() {<strong>
$this->get('http://www.lastcraft.com/form_testing_documentation.php');
$this->assertFalse($this->setField('type', 'Superuser'));</strong>
}
}
</pre>
The selection will not be changed on a failure to set
a widget value.
</p>
<p>
Here is the full list of widgets currently supported...
<ul>
<li>Text fields, including hidden and password fields.</li>
<li>Submit buttons including the button tag, although not yet reset buttons</li>
<li>Text area. This includes text wrapping behaviour.</li>
<li>Checkboxes, including multiple checkboxes in the same form.</li>
<li>Drop down selections, including multiple selects.</li>
<li>Radio buttons.</li>
<li>Images.</li>
</ul>
</p>
<p>
Although most standard HTML widgets are catered for by <em>SimpleTest</em>'s
built in parser, it is unlikely that JavaScript will be implemented
anytime soon.
</p>
<p>
<a class="target" name="multiple">
<h2>Fields with multiple values</h2>
</a>
</p>
<p>
SimpleTest can cope with two types of multivalue controls: Multiple
selection drop downs, and multiple checkboxes with the same name
within a form.
The multivalue nature of these means that setting and testing
are slightly different.
Using checkboxes as an example...
<pre>
<form class="demo">
<strong>Create privileges allowed:</strong>
<input type="checkbox" name="crud" value="c" checked><br>
<strong>Retrieve privileges allowed:</strong>
<input type="checkbox" name="crud" value="r" checked><br>
<strong>Update privileges allowed:</strong>
<input type="checkbox" name="crud" value="u" checked><br>
<strong>Destroy privileges allowed:</strong>
<input type="checkbox" name="crud" value="d" checked><br>
<input type="submit" value="Enable Privileges">
</form>
</pre>
Which renders as...
</p>
<p>
<form class="demo">
<strong>Create privileges allowed:</strong>
<input type="checkbox" name="crud" value="c" checked>
<br>
<strong>Retrieve privileges allowed:</strong>
<input type="checkbox" name="crud" value="r" checked>
<br>
<strong>Update privileges allowed:</strong>
<input type="checkbox" name="crud" value="u" checked>
<br>
<strong>Destroy privileges allowed:</strong>
<input type="checkbox" name="crud" value="d" checked>
<br>
<input type="submit" value="Enable Privileges">
</form>
</p>
<p>
If we wish to disable all but the retrieval privileges and
submit this information we can do it like this...
<pre>
class SimpleFormTests extends WebTestCase {
...<strong>
function testDisableNastyPrivileges() {
$this->get('http://www.lastcraft.com/form_testing_documentation.php');
$this->assertField('crud', array('c', 'r', 'u', 'd'));
$this->setField('crud', array('r'));
$this->clickSubmit('Enable Privileges');
}</strong>
}
</pre>
Instead of setting the field to a single value, we give it a list
of values.
We do the same when testing expected values.
We can then write other test code to confirm the effect of this, perhaps
by logging in as that user and attempting an update.
</p>
<p>
<a class="target" name="raw">
<h2>Raw posting</h2>
</a>
</p>
<p>
If you want to test a form handler, but have not yet written
or do not have access to the form itself, you can create a
form submission by hand.
<pre>
class SimpleFormTests extends WebTestCase {
...<strong>
function testAttemptedHack() {
$this->post(
'http://www.my-site.com/add_user.php',
array('type' => 'superuser'));
$this->assertNoUnwantedPattern('/user created/i');
}</strong>
}
</pre>
By adding data to the <span class="new_code">WebTestCase::post()</span>
method, we are attempting to fetch the page as a form submission.
</p>
</div>
<div class="copyright">
Copyright<br>Marcus Baker, Jason Sweat, Perrick Penet 2004
</div>
</body>
</html>
|
