head	1.2;
access;
symbols
	perseant-exfatfs-base-20240630:1.2
	perseant-exfatfs:1.2.0.24
	perseant-exfatfs-base:1.2
	cjep_sun2x:1.2.0.22
	cjep_sun2x-base:1.2
	cjep_staticlib_x-base1:1.2
	cjep_staticlib_x:1.2.0.20
	cjep_staticlib_x-base:1.2
	phil-wifi-20200421:1.2
	phil-wifi-20200411:1.2
	phil-wifi-20200406:1.2
	pgoyette-compat-merge-20190127:1.2
	pgoyette-compat-20190127:1.2
	pgoyette-compat-20190118:1.2
	pgoyette-compat-1226:1.2
	pgoyette-compat-1126:1.2
	pgoyette-compat-1020:1.2
	pgoyette-compat-0930:1.2
	pgoyette-compat-0906:1.2
	pgoyette-compat-0728:1.2
	pgoyette-compat-0625:1.2
	pgoyette-compat-0521:1.2
	pgoyette-compat-0502:1.2
	pgoyette-compat-0422:1.2
	pgoyette-compat-0415:1.2
	pgoyette-compat-0407:1.2
	pgoyette-compat-0330:1.2
	pgoyette-compat-0322:1.2
	pgoyette-compat-0315:1.2
	pgoyette-compat:1.2.0.18
	pgoyette-compat-base:1.2
	perseant-stdc-iso10646:1.2.0.16
	perseant-stdc-iso10646-base:1.2
	prg-localcount2-base3:1.2
	prg-localcount2-base2:1.2
	prg-localcount2-base1:1.2
	prg-localcount2:1.2.0.14
	prg-localcount2-base:1.2
	pgoyette-localcount-20170426:1.2
	bouyer-socketcan-base1:1.2
	pgoyette-localcount-20170320:1.2
	bouyer-socketcan:1.2.0.12
	bouyer-socketcan-base:1.2
	pgoyette-localcount-20170107:1.2
	pgoyette-localcount-20161104:1.2
	localcount-20160914:1.2
	pgoyette-localcount-20160806:1.2
	pgoyette-localcount-20160726:1.2
	pgoyette-localcount:1.2.0.10
	pgoyette-localcount-base:1.2
	yamt-pagecache-base9:1.2
	yamt-pagecache-tag8:1.2
	tls-earlyentropy:1.2.0.6
	tls-earlyentropy-base:1.2
	riastradh-xf86-video-intel-2-7-1-pre-2-21-15:1.2
	riastradh-drm2-base3:1.2
	agc-symver:1.2.0.8
	agc-symver-base:1.2
	tls-maxphys-base:1.2
	yamt-pagecache-base8:1.2
	yamt-pagecache-base7:1.2
	yamt-pagecache-base6:1.2
	yamt-pagecache-base5:1.2
	yamt-pagecache-base4:1.2
	yamt-pagecache-base3:1.2
	yamt-pagecache-base2:1.2
	yamt-pagecache:1.2.0.4
	yamt-pagecache-base:1.2
	bouyer-quota2-nbase:1.2
	bouyer-quota2:1.2.0.2
	bouyer-quota2-base:1.2
	atf-0-9:1.1.1.3
	atf-0-8:1.1.1.2
	atf-0-7:1.1.1.1
	TNF:1.1.1;
locks; strict;
comment	@# @;


1.2
date	2010.06.18.15.41.21;	author jmmv;	state dead;
branches;
next	1.1;

1.1
date	2009.12.22.13.25.58;	author jmmv;	state Exp;
branches
	1.1.1.1;
next	;

1.1.1.1
date	2009.12.22.13.25.58;	author jmmv;	state Exp;
branches;
next	1.1.1.2;

1.1.1.2
date	2010.05.08.08.05.23;	author jmmv;	state Exp;
branches;
next	1.1.1.3;

1.1.1.3
date	2010.06.04.08.23.46;	author jmmv;	state Exp;
branches;
next	;


desc
@@


1.2
log
@Remove unnecessary files

