NEWS revision 1.1.1.4 1 Major changes in ATF releases
2
3 By Julio Merino, The NetBSD Foundation
4
5 Contents
6
7 1. Changes in version 0.9
8
9 2. Changes in version 0.8
10
11 3. Changes in version 0.7
12
13 4. Changes in version 0.6
14
15 5. Changes in version 0.5
16
17 6. Changes in version 0.4
18
19 7. Changes in version 0.3
20
21 8. Changes in version 0.2
22
23 9. Changes in version 0.1
24
25 Changes in version 0.9
26
27 Experimental version released on June 3rd, 2010.
28
29 * Added atf-sh, an interpreter to process test programs written using
30 the shell API. This is not really a shell interpreter by itself
31 though: it is just a wrapper around the system shell that eases the
32 loading of the necessary ATF libraries.
33
34 * Removed atf-compile in favour of atf-sh.
35
36 * Added the use.fs metadata property to test case, which is used to
37 specify which test cases require file system access. This is to
38 highlight dependencies on external resources more clearly and to speed
39 up the execution of test suites by skipping the creation of many
40 unnecessary work directories.
41
42 * Fixed test programs to get a sane default value for their source
43 directory. This means that it should not be necessary any more to pass
44 -s when running test programs that do not live in the current
45 directory.
46
47 * Defining test case headers became optional. This is trivial to achieve
48 in shell-based tests but a bit ugly in C and C++. In C, use the new
49 ATF_TC_WITHOUT_HEAD macro to define the test case, and in C++ use
50 ATF_TEST_CASE_WITHOUT_HEAD.
51
52 Changes in version 0.8
53
54 Experimental version released on May 7th, 2010.
55
56 * Test programs no longer run several test cases in a row. The execution
57 of a test program now requires a test case name, and that single test
58 case is executed. To execute several test cases, use the atf-run
59 utility as usual.
60
61 * Test programs no longer fork a subprocess to isolate the execution of
62 test cases. They run the test case code in-process, and a crash of the
63 test case will result in a crash of the test program. This is to ease
64 debugging of faulty test cases.
65
66 * Test programs no longer isolate their test cases. This means that they
67 will not create temporary directories nor sanitize the environment any
68 more. Yes: running a test case that depends on system state by hand
69 will most likely yield different results depending on where (machine,
70 directory, user environment, etc.) it is run. Isolation has been moved
71 to atf-run.
72
73 * Test programs no longer print a cryptic format (application/X-atf-tcs)
74 on a special file channel. They can now print whatever they want on
75 the screen. Because test programs can now only run one test case every
76 time, providing controlled output is not necessary any more.
77
78 * Test programs no longer write their status into a special file
79 descriptor. Instead, they create a file with the results, which is
80 later parsed by atf-run. This changes the semantics of the -r flag.
81
82 * atf-run has been adjusted to perform the test case isolation. As a
83 result, there is now a single canonical place that implements the
84 isolation of test caes. In previous releases, the three language
85 bindings (C, C++ and shell) had to be kept in sync with each other
86 (read: not a nice thing to do at all). As a side effect of this
87 change, writing bindings for other languages will be much, much easier
88 from now on.
89
90 * atf-run forks test programs on a test case basis, instead of on a test
91 program basis as it did before. This is to provide the test case
92 isolation that was before implemented by the test programs themselves.
93
94 * Removed the atf-exec tool. This was used to implement test case
95 isolation in atf-sh, but it is now unnecessary.
96
97 * It is now optional to define the descr meta-data property. It has been
98 proven to be mostly useless, because test cases often carry a
99 descriptive name of their own.
100
101 Changes in version 0.7
102
103 Experimental version released on December 22nd, 2009.
104
105 * Added build-time checks to atf-c and atf-c++. A binding for atf-sh
106 will come later.
107
108 * Migrated all build-time checks for header files to proper ATF tests.
109 This demonstrates the use of the new feature described above.
110
111 * Added an internal API for child process management.
112
113 * Converted all plain-text distribution documents to a Docbook canonical
114 version, and include pre-generated plain text and HTML copies in the
115 distribution file.
116
117 * Simplified the contents of the Makefile.am by regenerating it from a
118 canonical Makefile.am.m4 source. As a side-effect, some dependency
119 specifications were fixed.
120
121 * Migrated all checks from the check target to installcheck, as these
122 require ATF to be installed.
123
124 * Fixed sign comparison mismatches triggered by the now-enabled
125 -Wsign-compare.
126
127 * Fixed many memory and object leaks.
128
129 Changes in version 0.6
130
131 Experimental version released on January 18th, 2009.
132
133 * Make atf-exec be able to kill its child process after a certain period
134 of time; this is controlled through the new -t option.
135
136 * Change atf-sh to use atf-exec's -t option to control the test case's
137 timeouts, instead of doing it internally. Same behavior as before, but
138 noticeably faster.
139
140 * atf-exec's -g option and atf-killpg are gone due to the previous
141 change.
142
143 * Added the atf-check(1) tool, a program that executes a given command
144 and checks its exit code against a known value and allows the
145 management of stdout and stderr in multiple ways. This replaces the
146 previous atf_check function in the atf-sh library and exposes this
147 functionality to both atf-c and atf-c++.
148
149 * Added the ATF_REQUIRE family of macros to the C interface. These help
150 in checking for fatal test conditions. The old ATF_CHECK macros now
151 perform non-fatal checks only. I.e. by using ATF_CHECK, the test case
152 can now continue its execution and the failures will not be reported
153 until the end of the whole run.
154
155 * Extended the amount of ATF_CHECK_* C macros with new ones to provide
156 more features to the developer. These also have their corresponding
157 counterparts in the ATF_REQUIRE_* family. The new macros (listing the
158 suffixes only) are: _EQ (replaces _EQUAL), _EQ_MSG, _STREQ and
159 _STREQ_MSG.
160
161 Changes in version 0.5
162
163 Experimental version released on May 1st, 2008.
164
165 * Clauses 3 and 4 of the BSD license used by the project were dropped.
166 All the code is now under a 2-clause BSD license compatible with the
167 GNU General Public License (GPL).
168
169 * Added a C-only binding so that binary test programs do not need to be
170 tied to C++ at all. This binding is now known as the atf-c library.
171
172 * Renamed the C++ binding to atf-c++ for consistency with the new atf-c.
173
174 * Renamed the POSIX shell binding to atf-sh for consistency with the new
175 atf-c and atf-c++.
176
177 * Added a -w flag to test programs through which it is possible to
178 specify the work directory to be used. This was possible in prior
179 releases by defining the workdir configuration variable (-v
180 workdir=...), but was a conceptually incorrect mechanism.
181
182 * Test programs now preserve the execution order of test cases when they
183 are given in the command line. Even those mentioned more than once are
184 executed multiple times to comply with the user's requests.
185
186 Changes in version 0.4
187
188 Experimental version released on February 4th, 2008.
189
190 * Added two new manual pages, atf-c++-api and atf-sh-api, describing the
191 C++ and POSIX shell interfaces used to write test programs.
192
193 * Added a pkg-config file, useful to get the flags to build against the
194 C++ library or to easily detect the presence of ATF.
195
196 * Added a way for test cases to require a specific architecture and/or
197 machine type through the new 'require.arch' and 'require.machine'
198 meta-data properties, respectively.
199
200 * Added the 'timeout' property to test cases, useful to set an
201 upper-bound limit for the test's run time and thus prevent global test
202 program stalls due to the test case's misbehavior.
203
204 * Added the atf-exec(1) internal utility, used to execute a command
205 after changing the process group it belongs to.
206
207 * Added the atf-killpg(1) internal utility, used to kill process groups.
208
209 * Multiple portability fixes. Of special interest, full support for
210 SunOS (Solaris Express Developer Edition 2007/09) using the Sun Studio
211 12 C++ compiler.
212
213 * Fixed a serious bug that prevented atf-run(1) from working at all
214 under Fedora 8 x86_64. Due to the nature of the bug, other platforms
215 were likely affected too.
216
217 Changes in version 0.3
218
219 Experimental version released on November 11th, 2007.
220
221 * Added XML output support to atf-report. This is accompanied by a DTD
222 for the format's structure and sample XSLT/CSS files to post-process
223 this output and convert it to a plain HTML report.
224
225 * Changed atf-run to add system information to the report it generates.
226 This is currently used by atf-report's XML output only, and is later
227 printed in the HTML reports in a nice and useful summary table. The
228 user and system administrator are allowed to tune this feature by
229 means of hooks.
230
231 * Removed the test cases' 'isolated' property. This was intended to
232 avoid touching the file system at all when running the related test
233 case, but this has not been true for a long while: some control files
234 are unconditionally required for several purposes, and we cannot
235 easily get rid of them. This way we remove several critical and
236 delicate pieces of code.
237
238 * Improved atf-report's CSV output format to include information about
239 test programs too.
240
241 * Fixed the tests that used atf-compile to not require this tool as a
242 helper. Avoids systems without build-time utilities to skip many tests
243 that could otherwise be run. (E.g. NetBSD without the comp.tgz set
244 installed.)
245
246 * Many general cleanups: Fixed many pieces of code marked as ugly and/or
247 incomplete.
248
249 Changes in version 0.2
250
251 Experimental version released on September 20th, 2007.
252
253 * Test cases now get a known umask on entry.
254
255 * atf-run now detects many unexpected failures caused by test programs
256 and reports them as bogus tests. atf-report is able to handle these
257 new errors and nicely reports them to the user.
258
259 * All the data formats read and written by the tools have been
260 documented and cleaned up. These include those grammars that define
261 how the different components communicate with each other as well as
262 the format of files written by the developers and users: the Atffiles
263 and the configuration files.
264
265 * Added the atf-version tool, a utility that displays information about
266 the currently installed version of ATF.
267
268 * Test cases can now define an optional cleanup routine to undo their
269 actions regardless of their exit status.
270
271 * atf-report now summarizes the list of failed (bogus) test programs
272 when using the ticker output format.
273
274 * Test programs now capture some termination signals and clean up any
275 temporary files before exiting the program.
276
277 * Multiple bug fixes and improvements all around.
278
279 Changes in version 0.1
280
281 Experimental version released on August 20th, 2007.
282
283 * First public version. This was released coinciding with the end of the
284 Google Summer of Code 2007 program.
285