Automated Testing Framework 0.6 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Automated Testing Framework 0.6 (Default branch)
# 1  
Old 01-19-2009
Automated Testing Framework 0.6 (Default branch)

ATF is a collection of libraries and utilitiesdesigned to ease unattended application testing inthe hands of developers and end users of aspecific piece of software. Tests can currently bewritten in C/C++ or POSIX shell and, contrary toother testing frameworks, ATF tests are installedinto the system alongside any other applicationfiles. This allows the end user to easily verifythat the software behaves correctly on her system.Furthermore, the results of the test suites can becollected into nicely-formatted reports tosimplify their visualization and analysis.License: BSD License (revised)Changes:
The atf-check tool has been added, which executes a given command and checks its exit code and output against pre-specified values. This is mostly used internally by the shell interface. A new set of macros, ATF_REQUIRE_*, has been added to the C interface to signal fatal errors, while the old ones (ATF_CHECK_*) now only signal non-fatal errors. There are several other internal changes to make test case timeout control more robust, and multiple optimizations all around the code (especially in the shell code).Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
MAC_TEST(4)						   BSD Kernel Interfaces Manual 					       MAC_TEST(4)

NAME
mac_test -- MAC framework testing policy SYNOPSIS
To compile the testing policy into your kernel, place the following lines in your kernel configuration file: options MAC options MAC_TEST Alternately, to load the testing module at boot time, place the following line in your kernel configuration file: options MAC and in loader.conf(5): mac_test_load="YES" DESCRIPTION
The mac_test policy module implements a testing facility for the MAC framework. Among other things, mac_test will try to catch corrupt labels the system is attempting to destroy and drop to the debugger. Additionally, a set of statistics regarding the number of times various MAC framework entry points have been called is stored in the security.mac.test sysctl(8) tree. Label Format No labels are defined for mac_test. SEE ALSO
mac(4), mac_biba(4), mac_bsdextended(4), mac_ifoff(4), mac_lomac(4), mac_mls(4), mac_none(4), mac_partition(4), mac_portacl(4), mac_seeotheruids(4), mac(9) HISTORY
The mac_test policy module first appeared in FreeBSD 5.0 and was developed by the TrustedBSD Project. AUTHORS
This software was contributed to the FreeBSD Project by Network Associates Labs, the Security Research Division of Network Associates Inc. under DARPA/SPAWAR contract N66001-01-C-8035 (``CBOSS''), as part of the DARPA CHATS research program. BUGS
See mac(9) concerning appropriateness for production use. The TrustedBSD MAC Framework is considered experimental in FreeBSD. While the MAC Framework design is intended to support the containment of the root user, not all attack channels are currently protected by entry point checks. As such, MAC Framework policies should not be relied on, in isolation, to protect against a malicious privileged user. BSD
December 1, 2002 BSD