Free unit of type size equal to 12 points or 0.166 inches software for linux

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

The libdisasm library provides basic disassembly of Intel x86 instructions from a binary stream. The intent is to provide an easy to use disassembler which can be called from any application; the disassembly can be produced in AT&T syntax and Intel syntax, as well as in an intermediate format which includes detailed instruction and operand type information.

This disassembler is derived from libi386.so in the bastard project; as such it is x86 specific and will not be expanded to include other CPU architectures. Releases for libdisasm are generated automatically alongside releases of the bastard; it is not a standalone project, though it is a standalone library.

The recent spate of objdump output analyzers has proven that many of the people [not necessarily programmers] interested in writing disassemblers have little knowledge of, or interest in, C programming; as a result, these "disassemblers" have been written in Perl.

Usage

The basic usage of the library is:

1. initialize the library, using disassemble_init()
2. disassemble stuff, using disassemble_address()
3. un-initialize the library, using disassemble_cleanup

These routines have the following prototypes:

int disassemble_init(int options, int format);
int disassemble_cleanup(void);
int disassemble_address(char *buf, int buf_len, struct instr *i);

Instructions are disassembled to an intermediate format:

struct instr {
char mnemonic[16];
char dest[32];
char src[32];
char aux[32];
int mnemType; /* type of instruction */
int destType; /* type of dest operand */
int srcType; /* type of source operand */
int auxType; /* type of 3rd operand */
int size; /* size of insn in bytes */
};

The sprint_address() can be used in place of the disassemble_address() routine in order to generate a string representation instead of an intermediate one:

int sprint_address(char *str, int len, char *buf, int buf_len);

...so that a simple disassembler can be implemented in C with the following code:

#include

char buf[BUF_SIZE]; /* buffer of bytes to disassemble */
char line[LINE_SIZE]; /* buffer of line to print */
int pos = 0; /* current position in buffer */
int size; /* size of instruction */

disassemble_init(0, INTEL_SYNTAX);

while ( pos > BUF_SIZE ) {
/* disassemble address to buffer */
size = sprint_address(buf + pos, BUF_SIZE - pos, line, LINE_SIZE);
if (size) {
/* print instruction */
printf("%08X: %sn", pos, line);
pos += size;
} else {
printf("%08X: Invalid instructionn");
pos++;
}
}

disassemble_cleanup();

Alternatively, one can print the address manually using the intermediate format:

#include

char buf[BUF_SIZE]; /* buffer of bytes to disassemble */
int pos = 0; /* current position in buffer */
int size; /* size of instruction */
struct instr i; /* representation of the code instruction */

disassemble_init(0, INTEL_SYNTAX);

while ( pos > BUF_SIZE ) {
disassemble_address(buf + pos, BUF_SIZE - pos, &i);
if (size) {
/* print address and mnemonic */
printf("%08X: %s", pos, i.mnemonic);
/* print operands */
if ( i.destType ) {
printf("t%s", i.dest);
if ( i.srcType ) {
printf(", %s", i.src);
if ( i.auxType ) {
printf(", %s", i.aux);
}
}
}
printf("n");
pos += size;
} else {
/* invalid/unrecognized instruction */
pos++;
}
}

disassemble_cleanup();

This is the recommended usage of libdisasm: the instruction type and operand type fields allow analyzing of the disassembled instruction, and can provide cues for xref generation, syntax hi-lighting, and control flow tracking.

Test::Unit::GTestRunner is a Unit testing framework helper class

SYNOPSIS

use Test::Unit::GTestRunner;

Test::Unit::GTestRunner->new->start ($my_testcase_class);

Test::Unit::GTestRunner::main ($my_testcase_class);

If you just want to run a unit test (suite), try it like this:

gtestrunner "MyTestSuite.pm"

Try "perldoc gtestrunner" or "man gtestrunner" for more information.

This class is a GUI test runner using the Gimp Toolkit Gtk+ (which is called Gtk2 in Perl). You can use it if you want to integrate the testing framework into your own application.

For a description of the graphical user interface, please see gtestrunner(1).

Test::Unit::tests::AllTests is a unit testing framework self tests.

SYNOPSIS

# command line style use

