Free tests in print software for linux

Test soon project is a testing framework trying to enable you to write tests quickly, organize them easily and still being flexible.

The goal is to utilize the strengths of C++ while minimizing the impact of its weaknesses.

Test::Singleton is a test for Singleton classes.

SYNOPSIS

use Test::More tests => 1;
use Test::Singleton;
is_singleton( "Some::Class", "new", "instance" );

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

This is asimple, basic module for checking whether a class is a Singleton. A Singleton describes an object class that can have only one instance in any system. An example of a Singleton might be a print spooler or system registry, or any kind of central dispatcher.

For a description and discussion of the Singleton class, see "Design Patterns", Gamma et al, Addison-Wesley, 1995, ISBN 0-201-63361-2.

Holodeck10 is built using JAVA for the Linux Operating system. Holodeck10 Image Print utilizes the log4j package from the Free Software Foundation (www.apache.org) to facilitate logging of debuging information.

The project takes advantage of the ImageIO class to reduce the memory consumption associated with processing images. The Concurrent package that is now included with JAVA 1.5 is utilized to handle multi-threading of the processing.

Holodeck10 allows the user to select images to be set on a standard LETTER sized page to be printed in either LANDSCAPE or PORTRAIT orientation and then printed. The current version supports layouts of 1x1, 1x2, 2x2, 2x3, 4x5, and 6x8 in either LANDSCAPE or PORTRAIT.

The software uses a filechooser with a filefilter to display the image files that are available. Currently the filefilter allows for the selection of *.gif, *.jpg, *.jpeg, *.xcf, *.xpm, and *.png files.

The SimpleDocument interface in JAVA is used to format the page for printing.

Test::Manifest is a Perl module created to interact with a t/test_manifest file.

SYNOPSIS

# in Makefile.PL
eval "use Test::Manifest";

# in the file t/test_manifest, list the tests you want
# to run

Test::Harness assumes that you want to run all of the .t files in the t/ directory in ascii-betical order during make test unless you say otherwise. This leads to some interesting naming schemes for test files to get them in the desired order. This interesting names ossify when they get into source control, and get even more interesting as more tests show up.

