Mercurial > octave
annotate doc/interpreter/testfun.txi @ 10828:322f43e0e170
Grammarcheck .txi documentation files.
author | Rik <octave@nomad.inbox5.com> |
---|---|
date | Wed, 28 Jul 2010 12:45:04 -0700 |
parents | 3b77db443cc0 |
children | a4f482e66b65 |
rev | line source |
---|---|
8920 | 1 @c Copyright (C) 2005, 2007, 2009 David Bateman |
7018 | 2 @c Copyright (C) 2002, 2003, 2004, 2005 Paul Kienzle |
3 @c | |
4 @c This file is part of Octave. | |
5 @c | |
6 @c Octave is free software; you can redistribute it and/or modify it | |
7 @c under the terms of the GNU General Public License as published by the | |
8 @c Free Software Foundation; either version 3 of the License, or (at | |
9 @c your option) any later version. | |
10 @c | |
11 @c Octave is distributed in the hope that it will be useful, but WITHOUT | |
12 @c ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or | |
13 @c FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License | |
14 @c for more details. | |
15 @c | |
16 @c You should have received a copy of the GNU General Public License | |
17 @c along with Octave; see the file COPYING. If not, see | |
18 @c <http://www.gnu.org/licenses/>. | |
5582 | 19 |
20 @node Test and Demo Functions | |
21 @appendix Test and Demo Functions | |
22 @cindex test functions | |
23 | |
24 Octave includes a number of functions to allow the integration of testing | |
25 and demonstration code in the source code of the functions themselves. | |
26 | |
27 @menu | |
28 * Test Functions:: | |
29 * Demonstration Functions:: | |
30 @end menu | |
31 | |
32 @node Test Functions | |
33 @section Test Functions | |
34 | |
35 @DOCSTRING(test) | |
36 | |
37 @code{test} scans the named script file looking for lines which | |
9080
ec41eabf4499
Cleanup documentation files dynamic.texi, testfun.texi, tips.texi
Rik <rdrider0-list@yahoo.com>
parents:
8920
diff
changeset
|
38 start with @code{%!}. The prefix is stripped off and the rest of the |
ec41eabf4499
Cleanup documentation files dynamic.texi, testfun.texi, tips.texi
Rik <rdrider0-list@yahoo.com>
parents:
8920
diff
changeset
|
39 line is processed through the Octave interpreter. If the code |
5582 | 40 generates an error, then the test is said to fail. |
41 | |
42 Since @code{eval()} will stop at the first error it encounters, you must | |
43 divide your tests up into blocks, with anything in a separate | |
44 block evaluated separately. Blocks are introduced by the keyword | |
10828
322f43e0e170
Grammarcheck .txi documentation files.
Rik <octave@nomad.inbox5.com>
parents:
10496
diff
changeset
|
45 @code{test} immediately following the @code{%!}. For example: |
5582 | 46 |
47 @example | |
48 @group | |
6728 | 49 %!test error ("this test fails!"); |
7081 | 50 %!test "test doesn't fail. it doesn't generate an error"; |
5582 | 51 @end group |
52 @end example | |
53 | |
54 When a test fails, you will see something like: | |
55 | |
56 @example | |
57 @group | |
6728 | 58 ***** test error ('this test fails!') |
5582 | 59 !!!!! test failed |
60 this test fails! | |
61 @end group | |
62 @end example | |
63 | |
64 Generally, to test if something works, you want to assert that it | |
65 produces a correct value. A real test might look something like | |
66 | |
67 @example | |
68 @group | |
69 %!test | |
70 %! @var{a} = [1, 2, 3; 4, 5, 6]; B = [1; 2]; | |
71 %! expect = [ @var{a} ; 2*@var{a} ]; | |
72 %! get = kron (@var{b}, @var{a}); | |
73 %! if (any(size(expect) != size(get))) | |
74 %! error ("wrong size: expected %d,%d but got %d,%d", | |
75 %! size(expect), size(get)); | |
76 %! elseif (any(any(expect!=get))) | |
77 %! error ("didn't get what was expected."); | |
78 %! endif | |
79 @end group | |
80 @end example | |
81 | |
82 To make the process easier, use the @code{assert} function. For example, | |
83 with @code{assert} the previous test is reduced to: | |
84 | |
85 @example | |
86 @group | |
87 %!test | |
88 %! @var{a} = [1, 2, 3; 4, 5, 6]; @var{b} = [1; 2]; | |
89 %! assert (kron (@var{b}, @var{a}), [ @var{a}; 2*@var{a} ]); | |
90 @end group | |
91 @end example | |
92 | |
93 @code{assert} can accept a tolerance so that you can compare results | |
9080
ec41eabf4499
Cleanup documentation files dynamic.texi, testfun.texi, tips.texi
Rik <rdrider0-list@yahoo.com>
parents:
8920
diff
changeset
|
94 absolutely or relatively. For example, the following all succeed: |
5582 | 95 |
96 @example | |
97 @group | |
98 %!test assert (1+eps, 1, 2*eps) # absolute error | |
99 %!test assert (100+100*eps, 100, -2*eps) # relative error | |
100 @end group | |
101 @end example | |
102 | |
103 You can also do the comparison yourself, but still have assert | |
104 generate the error: | |
105 | |
106 @example | |
107 @group | |
108 %!test assert (isempty([])) | |
109 %!test assert ([ 1,2; 3,4 ] > 0) | |
110 @end group | |
111 @end example | |
112 | |
113 Because @code{assert} is so frequently used alone in a test block, there | |
114 is a shorthand form: | |
115 | |
116 @example | |
117 %!assert (@dots{}) | |
118 @end example | |
119 | |
120 which is equivalent to: | |
121 | |
122 @example | |
123 %!test assert (@dots{}) | |
124 @end example | |
125 | |
6728 | 126 Sometimes during development there is a test that should work but is |
127 known to fail. You still want to leave the test in because when the | |
128 final code is ready the test should pass, but you may not be able to | |
7001 | 129 fix it immediately. To avoid unnecessary bug reports for these known |
6728 | 130 failures, mark the block with @code{xtest} rather than @code{test}: |
131 | |
132 @example | |
9080
ec41eabf4499
Cleanup documentation files dynamic.texi, testfun.texi, tips.texi
Rik <rdrider0-list@yahoo.com>
parents:
8920
diff
changeset
|
133 @group |
6731 | 134 %!xtest assert (1==0) |
135 %!xtest fail ('success=1','error')) | |
9080
ec41eabf4499
Cleanup documentation files dynamic.texi, testfun.texi, tips.texi
Rik <rdrider0-list@yahoo.com>
parents:
8920
diff
changeset
|
136 @end group |
6728 | 137 @end example |
138 | |
139 Another use of @code{xtest} is for statistical tests which should | |
140 pass most of the time but are known to fail occasionally. | |
141 | |
5582 | 142 Each block is evaluated in its own function environment, which means |
143 that variables defined in one block are not automatically shared | |
144 with other blocks. If you do want to share variables, then you | |
145 must declare them as @code{shared} before you use them. For example, the | |
146 following declares the variable @var{a}, gives it an initial value (default | |
147 is empty), then uses it in several subsequent tests. | |
148 | |
149 @example | |
150 @group | |
151 %!shared @var{a} | |
152 %! @var{a} = [1, 2, 3; 4, 5, 6]; | |
153 %!assert (kron ([1; 2], @var{a}), [ @var{a}; 2*@var{a} ]); | |
154 %!assert (kron ([1, 2], @var{a}), [ @var{a}, 2*@var{a} ]); | |
155 %!assert (kron ([1,2; 3,4], @var{a}), [ @var{a},2*@var{a}; 3*@var{a},4*@var{a} ]); | |
156 @end group | |
157 @end example | |
158 | |
159 You can share several variables at the same time: | |
160 | |
161 @example | |
162 %!shared @var{a}, @var{b} | |
163 @end example | |
164 | |
165 You can also share test functions: | |
166 | |
167 @example | |
168 @group | |
169 %!function @var{a} = fn(@var{b}) | |
170 %! @var{a} = 2*@var{b}; | |
171 %!assert (@var{a}(2),4); | |
172 @end group | |
173 @end example | |
174 | |
175 Note that all previous variables and values are lost when a new | |
176 shared block is declared. | |
177 | |
178 Error and warning blocks are like test blocks, but they only succeed | |
179 if the code generates an error. You can check the text of the error | |
180 is correct using an optional regular expression @code{<pattern>}. | |
181 For example: | |
182 | |
183 @example | |
184 %!error <passes!> error('this test passes!'); | |
185 @end example | |
186 | |
9080
ec41eabf4499
Cleanup documentation files dynamic.texi, testfun.texi, tips.texi
Rik <rdrider0-list@yahoo.com>
parents:
8920
diff
changeset
|
187 If the code doesn't generate an error, the test fails. For example, |
5582 | 188 |
189 @example | |
190 %!error "this is an error because it succeeds."; | |
191 @end example | |
192 | |
193 produces | |
194 | |
195 @example | |
196 @group | |
197 ***** error "this is an error because it succeeds."; | |
198 !!!!! test failed: no error | |
199 @end group | |
200 @end example | |
201 | |
202 It is important to automate the tests as much as possible, however | |
203 some tests require user interaction. These can be isolated into | |
204 demo blocks, which if you are in batch mode, are only run when | |
9080
ec41eabf4499
Cleanup documentation files dynamic.texi, testfun.texi, tips.texi
Rik <rdrider0-list@yahoo.com>
parents:
8920
diff
changeset
|
205 called with @code{demo} or @code{verbose}. The code is displayed before |
ec41eabf4499
Cleanup documentation files dynamic.texi, testfun.texi, tips.texi
Rik <rdrider0-list@yahoo.com>
parents:
8920
diff
changeset
|
206 it is executed. For example, |
5582 | 207 |
208 @example | |
209 @group | |
210 %!demo | |
211 %! @var{t}=[0:0.01:2*pi]; @var{x}=sin(@var{t}); | |
212 %! plot(@var{t},@var{x}); | |
213 %! you should now see a sine wave in your figure window | |
214 @end group | |
215 @end example | |
216 | |
217 produces | |
218 | |
219 @example | |
220 @group | |
221 > @var{t}=[0:0.01:2*pi]; @var{x}=sin(@var{t}); | |
222 > plot(@var{t},@var{x}); | |
223 > you should now see a sine wave in your figure window | |
224 Press <enter> to continue: | |
225 @end group | |
226 @end example | |
227 | |
228 Note that demo blocks cannot use any shared variables. This is so | |
229 that they can be executed by themselves, ignoring all other tests. | |
230 | |
231 If you want to temporarily disable a test block, put @code{#} in place | |
232 of the block type. This creates a comment block which is echoed | |
233 in the log file, but is not executed. For example: | |
234 | |
235 @example | |
236 @group | |
237 %!#demo | |
238 %! @var{t}=[0:0.01:2*pi]; @var{x}=sin(@var{t}); | |
239 %! plot(@var{t},@var{x}); | |
240 %! you should now see a sine wave in your figure window | |
241 @end group | |
242 @end example | |
243 | |
244 Block type summary: | |
245 | |
246 @table @code | |
247 @item %!test | |
248 check that entire block is correct | |
10828
322f43e0e170
Grammarcheck .txi documentation files.
Rik <octave@nomad.inbox5.com>
parents:
10496
diff
changeset
|
249 |
5582 | 250 @item %!error |
251 check for correct error message | |
10828
322f43e0e170
Grammarcheck .txi documentation files.
Rik <octave@nomad.inbox5.com>
parents:
10496
diff
changeset
|
252 |
5582 | 253 @item %!warning |
254 check for correct warning message | |
10828
322f43e0e170
Grammarcheck .txi documentation files.
Rik <octave@nomad.inbox5.com>
parents:
10496
diff
changeset
|
255 |
5582 | 256 @item %!demo |
257 demo only executes in interactive mode | |
10828
322f43e0e170
Grammarcheck .txi documentation files.
Rik <octave@nomad.inbox5.com>
parents:
10496
diff
changeset
|
258 |
5582 | 259 @item %!# |
260 comment: ignore everything within the block | |
10828
322f43e0e170
Grammarcheck .txi documentation files.
Rik <octave@nomad.inbox5.com>
parents:
10496
diff
changeset
|
261 |
5582 | 262 @item %!shared x,y,z |
263 declares variables for use in multiple tests | |
10828
322f43e0e170
Grammarcheck .txi documentation files.
Rik <octave@nomad.inbox5.com>
parents:
10496
diff
changeset
|
264 |
5582 | 265 @item %!function |
266 defines a function value for a shared variable | |
10828
322f43e0e170
Grammarcheck .txi documentation files.
Rik <octave@nomad.inbox5.com>
parents:
10496
diff
changeset
|
267 |
5582 | 268 @item %!assert (x, y, tol) |
269 shorthand for %!test assert (x, y, tol) | |
270 @end table | |
271 | |
272 You can also create test scripts for builtins and your own C++ | |
9080
ec41eabf4499
Cleanup documentation files dynamic.texi, testfun.texi, tips.texi
Rik <rdrider0-list@yahoo.com>
parents:
8920
diff
changeset
|
273 functions. Just put a file of the function name on your path without |
5582 | 274 any extension and it will be picked up by the test procedure. You |
275 can even embed tests directly in your C++ code: | |
276 | |
277 @example | |
278 @group | |
279 #if 0 | |
280 %!test disp('this is a test') | |
281 #endif | |
282 @end group | |
283 @end example | |
284 | |
285 or | |
286 | |
287 @example | |
288 @group | |
289 /* | |
290 %!test disp('this is a test') | |
291 */ | |
292 @end group | |
293 @end example | |
294 | |
295 but then the code will have to be on the load path and the user | |
296 will have to remember to type test('name.cc'). Conversely, you | |
8481
00df69d7e698
[docs] capitalize Octave consistently
Brian Gough <bjg@gnu.org>
parents:
7081
diff
changeset
|
297 can separate the tests from normal Octave script files by putting |
5582 | 298 them in plain files with no extension rather than in script files. |
299 @c DO I WANT TO INCLUDE THE EDITOR SPECIFIC STATEMENT BELOW??? | |
300 @c Don't forget to tell emacs that the plain text file you are using | |
301 @c is actually octave code, using something like: | |
302 @c -*-octave-*- | |
303 | |
304 @DOCSTRING(assert) | |
305 | |
306 @DOCSTRING(fail) | |
307 | |
308 @node Demonstration Functions | |
309 @section Demonstration Functions | |
310 | |
311 @DOCSTRING(demo) | |
312 | |
8817
03b7f618ab3d
include docstrings for new functions in the manual
John W. Eaton <jwe@octave.org>
parents:
8481
diff
changeset
|
313 @DOCSTRING(rundemos) |
03b7f618ab3d
include docstrings for new functions in the manual
John W. Eaton <jwe@octave.org>
parents:
8481
diff
changeset
|
314 |
10496
3b77db443cc0
scripts/testfun/runtests.m: new function
John W. Eaton <jwe@octave.org>
parents:
9080
diff
changeset
|
315 @DOCSTRING(runtests) |
3b77db443cc0
scripts/testfun/runtests.m: new function
John W. Eaton <jwe@octave.org>
parents:
9080
diff
changeset
|
316 |
5582 | 317 @DOCSTRING(example) |
318 | |
319 @DOCSTRING(speed) |