Free tests for multiple sclerosis software for linux

Test::Simple is a Perl module with basic utilities for writing tests.

SYNOPSIS

use Test::Simple tests => 1;

ok( $foo eq $bar, foo is bar );

** If you are unfamiliar with testing read Test::Tutorial first! **

This is an extremely simple, extremely basic module for writing tests suitable for CPAN modules and other pursuits. If you wish to do more complicated testing, use the Test::More module (a drop-in replacement for this one).
The basic unit of Perl testing is the ok. For each thing you want to test your program will print out an "ok" or "not ok" to indicate pass or fail. You do this with the ok() function (see below).

The only other constraint is you must pre-declare how many tests you plan to run. This is in case something goes horribly wrong during the test and your test program aborts, or skips a test or whatever. You do this like so:

use Test::Simple tests => 23;

You must have a plan.

ok
ok( $foo eq $bar, $name );
ok( $foo eq $bar );

ok() is given an expression (in this case $foo eq $bar). If its true, the test passed. If its false, it didnt. Thats about it.

ok() prints out either "ok" or "not ok" along with a test number (it keeps track of that for you).

# This produces "ok 1 - Hell not yet frozen over" (or not ok)
ok( get_temperature($hell) > 0, Hell not yet frozen over );

If you provide a $name, that will be printed along with the "ok/not ok" to make it easier to find your test when if fails (just search for the name). It also makes it easier for the next guy to understand what your test is for. Its highly recommended you use test names.

All tests are run in scalar context. So this:

ok( @stuff, I have some stuff );
will do what you mean (fail if stuff is empty)

Test::Simple will start by printing number of tests run in the form "1..M" (so "1..5" means youre going to run 5 tests). This strange format lets Test::Harness know how many tests you plan on running in case something goes horribly wrong.
If all your tests passed, Test::Simple will exit with zero (which is normal). If anything failed it will exit with how many failed. If you run less (or more) tests than you planned, the missing (or extras) will be considered failures. If no tests were ever run Test::Simple will throw a warning and exit with 255. If the test died, even after having successfully completed all its tests, it will still be considered a failure and will exit with 255.

So the exit codes are...
0 all tests successful
255 test died or all passed but wrong # of tests run
any other number how many failed (including missing or extras)

If you fail more than 254 tests, it will be reported as 254.

This module is by no means trying to be a complete testing system. Its just to get you started. Once youre off the ground its recommended you look at Test::More.

FITpro for Eclipse allows easier creation of FIT tests and suites, more flexible test execution, and more.
Main features:
- Create Fit tests in WYSWIG HTML Editor
- Create suites, ordered collections of Fit tests and sub-suites.
- Execute tests and suites.
- Link from tests to related fixtures.
- Insert Test Template into a Fit test, based on an existing fixture.

Test::Tail::Multi is a Perl module to execute code, monitor dynamic file contents.

SYNOPSIS

use Test::Tail::Multi files => [qw(file1 file2)] tests=>2;
# Can add files dynamically as well
add_file(file3, "decided to add file3 too");

# Execute a command and check against output
contents_like {system(my_command -my_args")} # Note no trailing comma!
qr/expected value/,
"got the expected output");

# if code to execute is undef, check against previously captured new content
contents_unlike undef, # trailing command REQUIRED
qr/unexpected text/,
"unexpected stuff not found in same text");

# Shorten the delay to 1 second.
delay(1, "Now a 1 second delay");
contents_like(sub {system(fast_command)}, # trailing comma in parens
qr/expected/,
"this command runs faster");

Test::Tail::Multi allows you to create tests or test classes that permit you to monitor the contents of one or more files a la < tail -f > using the nice File::Tail module. You can execute arbitrary code and then run tests versus the new content in the files.
If you choose, you can run multiple tests against the same content by passing undef as the code to be executed; Test::Tail::Multi will then reuse the contents it last extracted.

You can also adjust the delay time to be used to allow the code you called to "settle down" before checking the tails.

Test::Tail::Multi comes in handy for those testing jobs that require you to monitor several files at once to see whats happening in each one.

Test::LectroTest is a Perl module with easy, automatic, specification-based tests.

SYNOPSIS

#!/usr/bin/perl -w

use MyModule; # contains code we want to test
use Test::LectroTest;

Property {
##[ x "my_function output is non-negative" ;

Property { ... }, name => "yet another property" ;

# more properties to check here

This module provides a simple (yet full featured) interface to LectroTest, an automated, specification-based testing system for Perl. To use it, declare properties that specify the expected behavior of your software. LectroTest then checks your software to see whether those properties hold.
Declare properties using the Property function, which takes a block of code and promotes it to a Test::LectroTest::Property:

Property {
##[ x "my_function output is non-negative" ;

The first part of the block must contain a generator-binding declaration. For example:

##[ x<<less