The just-commited prepare-import.sh script will take care of spotting extra
files that may be unnecessary during a future import.
@
text
@<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD Simplified DocBook XML V1.1//EN"
                  "http://docbook.org/xml/simple/1.1/sdocbook.dtd">

<article>

<articleinfo>
  <title>Major changes in ATF releases</title>

  <author>
    <firstname>Julio</firstname>
    <surname>Merino</surname>
    <affiliation>
      <orgname>The NetBSD Foundation</orgname>
    </affiliation>
  </author>
</articleinfo>

<section id="atf-0-7">

<title>Changes in version 0.7</title>

<para>Experimental version released on December 22nd, 2009.</para>

<itemizedlist>

<listitem><para>Added build-time checks to atf-c and atf-c++.  A binding
for atf-sh will come later.</para></listitem>

<listitem><para>Migrated all build-time checks for header files to proper
ATF tests.  This demonstrates the use of the new feature described
above.</para></listitem>

<listitem><para>Added an internal API for child process
management.</para></listitem>

<listitem><para>Converted all plain-text distribution documents to a Docbook
canonical version, and include pre-generated plain text and HTML copies in
the distribution file.</para></listitem>

<listitem><para>Simplified the contents of the
<filename>Makefile.am</filename> by regenerating it from a canonical
<filename>Makefile.am.m4</filename> source.  As a side-effect, some
dependency specifications were fixed.</para></listitem>

<listitem><para>Migrated all checks from the <literal>check</literal> target
to <literal>installcheck</literal>, as these require ATF to be
installed.</para></listitem>

<listitem><para>Fixed sign comparison mismatches triggered by
the now-enabled <literal>-Wsign-compare</literal>.</para></listitem>

<listitem><para>Fixed many memory and object leaks.</para></listitem>

</itemizedlist>

</section>

<section id="atf-0-6">

<title>Changes in version 0.6</title>

<para>Experimental version released on January 18th, 2009.</para>

<itemizedlist>

<listitem><para>Make atf-exec be able to kill its child process after a
certain period of time; this is controlled through the new -t
option.</para></listitem>

<listitem><para>Change atf-sh to use atf-exec's -t option to control the
test case's timeouts, instead of doing it internally.  Same behavior as
before, but noticeably faster.</para></listitem>

<listitem><para>atf-exec's -g option and atf-killpg are gone due to the
previous change.</para></listitem>

<listitem><para>Added the atf-check(1) tool, a program that executes a
given command and checks its exit code against a known value and allows the
management of stdout and stderr in multiple ways.  This replaces the
previous atf_check function in the atf-sh library and exposes this
functionality to both atf-c and atf-c++.</para></listitem>

<listitem><para>Added the ATF_REQUIRE family of macros to the C interface.
These help in checking for fatal test conditions.  The old ATF_CHECK macros
now perform non-fatal checks only.  I.e. by using ATF_CHECK, the test case
can now continue its execution and the failures will not be reported until
the end of the whole run.</para></listitem>

<listitem><para>Extended the amount of ATF_CHECK_* C macros with new ones
to provide more features to the developer.  These also have their
corresponding counterparts in the ATF_REQUIRE_* family.  The new macros
(listing the suffixes only) are: _EQ (replaces _EQUAL), _EQ_MSG, _STREQ and
_STREQ_MSG.</para></listitem>

</itemizedlist>

</section>

<section id="atf-0-5">

<title>Changes in version 0.5</title>

<para>Experimental version released on May 1st, 2008.</para>

<itemizedlist>

<listitem><para>Clauses 3 and 4 of the BSD license used by the project were
dropped.  All the code is now under a 2-clause BSD license compatible with
the GNU General Public License (GPL).</para></listitem>

<listitem><para>Added a C-only binding so that binary test programs do not
need to be tied to C++ at all.  This binding is now known as the atf-c
library.</para></listitem>

<listitem><para>Renamed the C++ binding to atf-c++ for consistency with the
new atf-c.</para></listitem>

<listitem><para>Renamed the POSIX shell binding to atf-sh for consistency
with the new atf-c and atf-c++.</para></listitem>

