32
32
<file>notes.xml</file>
35
<section><title>Test_Server 3.5</title>
37
<section><title>Improvements and New Features</title>
41
The test case group info function has been implemented in
42
Common Test. Before execution of a test case group, a
43
call is now made to <c>TestSuite:group(GroupName)</c>.
44
The function returns a list of test properties, e.g. to
45
specify timetrap values, require configuration data, etc
46
(analogue to the test suite- and test case info
47
function). The scope of the properties set by
48
<c>group(GroupName)</c> is all test cases and sub-groups
49
of group <c>GroupName</c>.</p>
55
The look of the HTML log files generated by Common Test
56
and Test Server has been improved (and made easier to
57
customize) by means of a CSS file.</p>
65
<section><title>Known Bugs and Problems</title>
69
Fix problems in CT/TS due to line numbers in exceptions.</p>
78
<section><title>Test_Server 3.4.5</title>
80
<section><title>Fixed Bugs and Malfunctions</title>
84
An error in how comments are colored in the test suite
85
overview html log file has been corrected. As result, a
86
new framework callback function, format_comment/1, has
93
Test Server did not release SASL TTY handlers
94
(sasl_report_tty_h and error_logger_tty_h) properly after
95
each test run. This error has been fixed.</p>
101
Automatically generated init- and end-configuration
102
functions for test case groups caused incorrect execution
103
order of test cases. This has been corrected.</p>
109
If ct:log/2 was called with bad arguments, this could
110
cause the Common Test IO handling process to crash. This
111
fault has been corrected.</p>
113
Own Id: OTP-9371 Aux Id: OTP-8933 </p>
117
A bug has been fixed that made Test Server call the
118
end_tc/3 framework function with an incorrect module name
119
as first argument.</p>
121
Own Id: OTP-9379 Aux Id: seq11863 </p>
125
If end_per_testcase caused a timetrap timeout, the actual
126
test case status was discarded and the test case logged
127
as successful (even if the case had actually failed
128
before the call to end_per_testcase). This fault has been
135
If a timetrap timeout occured during execution of of a
136
function in a lib module (i.e. a function called directly
137
or indirectly from a test case), the Suite argument in
138
the end_tc/3 framework callback function would not
139
correctly contain the name of the test suite, but the lib
140
module. (This would only happen if the lib module was
141
compiled with ct.hrl included). This error has been
148
Add a proplist() type</p>
150
Recently I was adding specs to an API and found that
151
there is no canonical proplist() type defined. (Thanks to
157
<p> XML files have been corrected. </p>
159
Own Id: OTP-9550 Aux Id: OTP-9541 </p>
163
If a test suite would start with a test case group
164
defined without the init_per_group/2 and end_per_group/2
165
function, init_per_suite/1 would not execute initially
166
and logging of the test run would fail. This error has
175
<section><title>Improvements and New Features</title>
179
A new option, 'logopts', has been introduced, to make it
180
possible to modify some aspects of the logging behaviour
181
in Common Test (or Test Server). For example, whenever an
182
io printout is made, test_server adds newline (\n) to the
183
end of the output string. This may not always be a
184
preferred action and can therefore be disabled by means
185
of "ct_run ... -logopts no_nl" (or ct:run_test([...,
186
{logopts,[no_nl]}])). A new framework callback function,
187
get_logopts/0, has been introduced (see the ct_framework
188
module for details).</p>
190
Own Id: OTP-9372 Aux Id: OTP-9396 </p>
194
A new option, 'logopts', has been introduced, to make it
195
possible to modify some aspects of the logging behaviour
196
in Common Test (or Test Server). For example, if the html
197
version of the test suite source code should not be
198
generated during the test run (and consequently be
199
unavailable in the log file system), the feature may be
200
disabled by means of "ct_run ... -logopts no_src" (or
201
ct:run_test([..., {logopts,[no_src]}])). A new framework
202
callback function, get_logopts/0, has been introduced
203
(see the ct_framework module for details).</p>
205
Own Id: OTP-9396 Aux Id: seq11869, OTP-9372 </p>
209
It is now possible to use a tuple {M,F,A}, or a fun, as
210
timetrap specification in the suite info function or test
211
case info functions. The function must return a valid
212
timeout value, as documented in the common_test man page
213
and in the User's Guide.</p>
215
Own Id: OTP-9501 Aux Id: seq11894 </p>
222
<section><title>Test_Server 3.4.4</title>
224
<section><title>Fixed Bugs and Malfunctions</title>
228
It was previously not possible to use timetrap value
229
'infinity' with ct:timetrap/1. This has been fixed.</p>
235
A bug that made it impossible to cancel the previous
236
timetrap when calling ct:timetrap/1 has been corrected.</p>
238
Own Id: OTP-9233 Aux Id: OTP-9159 </p>
244
<section><title>Improvements and New Features</title>
248
When running tests with auto-compilation disabled, Common
249
Test could only display the test suite source code on
250
html format in the test case log if the source file was
251
located in the same directory as the pre-compiled suite.
252
This has been modified so that Common Test now tries to
253
locate the source file by means of the test suite module
254
info (Suite:module_info/1). As a result, a suite may now
255
be compiled to a different output directory (e.g.
256
$MYTEST/bin) than the source code directory (e.g.
257
$MYTEST/src), without the source-code-to-html generation
264
It is now possible to return a tuple {fail,Reason} from
265
init_per_testcase/2. The result is that the associated
266
test case gets logged as failed without ever executing.</p>
268
Own Id: OTP-9160 Aux Id: seq11502 </p>
272
Added DragonflyBSD check in test_server configure.</p>
281
<section><title>Test_Server 3.4.3</title>
283
<section><title>Fixed Bugs and Malfunctions</title>
287
Updated the ts*.config files to contain information
288
relevant to testing Erlang/OTP in an open source
297
<section><title>Improvements and New Features</title>
301
Alpha release of Common Test Hooks (CTH). CTHs allow the
302
users of common test to abtract out common behaviours
303
from test suites in a much more elegant and flexible way
304
than was possible before. Note that the addition of this
305
feature may introduce minor changes in the undocumented
306
behaviour of the interface inbetween common_test and
309
*** POTENTIAL INCOMPATIBILITY ***</p>
35
318
<section><title>Test_Server 3.4.2</title>
37
320
<section><title>Improvements and New Features</title>