Free test data 1.20 software for linux

DBD::Teradata is Perl module with a DBI driver for Teradata.

SYNOPSIS

use DBI;

$dbh = DBI->connect(dbi:Teradata:hostname, user, password);
See DBI for more information.

Refer to the included tdatdbd.html.

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.

Test::Tech is a Perl module that adds skip_tests and test data structures capabilities to the "Test" module.

SYNOPSIS

#######
# Procedural (subroutine) Interface
#
# (use for &Test::plan, &Test::ok, &Test::skip drop in)
#
use Test::Tech qw(demo finish is_skip ok ok_sub plan skip skip_sub
skip_tests stringify tech_config);

demo($quoted_expression, @expression);

(@stats) = finish( );
$num_passed = finish( );

$skip_on = is_skip( );
($skip_on, $skip_diag) = is_skip( );

$test_ok = ok($actual_results, $expected_results, [@options]);
$test_ok = ok($actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = ok($actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$test_ok = ok_sub(⊂routine, $actual_results, $expected_results, [@options]);
$test_ok = ok_sub(⊂routine, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = ok_sub(⊂routine, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$success = plan(@args);

$test_ok = skip($skip_test, $actual_results, $expected_results, [@options]);
$test_ok = skip($skip_test, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = skip($skip_test, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$test_ok = skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, [@options]);
$test_ok = skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$skip_on = skip_tests( $on_off, $skip_diagnostic);
$skip_on = skip_tests( $on_off );
$skip_on = skip_tests( );

$string = stringify($var, @options); # imported from Data::Secs2

$new_value = tech_config( $key, $old_value);

#####
# Object Interface
#
$tech = new Test::Tech;

$tech->demo($quoted_expression, @expression)

(@stats) = $tech->finish( );
$num_passed = $tech->finish( );

$skip_on = $tech->is_skip( );
($skip_on, $skip_diag) = $tech->is_skip( );

$test_ok = $tech->ok($actual_results, $expected_results, [@options]);
$test_ok = $tech->ok($actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = $tech->ok($actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$test_ok = $tech->ok_sub(⊂routine, $actual_results, $expected_results, [@options]);
$test_ok = $tech->ok_sub(⊂routine, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = $tech->ok_sub(⊂routine, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$success = $tech->plan(@args);

$test_ok = $tech->skip($skip_test, $actual_results, $expected_results, [@options]);
$test_ok = $tech->skip($skip_test, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = $tech->skip($skip_test, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$test_ok = $tech->skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, [@options]);
$test_ok = $tech->skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, $diagnostic, [@options]);
$test_ok = $tech->skip_sub(⊂routine, $skip_test, $actual_results, $expected_results, $diagnostic, $test_name, [@options]);

$state = $tech->skip_tests( );
$state = $tech->skip_tests( $on_off );

$state = skip_tests( $on_off, $skip_diagnostic );

$string = $tech->stringify($var, @options); # imported from Data::Secs2

$new_value = $tech->tech_config($key, $old_value);

Generally, if a subroutine will process a list of options, @options, that subroutine will also process an array reference, @options, [@options], or hash reference, %options, {@options}. If a subroutine will process an array reference, @options, [@options], that subroutine will also process a hash reference, %options, {@options}. See the description for a subroutine for details and exceptions.

Test::STDmaker is a Perl module to generate test scripts, demo scripts from a test description short hand.

SYNOPSIS

#######
# Procedural (subroutine) interface
#
use Test::STDmake qw(find_t_roots get_data perl_command);

@t_path = find_t_paths()
$date = get_date();
$myperl = perl_command();

#####
# Class interface
#
use Test::STDmaker

$std = new Test::STDmaker( @options ); # From File::Maker

$success = $std->check_db($std_pm);
@t_path = $std->find_t_paths()
$date = $std->get_date();
$myperl = $std->perl_command();

$std->tmake( @targets, %options );
$std->tmake( @targets );
$std->tmake( %options );

######
# Internal (Private) Methods
#
$success = $std->build($std_driver_class);
$success = $std->generate();
$success = $std->print($file_out);

The Test::STDmaker program module provides the following capabilities:
Automate Perl related programming needed to create a test script resulting in reduction of time and cost.

Translate a short hand Software Test Description (STD) file into a Perl test script that eventually makes use of the Test module.

Translate the sort hand STD data file into a Perl demo script that demonstrates the features of the the module under test.

Provide in the POD of a STD file information required by a Military/Federal Government Software Test Description (STD) document that may easily be index and accessed by automated Test software. ISO, British Military require most of the same information, US agencies such as the FAA. The difference is that ISO, British Military do not dictate detail format. US agencies such as FAA will generally tailor down the DOD required formats.

Thus, there is an extremely wide variation in the format of the same information among ISO certified comericial activities and militaries other than US. Once the information is in a POD, different translators may format nearly exactly as dictated by the end user, whether it is the US DOD, ISO certified commericial activity, British Military or whoever. By being able to provide the most demanding, which is usually US DOD, the capabilities are there for all the others.

The Test::STDmaker package relieves the designer and developer from the burden of filling out word processor boiler plate templates (whether run-off, Word, or vi), counting oks, providing documentation examples, tracing tests to test requirments, making sure it is in the proper corporate, ISO or military format, and other such extremely time consuming, boring, development support tasks. Instead the designers and developers need only to fill in a form using a test description short hand. The Test::STDmaker will take it from there and automatically and quickly generate the desired test scripts, demo scripts, and test description documents.

Look at the economics. It does not make economically sense to have expensive talent do this work. In does not even make economically sense to take a bright 16 year, at mimimum wage and have him manually count oks. Perl can count those oks much much cheaper and it is so easily to automated with Perl. And something like this were you are doing it year in and year out, the saving are enormous. To a program manager or contract officer, this is what programming and computers are all about, saving money and increasing productivity, not object oriented oriented programing, gotos or other such things.

The Test::STDmaker class package automates the generation of Software Test Descriptions (STD) Plain Old Documentation (POD), test scripts, demonstrations scripts and the execution of the generated test scripts and demonstration scripts. It will automatically insert the output from the demonstration script into the POD -headx Demonstration section of the file being tested.

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::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.

HOL-TestGen allows one to write test specifications in Higher-order logics (HOL). It can (semi-) automatically partition the input space, resulting in abstract test cases, and automatically select concrete test data.
Automatic generation of test harnesses (in SML) is supported, and using a foreign language interface, implementations in arbitrary languages (e.g. C) can be tested.
Main features:
- write test specifications in Higher-order logics (HOL)
- (semi-) automatically partition the input space, resulting in abstract test cases
- automatically select concrete test data
- automatically generate test scripts (in SML)
- using a foreign language interface, implementations in arbitrary languages (e.g. C) can be tested.
HOL-OCL is free software; you can redistribute it and/or modify it under the terms of the GPL. HOL-TestGen project is developed by Achim D. Brucker and Burkhart Wolff.
Enhancements:
- This release extends the configuration possibilities of the code generator, and includes an example demonstrating sequence testing.