<listitem><para>Added a -w flag to test programs through which it is
possible to specify the work directory to be used.  This was possible in
prior releases by defining the workdir configuration variable (-v
workdir=...), but was a conceptually incorrect mechanism.</para></listitem>

<listitem><para>Test programs now preserve the execution order of test
cases when they are given in the command line.  Even those mentioned more
than once are executed multiple times to comply with the user's
requests.</para></listitem>

</itemizedlist>

</section>

<section id="atf-0-4">

<title>Changes in version 0.4</title>

<para>Experimental version released on February 4th, 2008.</para>

<itemizedlist>

<listitem><para>Added two new manual pages, atf-c++-api and atf-sh-api,
describing the C++ and POSIX shell interfaces used to write test
programs.</para></listitem>

<listitem><para>Added a pkg-config file, useful to get the flags to build
against the C++ library or to easily detect the presence of
ATF.</para></listitem>

<listitem><para>Added a way for test cases to require a specific
architecture and/or machine type through the new 'require.arch' and
'require.machine' meta-data properties, respectively.</para></listitem>

<listitem><para>Added the 'timeout' property to test cases, useful to set
an upper-bound limit for the test's run time and thus prevent global test
program stalls due to the test case's misbehavior.</para></listitem>

<listitem><para>Added the atf-exec(1) internal utility, used to execute a
command after changing the process group it belongs to.</para></listitem>

<listitem><para>Added the atf-killpg(1) internal utility, used to kill
process groups.</para></listitem>

<listitem><para>Multiple portability fixes.  Of special interest, full
support for SunOS (Solaris Express Developer Edition 2007/09) using the Sun
Studio 12 C++ compiler.</para></listitem>

<listitem><para>Fixed a serious bug that prevented atf-run(1) from working
at all under Fedora 8 x86_64.  Due to the nature of the bug, other
platforms were likely affected too.</para></listitem>

</itemizedlist>

</section>

<section id="atf-0-3">

<title>Changes in version 0.3</title>

<para>Experimental version released on November 11th, 2007.</para>

<itemizedlist>

<listitem><para>Added XML output support to atf-report.  This is
accompanied by a DTD for the format's structure and sample XSLT/CSS files
to post-process this output and convert it to a plain HTML
report.</para></listitem>

<listitem><para>Changed atf-run to add system information to the report it
generates.  This is currently used by atf-report's XML output only, and is
later printed in the HTML reports in a nice and useful summary table.  The
user and system administrator are allowed to tune this feature by means of
hooks.</para></listitem>

<listitem><para>Removed the test cases' 'isolated' property.  This was
intended to avoid touching the file system at all when running the related
test case, but this has not been true for a long while: some control files
are unconditionally required for several purposes, and we cannot easily get
rid of them.  This way we remove several critical and delicate pieces of
code.</para></listitem>

<listitem><para>Improved atf-report's CSV output format to include
information about test programs too.</para></listitem>

<listitem><para>Fixed the tests that used atf-compile to not require this
tool as a helper.  Avoids systems without build-time utilities to skip many
tests that could otherwise be run.  (E.g. NetBSD without the comp.tgz set
installed.)</para></listitem>

<listitem><para>Many general cleanups: Fixed many pieces of code marked as
ugly and/or incomplete.</para></listitem>

</itemizedlist>

</section>

<section id="atf-0-2">

<title>Changes in version 0.2</title>

<para>Experimental version released on September 20th, 2007.</para>

<itemizedlist>

<listitem><para>Test cases now get a known umask on
entry.</para></listitem>

<listitem><para>atf-run now detects many unexpected failures caused by test
programs and reports them as bogus tests.  atf-report is able to handle
these new errors and nicely reports them to the user.</para></listitem>

<listitem><para>All the data formats read and written by the tools have
been documented and cleaned up.  These include those grammars that define
how the different components communicate with each other as well as the
format of files written by the developers and users: the Atffiles and the
configuration files.</para></listitem>

<listitem><para>Added the atf-version tool, a utility that displays
information about the currently installed version of ATF.</para></listitem>

