linbox
checker.C File Reference

script to run LinBox tests More...

#include <cstdlib>
#include <iostream>
#include <fstream>
#include <sstream>
#include <map>
#include <set>
#include <vector>

Detailed Description

script to run LinBox tests

Checker is compiled and run by the check macro invoked by "make fullcheck" in the top source dir or in tests/.

Run without args, each test is build and run, with a one line report of success or failure. A summary at the end reports number of test failing to compile, failing at runtime, and skipped. There should be a 1-1 correspondence between files tests/test-*.C and report lines

A LinBox unit/regresssion test has a default behaviour – when there are no command line file names – in which nothing is written to any output stream and the return value is 0 for a passing test, nonzero for any failure.

The current convention is that (1) linbox' checker.C, runs the tests with no command line parameters at all, and (2) if there is a command line file name, verbose diagnostic output is written to that file and more terse output may be written to standard output streams. The second feature is intended to assist debugging with individual tests.

Checker is compiled and run by the check macro invoked by "make fullcheck" in the top source dir or in tests/.

Run without args, checker prints an explanation of command line options, then proceeds with default test behaviour. "checker -h" just prints the options.

Each LinBox test gets a line below. A LinBox unit/regresssion test has a default behaviour – when there are no command line file names – in which nothing is written to any output stream and the return value is 0 for a passing test, nonzero for any failure.

The current convention is that (1) linbox' check macro, checker.C, runs the tests with no command line parameters at all, and (2) if there is a command line file name, verbose diagnostic output is written to that file and more terse output may be written to standard output streams. The second feature is intended to assist debugging with individual tests.

In future, command line arguments could be used in checking to vary matrix sizes and other parameters in check runs.

There should be a 1-1 correspondence between files tests/test-*.C and calls here to build_n_run() or no_build_n_run() (possibly commented out).