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
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)