<listitem><para>Test cases can now define an optional cleanup routine to
undo their actions regardless of their exit status.</para></listitem>

<listitem><para>atf-report now summarizes the list of failed (bogus) test
programs when using the ticker output format.</para></listitem>

<listitem><para>Test programs now capture some termination signals and
clean up any temporary files before exiting the program.</para></listitem>

<listitem><para>Multiple bug fixes and improvements all
around.</para></listitem>

</itemizedlist>

</section>

<section id="atf-0-1">

<title>Changes in version 0.1</title>

<para>Experimental version released on August 20th, 2007.</para>

<itemizedlist>

<listitem><para>First public version.  This was released coinciding with
the end of the Google Summer of Code 2007 program.</para></listitem>

</itemizedlist>

</section>

</article>
@


1.1
log
@Initial revision
@
text
@@


1.1.1.1
log
@Import atf 0.7.  Changes in this release:

* Added build-time checks to atf-c and atf-c++.  A binding for atf-sh
  will come later.

* Migrated all build-time checks for header files to proper ATF tests.
  This demonstrates the use of the new feature described above.

* Added an internal API for child process management.

* Converted all plain-text distribution documents to a Docbook canonical
  version, and include pre-generated plain text and HTML copies in the
  distribution file.

* Simplified the contents of the Makefile.am by regenerating it from a
  canonical Makefile.am.m4 source.  As a side-effect, some dependency
  specifications were fixed.

* Migrated all checks from the check target to installcheck, as these
  require ATF to be installed.

* Fixed sign comparison mismatches triggered by the now-enabled
  -Wsign-compare.

* Fixed many memory and object leaks.
@
text
@@


1.1.1.2
log
@Import atf 0.8.  Changes in this release:

* Test programs no longer run several test cases in a row. The execution
  of a test program now requires a test case name, and that single test
  case is executed. To execute several test cases, use the atf-run
  utility as usual.

* Test programs no longer fork a subprocess to isolate the execution of
  test cases. They run the test case code in-process, and a crash of the
  test case will result in a crash of the test program. This is to ease
  debugging of faulty test cases.

* Test programs no longer isolate their test cases. This means that they
  will not create temporary directories nor sanitize the environment any
  more. Yes: running a test case that depends on system state by hand
  will most likely yield different results depending on where (machine,
  directory, user environment, etc.) it is run. Isolation has been moved
  to atf-run.

* Test programs no longer print a cryptic format (application/X-atf-tcs)
  on a special file channel. They can now print whatever they want on
  the screen. Because test programs can now only run one test case every
  time, providing controlled output is not necessary any more.

* Test programs no longer write their status into a special file
  descriptor. Instead, they create a file with the results, which is
  later parsed by atf-run. This changes the semantics of the -r flag.

* atf-run has been adjusted to perform the test case isolation. As a
  result, there is now a single canonical place that implements the
  isolation of test caes. In previous releases, the three language
  bindings (C, C++ and shell) had to be kept in sync with each other
  (read: not a nice thing to do at all). As a side effect of this
  change, writing bindings for other languages will be much, much easier
  from now on.

* atf-run forks test programs on a test case basis, instead of on a test
  program basis as it did before. This is to provide the test case
  isolation that was before implemented by the test programs themselves.

* Removed the atf-exec tool. This was used to implement test case
  isolation in atf-sh, but it is now unnecessary.

* It is now optional to define the descr meta-data property. It has been
  proven to be mostly useless, because test cases often carry a
  descriptive name of their own.
@
text
@a18 60
<section id="atf-0-8">

<title>Changes in version 0.8</title>

<para>Experimental version released on May 7th, 2010.</para>

<itemizedlist>

<listitem><para>Test programs no longer run several test cases in a row.
The execution of a test program now requires a test case name, and that
single test case is executed.  To execute several test cases, use the
atf-run utility as usual.</para></listitem>

<listitem><para>Test programs no longer fork a subprocess to isolate the
execution of test cases.  They run the test case code in-process, and a
crash of the test case will result in a crash of the test program.  This is
to ease debugging of faulty test cases.</para></listitem>

