Free intermediate unit one software for linux

Test::Unit is the main PerlUnit testing framework.

SYNOPSIS

This package provides only the project version number, copyright texts, and a framework overview in POD format.

This framework is intended to support unit testing in an object-oriented development paradigm (with support for inheritance of tests etc.) and is derived from the JUnit testing framework for Java by Kent Beck and Erich Gamma. To start learning how to use this framework, see Test::Unit::TestCase and Test::Unit::TestSuite. (There will also eventually be a tutorial in Test::Unit::Tutorial.

However Test::Unit::Procedural is the procedural style interface to a sophisticated unit testing framework for Perl that . Test::Unit is intended to provide a simpler interface to the framework that is more suitable for use in a scripting style environment. Therefore, Test::Unit does not provide much support for an object-oriented approach to unit testing.

Eunit project is an Erlang test suite tool, inspired by agile development ideas.
Usage:
Launch example unit test with:
erl -config sys.config
and then
eunit:run([eunit_examples], {suffix, "_test"}).
Enhancements:
- This release is a complete rewrite.
- Writing unit tests should now be simpler than with the previous version.
- This release can also be used with the Aegis configuration management system for continuous integration.

Test::Unit::InnerClass is a unit testing framework helper class.

SYNOPSIS

This class is not intended to be used directly

This class is used by the framework to emulate the anonymous inner classes feature of Java. It is much easier to port Java to Perl using this class.

Test::Unit::TestRunner is a unit testing framework helper class.

SYNOPSIS

use Test::Unit::TestRunner;

my $testrunner = Test::Unit::TestRunner->new();
$testrunner->start($my_testcase_class);

This class is the test runner for the command line style use of the testing framework.

It is used by simple command line tools like the TestRunner.pl script provided.
The class needs one argument, which is the name of the class encapsulating the tests to be run.

OPTIONS

-wait
wait for user confirmation between tests

-v
version info

Test::Unit::Procedural Perl module contains a procedural style unit testing interface.

SYNOPSIS

use Test::Unit::Procedural;

# your code to be tested goes here

sub foo { return 23 };
sub bar { return 42 };

# define tests

sub test_foo { assert(foo() == 23, "Your message here"); }
sub test_bar { assert(bar() == 42, "I will be printed if this fails"); }

# set_up and tear_down are used to
# prepare and release resources need for testing

sub set_up { print "hello worldn"; }
sub tear_down { print "leaving world againn"; }

# run your test

create_suite();
run_suite();

Test::Unit::Procedural is the procedural style interface to a sophisticated unit testing framework for Perl that is derived from the JUnit testing framework for Java by Kent Beck and Erich Gamma. While this framework is originally intended to support unit testing in an object-oriented development paradigm (with support for inheritance of tests etc.), Test::Unit::Procedural is intended to provide a simpler interface to the framework that is more suitable for use in a scripting style environment. Therefore, Test::Unit::Procedural does not provide much support for an object-oriented approach to unit testing - if you want that, please have a look at Test::Unit::TestCase.

You test a given unit (a script, a module, whatever) by using Test::Unit::Procedural, which exports the following routines into your namespace:

assert()

used to assert that a boolean condition is true

create_suite()

used to create a test suite consisting of all methods with a name prefix of test

run_suite()

runs the test suite (text output)

add_suite()

used to add test suites to each other

For convenience, create_suite() will automatically build a test suite for a given package. This will build a test case for each subroutine in the package given that has a name starting with test and pack them all together into one TestSuite object for easy testing. If you dont give a package name to create_suite(), the current package is taken as default.

Test output is one status line (a "." for every successful test run, or an "F" for any failed test run, to indicate progress), one result line ("OK" or "!!!FAILURES!!!"), and possibly many lines reporting detailed error messages for any failed tests.
Please remember, Test::Unit::Procedural is intended to be a simple and convenient interface. If you need more functionality, take the object-oriented approach outlined in Test::Unit::TestCase.

Test::Unit::Tutorial is a Perl module that contains a tutorial on unit testing.

SYNOPSIS

perldoc Test::Unit::Tutorial

Here should be extensive documentation on what unit testing is, why it is useful, and how to do it with the Test::Unit collection of modules.

Sorry for not implementing this yet.

Please have a look at the examples in the examples directory and read the README file that came with this distribution.

A short tutorial on how to use the unit testing framework is included in Test::Unit::TestCase.

Further examples can be found by looking at the self test collection, starting in Test::Unit::tests::AllTests.

Test::Unit::TestSuite is a unit testing framework base class.

SYNOPSIS

use Test::Unit::TestSuite;

# more code here ...

sub suite {
my $class = shift;

# create an empty suite
my $suite = Test::Unit::TestSuite->empty_new("A Test Suite");

# get and add an existing suite
$suite->add_test(Test::Unit::TestSuite->new("MyModule::Suite_1"));

# extract suite by way of suite method and add
$suite->add_test(MyModule::Suite_2->suite());

# get and add another existing suite
$suite->add_test(Test::Unit::TestSuite->new("MyModule::TestCase_2"));

# return the suite built
return $suite;
}

This class is normally not used directly, but it can be used for creating your own custom built aggregate suites.

Normally, this class just provides the functionality of auto-building a test suite by extracting methods with a name prefix of test from a given package to the test runners.

linSmith project is a Smith Charting program, mainly designed for educational use.
linSmith is a Smith Charting program, mainly designed for educational use. As such, there is an emphasis on capabilities that improve the showing the effect of-style of operation.
Main features:
- Definition of multiple load impedances (at different frequencies)
- Addition of discrete (L, C, series and parallel LC, and transformer) and line components (open and closed stubs, and line segments)
- Connection in series and parallel
- Easy experimenting with component values using scrollbars
- A virtual component switches from impedance to admittance to help explaining (or understanding) parallel components
- The chart works in real impedances (not normalized ones)
- Direct view of the result on the screen
- Ability to generate publication quality Postscript output
- A log file with textual results at each intermediate step
- Load and circuit configuration is stored separately, permitting several solutions without re-defining the other.