Kyua 0.11: Major cleanup release (bug fixes, doc improvements)
Changes in version 0.11
Released on October 23rd, 2014.
- Added support to print the details of all test cases (metadata and
their output) to 'report'. This is via a new '--verbose' flag which
replaces the previous '--show-context'. - Added support to specify the amount of physical disk space required
by a test case. This is in the form of a new "required_disk_space"
metadata property, which can also be provided by ATF test cases as
"require.diskspace". - Assimilated the contents of all the kyua--tester(1) and
kyua--interface(7) manual pages into more relevant places. In
particular, added more details on test program registration and their
metadata to kyuafile(5), and added kyua-test-isolation(7) describing
the isolation features of the test execution. - Assimilated the contents of all auxiliary manual pages, including
kyua-build-root(7), kyua-results-files(7), kyua-test-filters(7) and
kyua-test-isolation(7), into the relevant command-specific manual
pages. This is for easier discoverability of relevant information
when reading how specific Kyua commands work. - Issue 30: Plumbed through support to query configuration variables
from ATF's test case heads. This resolves the confusing situation
where test cases could only do this from their body and cleanup
routines. - Issue 49: Extended 'report' to support test case filters as
command-line arguments. Combined with '--verbose', this allows
inspecting the details of a test case failure after execution. - Issue 55: Deprecated support for specifying test_suite overrides on
a test program basis. This idiom should not be used but support for
it remains in place. - Issue 72: Added caching support to the getcwd(3) test in configure so
that the result can be overriden for cross-compilation purposes. - Issue 83: Changed manual page headings to include a "kyua" prefix in
their name. This prevents some possible confusion when displaying,
for example, the "kyua-test" manual page with a plain name of "test". - Issue 84: Started passing test-suite configuration variables to plain
and TAP test programs via the environment. The name of the
environment variables set this way is prefixed by TEST_ENV_, so a
configuration variable of the form
'test_suites.some_name.allow_unsafe_ops=yes' in kyua.conf becomes
'TEST_ENV_allow_unsafe_ops=YES' in the environment. - Issue 97 and 116: Fixed the build on Illumos.
- Issue 102: Set TMPDIR to the test case's work directory when running
the test case. If the test case happens to use the mktemp(3) family
of functions (due to misunderstandings on how Kyua works or due to
the reuse of legacy test code), we don't want it to easily escape the
automanaged work directory. - Issue 103: Started being more liberal in the parsing of TAP test
results by treating the number in 'ok' and 'not ok' lines as optional. - Issue 105: Started using tmpfs instead of md as a temporary file
system for tests in FreeBSD so that we do not leak md(4) devices. - Issue 109: Changed the privilege dropping code to start properly
dropping group privileges when unprivileged_user is set. Also fixes
testers/run_test:fork_wait__unprivileged_group. - Issue 110: Changed 'help' to display version information and clarified
the purpose of the 'about' command in its documentation. - Issue 111: Fixed crash when defining a test program in a Kyuafile that
has not yet specified the test suite name. - Issue 114: Improved the kyuafile(5) manual page by clarifying the
restrictions of the include() directive and by adding abundant
examples.