<listitem><para>Test programs no longer isolate their test cases.  This
means that they will not create temporary directories nor sanitize the
environment any more.  Yes: running a test case that depends on system
state by hand will most likely yield different results depending on where
(machine, directory, user environment, etc.) it is run.  Isolation has been
moved to atf-run.</para></listitem>

<listitem><para>Test programs no longer print a cryptic format
(<literal>application/X-atf-tcs</literal>) on a special file channel.  They
can now print whatever they want on the screen.  Because test programs can
now only run one test case every time, providing controlled output is not
necessary any more.</para></listitem>

<listitem><para>Test programs no longer write their status into a special
file descriptor.  Instead, they create a file with the results, which is
later parsed by atf-run.  This changes the semantics of the
<literal>-r</literal> flag.</para></listitem>

<listitem><para>atf-run has been adjusted to perform the test case
isolation.  As a result, there is now a single canonical place that
implements the isolation of test caes.  In previous releases, the three
language bindings (C, C++ and shell) had to be kept in sync with each other
(read: not a nice thing to do at all).  As a side effect of this change,
writing bindings for other languages will be much, much easier from now
on.</para></listitem>

<listitem><para>atf-run forks test programs on a test case basis, instead
of on a test program basis as it did before.  This is to provide the
test case isolation that was before implemented by the test programs
themselves.</para></listitem>

<listitem><para>Removed the atf-exec tool.  This was used to implement test
case isolation in atf-sh, but it is now unnecessary.</para></listitem>

<listitem><para>It is now optional to define the <literal>descr</literal>
meta-data property.  It has been proven to be mostly useless, because test
cases often carry a descriptive name of their own.</para></listitem>

</itemizedlist>

</section>

@


1.1.1.3
log
@Import atf 0.9:

* Added atf-sh, an interpreter to process test programs written using
  the shell API. This is not really a shell interpreter by itself
  though: it is just a wrapper around the system shell that eases the
  loading of the necessary ATF libraries.

* Removed atf-compile in favour of atf-sh.

* Added the use.fs metadata property to test case, which is used to
  specify which test cases require file system access. This is to
  highlight dependencies on external resources more clearly and to speed
  up the execution of test suites by skipping the creation of many
  unnecessary work directories.

* Fixed test programs to get a sane default value for their source
  directory. This means that it should not be necessary any more to pass
  -s when running test programs that do not live in the current
  directory.

* Defining test case headers became optional. This is trivial to achieve
  in shell-based tests but a bit ugly in C and C++. In C, use the new
  ATF_TC_WITHOUT_HEAD macro to define the test case, and in C++ use
  ATF_TEST_CASE_WITHOUT_HEAD.
@
text
@a18 36
<section id="atf-0-9">

<title>Changes in version 0.9</title>

<para>Experimental version released on June 3rd, 2010.</para>

<itemizedlist>

<listitem><para>Added atf-sh, an interpreter to process test programs
written using the shell API.  This is not really a shell interpreter by
itself though: it is just a wrapper around the system shell that eases
the loading of the necessary ATF libraries.</para></listitem>

<listitem><para>Removed atf-compile in favour of atf-sh.</para></listitem>

<listitem><para>Added the <literal>use.fs</literal> metadata property to
test case, which is used to specify which test cases require file system
access.  This is to highlight dependencies on external resources more
clearly and to speed up the execution of test suites by skipping the
creation of many unnecessary work directories.</para></listitem>

<listitem><para>Fixed test programs to get a sane default value for their
source directory.  This means that it should not be necessary any more to
pass <literal>-s</literal> when running test programs that do not live in
the current directory.</para></listitem>

<listitem><para>Defining test case headers became optional.  This is
trivial to achieve in shell-based tests but a bit ugly in C and C++.  In
C, use the new <literal>ATF_TC_WITHOUT_HEAD</literal> macro to define the
test case, and in C++ use
<literal>ATF_TEST_CASE_WITHOUT_HEAD</literal>.</para></listitem>

</itemizedlist>

</section>

@