Automated Testing Framework 0.4 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Automated Testing Framework 0.4 (Default branch)
# 1  
Old 02-05-2008
Automated Testing Framework 0.4 (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 (original) Changes:
This release adds preliminary documentation on the C++ and shell interfaces to write tests, mainly directed to developers wishing to adopt ATF. It adds a way to specify required architectures and machines for given tests through the require.arch and require.machine properties; if the platform running the tests does not fulfill the requirements, the tests are simply skipped. It adds the ability to limit the maximum time a test case can last through the timeout property, killing tests that get stalled. There are many portability fixes, especially to SunOS, and small improvements all around.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)