Test::Manifest overrides the default behaviour by replacing the test_via_harness target in the Makefile. Instead of running at the t/*.t files in ascii-betical order, it looks in the t/test_manifest file to find out which tests you want to run and the order in which you want to run them. It constructs the right value for MakeMaker to do the right thing.

In t/test_manifest, simply list the tests that you want to run. Their order in the file is the order in which they run. You can comment lines with a #, just like in Perl, and Test::Manifest will strip leading and trailing whitespace from each line. It also checks that the specified file is actually in the t/ directory. If the file does not exist, it does not put its name in the list of test files to run.

Optionally, you can add a number after the test name in test_manifest to define sets of tests. See get_t_files() for more information.

Functions

run_t_manifest( TEST_VERBOSE, INST_LIB, INST_ARCHLIB, TEST_LEVEL )

Run all of the files in t/test_manifest through Test::Harness:runtests in the order they appear in the file.

eval "use Test::Manifest";
get_t_files( [LEVEL] )

In scalar context it returns a single string that you can use directly in WriteMakefile(). In list context it returns a list of the files it found in t/test_manifest.

If a t/test_manifest file does not exist, get_t_files() returns nothing.
get_t_files() warns you if it cant find t/test_manifest, or if entries start with "t/". It skips blank lines, and strips Perl style comments from the file.

Each line in t/test_manifest can have three parts: the test name, the test level (a floating point number), and a comment. By default, the test level is 1.

test_name.t 2 #Run this only for level 2 testing

Without an argument, get_t_files() returns all the test files it finds. With an argument that is true (so you cant use 0 as a level) and is a number, it skips tests with a level greater than that argument. You can then define sets of tests and choose a set to run. For instance, you might create a set for end users, but also add on a set for deeper testing for developers.

Experimentally, you can include a command to grab test names from another file. The command starts with a ; to distinguish it from a true filename. The filename (currently) is relative to the current working directory, unlike the filenames, which are relative to t/. The filenames in the included are still relative to t/.

;include t/file_with_other_test_names.txt

To select sets of tests, specify the level in the variable TEST_LEVEL during `make test`.

make test # run all tests no matter the level
make test TEST_LEVEL=2 # run all tests level 2 and below

make_test_manifest()

Creates the test_manifest file in the t directory by reading the contents of the t directory.

TO DO: specify tests in argument lists.

TO DO: specify files to skip.

manifest_name()

Returns the name of the test manifest file, relative to t/

Test-Run is an improved test harness for scripts that emit TAP (Test Anything Protocol). It was forked from Test::Harness, and it uses TAP::Parser.

The project is used to analyze the output of the scripts and present it to the user in a summarized form. Test-Run features separation of the test-running backend and the command line frontend, a "runprove" utility for running tests from the command line, a plugin-system, and colors for the summary line.

Test::Parser is a collection of parsers for different test output file formats.
These parse the data into a general purpose data structure that can then be used to create reports, do post-processing analysis, etc.
Test::Parser can also export tests in SpikeSources TRPI test description XML language.
Installation:
To install the script and man pages in the standard areas, give the sequence of commands
$ perl Makefile.PL
$ make
$ make test
$ make install # you probably need to do this step as superuser
If you want to install the script in your own private space, use
$ perl Makefile.PL PREFIX=/home/joeuser
INSTALLMAN1DIR=/home/joeuser/man/man1
INSTALLMAN3DIR=/home/joeuser/man/man3
$ make
$ make test
$ make install # can do this step as joeuser
Note that `make test` does nothing interesting.
Enhancements:
- This release improves the LTP parser and adds a parse_ltp script that prints a tabular summary of the PASS/FAILs of test cases.

Test::C2FIT is a direct Perl port of Ward Cunninghams FIT acceptance test framework for Java.

SYNOPSIS

FileRunner.pl input_containing_fit_tests.html test_results.html

perl -MTest::C2FIT -e file_runner input_containing_fit_tests.html test_results.html

perl -MTest::C2FIT -e fit_shell

Great software requires collaboration and communication. Fit is a tool for enhancing collaboration in software development. Its an invaluable way to collaborate on complicated problems - and get them right - early in development.

Fit allows customers, testers, and programmers to learn what their software should do and what it does do. It automatically compares customers expectations to actual results.

This port of FIT has a featureset equivalent to v1.1 of FIT. Dave W. Smiths original port was based on fit-b021021j and Ive updated most of the core to match the 1.1 version.

This port passes the current FIT spec and also implements a all of the examples.

The following functions are provided (and exported) by this module:
file_runner($infile,$outfile)

Process a FIT-document contained in $infile and writes the result to $outfile.
wiki_runer($infile,$outfile)

Same as file_runner, except that not < table >, < tr > and < td > but < wiki >, < table >, < tr > and < td > is searched for in the input document.

fit_shell

Creates an interactive shell from which you can easily run tests. Start it and enter "help" for more information.

Suppose, your tests-related files reside in a directory with three subdirectories: input - where the files come from, output - where the results will be written to and lib - where your fixtures reside, all you need to do is just to enter "runall"

Logging

The file_runner and wiki_runner support filtering of warn messages, similar to javas common logging. To change the log level, use the -L parameter, e.g.:

perl -MTest::C2FIT -e file_runner -- -L 1 input_containing_fit_tests.html test_results.html

There are following log levels defined: 0 - trace, 1 - debug, 2 - info, 3 - warn, 4 - error, 5 - fatal.

In your code, simply use warn "message" if it should be printed out unconditionally or warn 1, " message" if it should be printed out, when log level is either TRACE or DEBUG.

Naming, Namespace(s)

In your FIT-documents, please use the java-style dot-notation for qualifying package names. E.g. if you want the package Domain::Object::Simple to be used, specify it by entering Domain.Object.Simple into your fit document.
Package names should be fully qualified, case is importat. Special care is taken on the fit.* packages, these can be specified either by fit.Name as well as Test.C2FIT.Name.