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
IO::Async::LoopTests(3pm)				User Contributed Perl Documentation				 IO::Async::LoopTests(3pm)

NAME
"IO::Async::LoopTests" - acceptance testing for "IO::Async::Loop" subclasses SYNOPSIS
use IO::Async::LoopTests; run_tests( 'IO::Async::Loop::Shiney', 'io' ); DESCRIPTION
This module contains a collection of test functions for running acceptance tests on IO::Async::Loop subclasses. It is provided as a facility for authors of such subclasses to ensure that the code conforms to the Loop API required by "IO::Async". TIMING
Certain tests require the use of timers or timed delays. Normally these are counted in units of seconds. By setting the environment variable "TEST_QUICK_TIMERS" to some true value, these timers run 10 times quicker, being measured in units of 0.1 seconds instead. This value may be useful when running the tests interactively, to avoid them taking too long. The slower timers are preferred on automated smoke-testing machines, to help guard against false negatives reported simply because of scheduling delays or high system load while testing. TEST_QUICK_TIMERS=1 ./Build test FUNCTIONS
run_tests( $class, @tests ) Runs a test or collection of tests against the loop subclass given. The class being tested is loaded by this function; the containing script does not need to "require" or "use" it first. This function runs "Test::More::plan" to output its expected test count; the containing script should not do this. TEST SUITES
The following test suite names exist, to be passed as a name in the @tests argument to "run_tests": io Tests the Loop's ability to watch filehandles for IO readiness timer Tests the Loop's ability to handle timer events signal Tests the Loop's ability to watch POSIX signals idle Tests the Loop's support for idle handlers child Tests the Loop's support for watching child processes by PID control Tests that the "run", "stop", "loop_once" and "loop_forever" methods behave correctly AUTHOR
Paul Evans <leonerd@leonerd.org.uk> perl v5.14.2 2012-10-24 IO::Async::LoopTests(3pm)