Automated Testing Framework 0.5 (Default branch)


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

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. Tests can currently be written in C/C++ or POSIX shell and, contrary to other testing frameworks, ATF tests are installed into the system alongside any other application files. This allows the end user to easily verify that the software behaves correctly on her system. Furthermore, the results of the test suites can be collected into nicely-formatted reports to simplify their visualization and analysis. License: BSD License (revised) Changes:
The code has been relicensed under a 2-clause BSD license. A new C-only binding (atf-c) has been added so that developers do not need to use C++ at all to write test cases. The C++ binding has been renamed to atf-c++, and the POSIX shell binding to atf-sh for consistency. Test programs now support a -w flag to indicate the work directory they have to use. Test programs now preserve the order of test cases when stated by the user on the command line.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
shlib_debug_enable(5)						File Formats Manual					     shlib_debug_enable(5)

NAME
shlib_debug_enable - dynamically enable or disable online shared library debugging support VALUES
Fail Safe Default semantics is disabled Allowed values DESCRIPTION
This tunable dynamically enables (1) or disables (0) the online shared library debugging feature. When this tunable is enabled, shared libraries of a running (active) application can be debugged. Who Is Expected to Change This Tunable? System administrators and developers who want to change the default behavior of Restrictions on Changing Changes to this tunable take effect immediately. There is no need to reboot the system. When Should the Tunable Be Turned On? When there is a need to debug a shared library of a running (active) application, this tunable can be turned on. When this feature/tunable is not enabled, debugging of shared libraries can be done at application start time through the command. See chatr(1). What Are the Side Effects of Turning the Tunable On? If an application which is being debugged for shared libraries is not MPAS (Mostly Private Address Space) executable, then the application will be converted to an MPAS executable type. After the conversion, all rules which apply to regular MPAS executable type does apply to the converted application until the process exits. The rules apply even after being detached from the debugger. When Should the Tunable Be Turned Off? Administrators and/or developers who will not need the online debugging feature of shared libraries. What Are the Side Effects of Turning the Tunable Off? When this tunable is disabled, then online debugging of shared libraries will not be possible beyond the existing hardware break point facility. With hardware break points, only a limited number of breakpoints can be set. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by HP. SEE ALSO
chatr(1). HP Integrity Systems Only Tunable Kernel Parameters shlib_debug_enable(5)