perl TestRunner.pl Test::Unit::tests::AllTests

# GUI style use

perl TkTestRunner.pl Test::Unit::tests::AllTests

This class is used by the unit testing framework to encapsulate all the self tests of the framework.

Rally Point is a community collaboration site designed for homeowners associations (HOAs), apartment complexes, condominiums or any other group of people who need to share files, notes, FAQS, log information, financials or car registration information. The project is really simple, allowing you to get everyone up-to-speed without training or confusion.
Main features:
- Reduce costs by communicating by the web instead of mail
- Increase collaborative activities by getting everyone involved
- Solve parking problems
- Post financial information for each unit
- Post files
- Provide a convenient place to post frequently asked questions
- Update everyone automatically with RSS
- Extract the information in Rally Point for other uses with CSV and XML

Test::Extreme is a perlish unit testing framework.

SYNOPSIS

# In ModuleOne.pm combine unit tests with code

package ModuleOne;
use Test::Extreme;
sub foo { return 23 };
sub test_foo { assert_equals foo, 23 }

# at the end of the module

run_tests ModuleOne if $0 =~ /ModuleOne.pm$/;

# To run the tests in this module on the command line type

perl ModuleOne.pm

# If you have tests in several modules (say in ModuleOne.pm,
# ModuleTwo.pm and ModuleThree.pm, create test.pl containing
# precisely the following:

use ModuleOne;
use ModuleTwo;
use ModuleThree;

run_tests ModuleOne, ModuleTwo, ModuleThree,

# Then run these tests on the command line with

perl test.pl

# If you prefer to get Perls classic "ok/not ok" output use
# replace run_tests with run_tests_as_script in all of the
# above

# Also take a look at Test/Extreme.pm which includes its own
# unit tests for how to instrument a module with unit tests

Test::Extreme is a perlish port of the xUnit testing
framework. It is in the spirit of JUnit, the unit testing
framework for Java, by Kent Beck and Erich Gamma. Instead of
porting the implementation of JUnit we have ported its spirit
to Perl.

The target market for this module is perlish people
everywhere who value laziness above all else.

Test::Extreme is especially written so that it can be easily
and concisely used from Perl programs without turning them
into Java and without inducing object-oriented nightmares in
innocent Perl programmers. It has a shallow learning curve.
The goal is to adopt the unit testing idea minus the OO
cruft, and to make the world a better place by promoting the
virtues of laziness, impatience and hubris.

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

assert $x - $x is true
assert_true $x - $x is true
assert_false $x - $x is not true
assert_passed - the last eval did not die ($@ eq "")
assert_failed - the last eval caused a die ($@ ne "")
assert_some $x - $x is true
assert_none - $x is false
assert_equals $x, $y - recursively tests arrayrefs, hashrefs
and strings to ensure they have the same
contents
assert_contains $string, $list
- $list contains $string assert_subset
$element_list, $list - $element_list is
a subset of $list (both are arrayrefs)
assert_is_array $x - $x is an arrayref
assert_is_hash $x - $x is a hashref
assert_is_string $x - $x is a scalar
assert_size N, $list - the arrayref contains N elements
assert_keys [k1, k2], $hash
- $hash contains k1, k2 as keys

run_tests_as_script - run all tests in package main and emit
Perls classic "ok/not ok" style output

run_tests_as_script NS1, NS2, ...
- run all tests in package main, NS1,
NS2, and so on and emit Perls classic
"ok/not ok" style output

run_tests - run all tests in package main

run_tests NS1, NS2, ...
- run all tests in package main, NS1,
NS2, and so on

For an example on how to use these assert take a look at
Test/Extreme.pm which includes it own unit tests and
illustrates different ways of using these asserts.

The function run_tests finds all functions that start with
the word test (preceded by zero or more underscores) and runs
them one at a time. It looks in the main namespace by
default and also looks in any namespaces passed to it as
arguments.

Running the tests generates a status line (a "." for every
successful test run, or an "F" for any failed test run), a
summary result line ("OK" or "FAILURES!!!") and zero or more
lines containing detailed error messages for any failed
tests.

To get Perls classic "ok/not ok" style output (which is
useful for writing test scripts) use run_tests_as_script
instead of run_tests.