05:27 Muhammad Moinur Rahman (bofh) 

devel/atf: Switch to FreeBSD upstream

- As per the recent discussion switch to the FreeBSD upstream
- For now resetting MAINTAINER to myself with ci@ hat on but anyone from
  ci@ feel free to commit
- Pet port{clippy|fmt}

PR:		276071
Approved by:	jmmv (private mail)

    46cb35f

16:39 jmmv 

Update devel/atf to 0.21.

Released on October 23rd, 2014.

* Restored the atf(7) manual page to serve as a reference to all the other
  manual pages shipped by ATF.

* Added the -s flag to atf-sh to support specifying the shell interpreter
  to be used.

* Removed ATF_WORKDIR.  The only remaining consumers have been converted to
  use the standard TMPDIR environment variable.  As a benefit, and because
  Kyua forces the TMPDIR to live within the test case's work directory,
  any stale files left behind by ATF will be automatically cleaned up.

* Documented the environment variables recognized by each component in the
  relevant manual pages.  This information was lost with the atf-config(1)
  removal.

* Added a new "require.diskspace" metadata property to test cases so that
  they can specify the minimum amount of disk space required for the test
  to run.

* Renamed the atf-{c,c++,sh}-api(3) manual pages to atf-{c,c++,sh}(3) for
  discoverability purposes.  Symbolic links are provided for the time
  being to still make the old names visible.

* Issue #5: Recommend the (expected, actual) idiom for calls to the test
  macros in the manual pages.

* Issue #7: Stopped catching unhandled exceptions in atf-c++ tests.  This
  propagates the crash to the caller, which in turn allows it to obtain
  proper debugging information.  In particular, Kyua should now be able to
  extract a stacktrace pinpointing the problem.

* Issue #8: Fixed atf-c/macros_test:use test failures spotted by the clang
  that ships with FreeBSD 11.0-CURRENT.

* Issue #12: Improved documentation of atf-sh(3) and atf-check(1) by better
  explaining how they relate to each other.

* Issue #14: Stopped setting 'set -e' in atf-sh.  This setting was
  initially added as a way to enable a "strict" mode in the library and to
  make test cases fail fast when they run unprotected commands.  However,
  doing so in the library is surprising as the responsibility of enabling
  'set -e' should be on the user's code.  Also, 'set -e' introduces
  inconsistent behavior on subshells and users do not expect that.

* Issue #15: Fixed atf_utils_{fork,wait} to support nested calls.

* Issue #16: Fixed test failures (by removing a long-standing hack) on
  systems that lack \e support in printf(1).

* Issue #19: Removed stale references to atf-config and atf-run.

Differential Revision:	https://reviews.freebsd.org/D1001
Approved by:	bapt

 

17:03 jmmv 

Update devel/atf to 0.20 and modernize the port.

This includes:
- Taking ownership of the package (with ack from previous maintainer).
- Forcing all file registrations into pkg-plist.
- Fully dropping support for the deprecated tools.
- Adding support for the TEST option.
- Properly using libtool via USES.
- Not using OSREVISION to determine whether atf can or can't be installed.
- Avoiding Makefile.in hacks by just using MAKE_FLAGS.

... which basically means this really is a full rewrite of the port.

Approved by:	bapt, bdrewery

 

22:58 bdrewery 

The Automated Testing Framework (ATF) is a collection of libraries and
utilities designed to ease unattended application testing in the hands of
developers and end users of a specific piece of software.

As regards developers, ATF provides the necessary means to easily create
test suites composed of multiple test programs, which in turn are a
collection of test cases.  It also attempts to simplify the debugging of
problems when these test cases detect an error by providing as much
information as possible about the failure.

As regards users, it simplifies the process of running the test suites and,
in special, encourages end users to run them often: they do not need to
have source trees around nor any other development tools installed to be
able to certify that a given piece of software works on their machine as
advertised.

Note that ATF is included in the base system since FreeBSD 10, so this
port does not need to be installed on FreeBSD 10.

WWW: http://code.google.com/p/kyua/wiki/ATF

PR:		ports/173197
Submitted by:	Roman Naumann <namor@hemio.de>
Reviewed by:	bapt, eadler
Feature safe:	yes