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
Test::Exit(3pm) 					User Contributed Perl Documentation					   Test::Exit(3pm)

NAME
Test::Exit - Test that some code calls exit() without terminating testing VERSION
version 0.03 SYNOPSIS
use Test::More tests => 4; use Test::Exit; exits_ok { exit 1; } "exiting exits" never_exits_ok { print "Hi!"; } "not exiting doesn't exit" exits_zero { exit 0; } "exited with success" exits_nonzero { exit 42; } "exited with failure" DESCRIPTION
Test::Exit provides some simple tools for testing that code does or does not call "exit()", while stopping code that does exit at the point of the "exit()". Currently it does so by means of exceptions, so it will not function properly if the code under test calls "exit()" inside of an "eval" block or string. The only criterion tested is that the supplied code does or does not call "exit()". If the code throws an exception, the exception will be propagated and you will have to call it yourself. "die()"ing is not exiting for the purpose of these tests. exits_ok Tests that the supplied code calls "exit()" at some point. exits_nonzero Tests that the supplied code calls "exit()" with a nonzero value. exits_zero Tests that the supplied code calls "exit()" with a zero (successful) value. never_exits_ok Tests that the supplied code completes without calling "exit()". AUTHOR
Andrew Rodland <andrew@hbslabs.com> COPYRIGHT AND LICENSE
This software is copyright (c) 2009 by HBS Labs, LLC.. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.10.1 2009-12-04 Test::Exit(3pm)