to test
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 2845
Otk Tests 1.0
Otk Tests are tests for the Open Tool Kit project. more>>
Otk Tests are tests for the Open Tool Kit project.
Otk is a portable widget library for making graphical user interfaces for C programs. It emphasizes simplicity for the application programmer without eliminating capability. Based on OpenGL, Otk supports Linux, Unix, and other OSs neutrally and efficiently. It is simple and compact, and it strives for easy compilation and linking to other applications.
In seeking to address several issues associated with earlier graphics APIs, Otk explores some interesting methods, such as window-relative layout instead of pixel-based layout.
Enhancements:
- This package of Otk test programs includes scripts to automatically compile and invoke them sequentially.
- The scripts enable quickly testing OTK_LIB functionality.
- The package will be handy for continued regression testing whenever otk_lib is changed or updated.
- It checks that OTK and applications compile will on various platforms, and exercises most features to test for proper operations.
<<lessOtk is a portable widget library for making graphical user interfaces for C programs. It emphasizes simplicity for the application programmer without eliminating capability. Based on OpenGL, Otk supports Linux, Unix, and other OSs neutrally and efficiently. It is simple and compact, and it strives for easy compilation and linking to other applications.
In seeking to address several issues associated with earlier graphics APIs, Otk explores some interesting methods, such as window-relative layout instead of pixel-based layout.
Enhancements:
- This package of Otk test programs includes scripts to automatically compile and invoke them sequentially.
- The scripts enable quickly testing OTK_LIB functionality.
- The package will be handy for continued regression testing whenever otk_lib is changed or updated.
- It checks that OTK and applications compile will on various platforms, and exercises most features to test for proper operations.
Download (0.006MB)
Added: 2006-03-27 License: LGPL (GNU Lesser General Public License) Price:
1306 downloads
TinyMe 2007 Test 5
TinyMe project exists to create a remaster of PCLinuxOS 2007 that will be quite slimmed down. more>>
TinyMe project exists to create a remaster of PCLinuxOS 2007 that will be quite slimmed down. The target is to get a functioning ~150MB ISO image that can provide a base installation for other MyPCLinuxOS projects, development, playing around, installation to old computers, where a minimal installation is all thats needed, and any other situations where a tiny Linux installation is required or desirable.
We want to create something that can compete with distros like Puppy, DSL, Feather, NimbleX, and PUD for speed and size while maintaining a similar level of functionality through the GUI.
Username/Password:
tiny/tiny
root/root
Enhancements:
- Fixed most open bugs. Only remaining major open bug (in my opinion) is that TinyMe still doesnt auto mount removable media.
- I switched to GDM. This allows us greater flexibility with our login manager. Also, it enables Shutdown and Reboot options on logout.
- AbiWord was installed, with all the plugins your heart desires. Create and edit ODT, DOC, WPD, and many other formats.
- Idesk now handles the desktop instead of PCManFM.
- Enabeled LXPanel transparency.
- Added Grafburn for burning CDs and DVDs. Thanks to Nathan Fisher of Grafpup for Grafburn.
- Created Welcome page. Fire up Opera to see it. (Did I mention Opera handles web browsing, mail, Bittorrent, and IRC chat?)
- Conky is a SuperKaramba-like desktop monitoring applet which has been added. GKrellm was fired. :-)
- Do you like music? Audacious was added. Audacious is a lot like WinAmp and you can use WinAmp themes on it.
- MEdit proved to be somewhat buggy. Although I rather liked it, I opted to use SciTE instead. Enjoy.
- Changed Mrxvt to the default terminal. Mrxvt is a tabbed terminal, plus it has some pretty cool transparency.
- Galculator is a quite small calculator added to test 5.
- Xarchiver has been added for its wonderous abilities to open just about any compressed archive, including RPMs and ISOs.
- MtPaint was added. MtPaint is a very basic picture editor. You can also use MtPaint to take a screenshot.
- XKill has been added and a menu entry created for those balky programs which hang on you.
- Tweaked overall look n feel some more. Added 2 wallpapers (okay, its 1 wallpaper; 1 is 4:3, the other 16:10)
<<lessWe want to create something that can compete with distros like Puppy, DSL, Feather, NimbleX, and PUD for speed and size while maintaining a similar level of functionality through the GUI.
Username/Password:
tiny/tiny
root/root
Enhancements:
- Fixed most open bugs. Only remaining major open bug (in my opinion) is that TinyMe still doesnt auto mount removable media.
- I switched to GDM. This allows us greater flexibility with our login manager. Also, it enables Shutdown and Reboot options on logout.
- AbiWord was installed, with all the plugins your heart desires. Create and edit ODT, DOC, WPD, and many other formats.
- Idesk now handles the desktop instead of PCManFM.
- Enabeled LXPanel transparency.
- Added Grafburn for burning CDs and DVDs. Thanks to Nathan Fisher of Grafpup for Grafburn.
- Created Welcome page. Fire up Opera to see it. (Did I mention Opera handles web browsing, mail, Bittorrent, and IRC chat?)
- Conky is a SuperKaramba-like desktop monitoring applet which has been added. GKrellm was fired. :-)
- Do you like music? Audacious was added. Audacious is a lot like WinAmp and you can use WinAmp themes on it.
- MEdit proved to be somewhat buggy. Although I rather liked it, I opted to use SciTE instead. Enjoy.
- Changed Mrxvt to the default terminal. Mrxvt is a tabbed terminal, plus it has some pretty cool transparency.
- Galculator is a quite small calculator added to test 5.
- Xarchiver has been added for its wonderous abilities to open just about any compressed archive, including RPMs and ISOs.
- MtPaint was added. MtPaint is a very basic picture editor. You can also use MtPaint to take a screenshot.
- XKill has been added and a menu entry created for those balky programs which hang on you.
- Tweaked overall look n feel some more. Added 2 wallpapers (okay, its 1 wallpaper; 1 is 4:3, the other 16:10)
Download (195.1MB)
Added: 2007-08-09 License: GPL (GNU General Public License) Price:
808 downloads
Test soon 0.59
Test soon project is a testing framework trying to enable you to write tests quickly. more>>
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.
<<lessThe goal is to utilize the strengths of C++ while minimizing the impact of its weaknesses.
Download (MB)
Added: 2007-07-01 License: zlib/libpng License Price:
846 downloads
Test::Cmd 1.05
Test::Cmd is a Perl module for portable testing of commands and scripts. more>>
Test::Cmd is a Perl module for portable testing of commands and scripts.
SYNOPSIS
use Test::Cmd;
$test = Test::Cmd->new(prog => program_or_script_to_test,
interpreter => script_interpreter,
string => identifier_string,
workdir => ,
subdir => dir,
match_sub => $code_ref,
verbose => 1);
$test->verbose(1);
$test->prog(program_or_script_to_test);
$test->basename(@suffixlist);
$test->interpreter(script_interpreter);
$test->string(identifier string);
$test->workdir(prefix);
$test->workpath(subdir, file);
$test->subdir(subdir, ...);
$test->subdir([sub, dir], ...);
$test->write(file, read($contents, [subdir, file]);
$test->read(@lines, [subdir, file]);
$test->writable(dir);
$test->writable(dir, $rwflag);
$test->writable(dir, $rwflag, %errors);
$test->preserve(condition, ...);
$test->cleanup(condition);
$test->run(prog => program_or_script_to_test,
interpreter => script_interpreter,
chdir => dir, args => arguments, stdin => pass(condition, &func);
$test->fail(condition);
$test->fail(condition, &func);
$test->fail(condition, &func, $caller);
$test->no_result(condition);
$test->no_result(condition, &func);
$test->no_result(condition, &func, $caller);
$test->stdout;
$test->stdout($run_number);
$test->stderr;
$test->stderr($run_number);
$test->match(@lines, @matches);
$test->match($lines, $matches);
$test->match_exact(@lines, @matches);
$test->match_exact($lines, $matches);
$test->match_regex(@lines, @regexes);
$test->match_regex($lines, $regexes);
$test->diff_exact(@lines, @matches, @output);
$test->diff_exact($lines, $matches, @output);
$test->diff_regex(@lines, @regexes, @output);
$test->diff_regex($lines, $regexes, @output);
sub func {
my ($self, $lines, $matches) = @_;
# code to match $lines and $matches
}
$test->match_sub(&func);
$test->match_sub(sub { code to match $_[1] and $_[2] });
$test->here;
The Test::Cmd module provides a low-level framework for portable automated testing of executable commands and scripts (in any language, not just Perl), especially commands and scripts that interact with the file system.
The Test::Cmd module makes no assumptions about what constitutes a successful or failed test. Attempting to read a file that doesnt exist, for example, may or may not be an error, depending on the software being tested.
Consequently, no Test::Cmd methods (including the new() method) exit, die or throw any other sorts of exceptions (but they all do return useful error indications). Exceptions or other error status should be handled by a higher layer: a subclass of Test::Cmd, or another testing framework such as the Test or Test::Simple Perl modules, or by the test itself.
(That said, see the Test::Cmd::Common module if you want a similar module that provides exception handling, either to use directly in your own tests, or as an example of how to use Test::Cmd.)
In addition to running tests and evaluating conditions, the Test::Cmd module manages and cleans up one or more temporary workspace directories, and provides methods for creating files and directories in those workspace directories from in-line data (that is, here-documents), allowing tests to be completely self-contained. When used in conjunction with another testing framework, the Test::Cmd module can function as a fixture (common startup code for multiple tests) for simple management of command execution and temporary workspaces.
The Test::Cmd module inherits File::Spec methods (file_name_is_absolute(), catfile(), etc.) to support writing tests portably across a variety of operating and file systems.
A Test::Cmd environment object is created via the usual invocation:
$test = Test::Cmd->new();
Arguments to the Test::Cmd::new method are keyword-value pairs that may be used to initialize the object, typically by invoking the same-named method as the keyword.
<<lessSYNOPSIS
use Test::Cmd;
$test = Test::Cmd->new(prog => program_or_script_to_test,
interpreter => script_interpreter,
string => identifier_string,
workdir => ,
subdir => dir,
match_sub => $code_ref,
verbose => 1);
$test->verbose(1);
$test->prog(program_or_script_to_test);
$test->basename(@suffixlist);
$test->interpreter(script_interpreter);
$test->string(identifier string);
$test->workdir(prefix);
$test->workpath(subdir, file);
$test->subdir(subdir, ...);
$test->subdir([sub, dir], ...);
$test->write(file, read($contents, [subdir, file]);
$test->read(@lines, [subdir, file]);
$test->writable(dir);
$test->writable(dir, $rwflag);
$test->writable(dir, $rwflag, %errors);
$test->preserve(condition, ...);
$test->cleanup(condition);
$test->run(prog => program_or_script_to_test,
interpreter => script_interpreter,
chdir => dir, args => arguments, stdin => pass(condition, &func);
$test->fail(condition);
$test->fail(condition, &func);
$test->fail(condition, &func, $caller);
$test->no_result(condition);
$test->no_result(condition, &func);
$test->no_result(condition, &func, $caller);
$test->stdout;
$test->stdout($run_number);
$test->stderr;
$test->stderr($run_number);
$test->match(@lines, @matches);
$test->match($lines, $matches);
$test->match_exact(@lines, @matches);
$test->match_exact($lines, $matches);
$test->match_regex(@lines, @regexes);
$test->match_regex($lines, $regexes);
$test->diff_exact(@lines, @matches, @output);
$test->diff_exact($lines, $matches, @output);
$test->diff_regex(@lines, @regexes, @output);
$test->diff_regex($lines, $regexes, @output);
sub func {
my ($self, $lines, $matches) = @_;
# code to match $lines and $matches
}
$test->match_sub(&func);
$test->match_sub(sub { code to match $_[1] and $_[2] });
$test->here;
The Test::Cmd module provides a low-level framework for portable automated testing of executable commands and scripts (in any language, not just Perl), especially commands and scripts that interact with the file system.
The Test::Cmd module makes no assumptions about what constitutes a successful or failed test. Attempting to read a file that doesnt exist, for example, may or may not be an error, depending on the software being tested.
Consequently, no Test::Cmd methods (including the new() method) exit, die or throw any other sorts of exceptions (but they all do return useful error indications). Exceptions or other error status should be handled by a higher layer: a subclass of Test::Cmd, or another testing framework such as the Test or Test::Simple Perl modules, or by the test itself.
(That said, see the Test::Cmd::Common module if you want a similar module that provides exception handling, either to use directly in your own tests, or as an example of how to use Test::Cmd.)
In addition to running tests and evaluating conditions, the Test::Cmd module manages and cleans up one or more temporary workspace directories, and provides methods for creating files and directories in those workspace directories from in-line data (that is, here-documents), allowing tests to be completely self-contained. When used in conjunction with another testing framework, the Test::Cmd module can function as a fixture (common startup code for multiple tests) for simple management of command execution and temporary workspaces.
The Test::Cmd module inherits File::Spec methods (file_name_is_absolute(), catfile(), etc.) to support writing tests portably across a variety of operating and file systems.
A Test::Cmd environment object is created via the usual invocation:
$test = Test::Cmd->new();
Arguments to the Test::Cmd::new method are keyword-value pairs that may be used to initialize the object, typically by invoking the same-named method as the keyword.
Download (0.030MB)
Added: 2007-02-23 License: Perl Artistic License Price:
978 downloads
Test::Data 1.20
Test::Data is a Perl module to test functions for particular variable types. more>>
Test::Data is a Perl module to test functions for particular variable types.
SYNOPSIS
use Test::Data qw(Scalar Array Hash Function);
Test::Data provides utility functions to check properties and values of data and variables.
Functions
Plug-in modules define functions for each data type. See the appropriate module.
How it works
The Test::Data module simply emports functions from Test::Data::* modules. Each module defines a self-contained function, and puts that function name into @EXPORT. Test::Data defines its own import function, but that does not matter to the plug-in modules.
If you want to write a plug-in module, follow the example of one that already exists. Name the module Test::Data::Foo, where you replace Foo with the right name. Test::Data should automatically find it.
<<lessSYNOPSIS
use Test::Data qw(Scalar Array Hash Function);
Test::Data provides utility functions to check properties and values of data and variables.
Functions
Plug-in modules define functions for each data type. See the appropriate module.
How it works
The Test::Data module simply emports functions from Test::Data::* modules. Each module defines a self-contained function, and puts that function name into @EXPORT. Test::Data defines its own import function, but that does not matter to the plug-in modules.
If you want to write a plug-in module, follow the example of one that already exists. Name the module Test::Data::Foo, where you replace Foo with the right name. Test::Data should automatically find it.
Download (0.008MB)
Added: 2007-05-03 License: Perl Artistic License Price:
904 downloads
Test::Glade 1.0
Test::Glade is a simple way to test Gtk2::GladeXML-based apps. more>>
Test::Glade is a simple way to test Gtk2::GladeXML-based apps.
SYNOPSIS
use Test::Glade tests => 2;
my $glade_xml = interface.glade;
has_widget( $glade_xml, {
name => main_window,
type => GtkWindow,
properties => {
title => Test Application,
type => GTK_WINDOW_TOPLEVEL,
resizable => 1,
},
} );
has_widget( $glade_xml, {
type => GtkButton,
properties => {label => Press me!},
signals => {clicked => button_pressed_handler},
} );
GUIs are notoriously difficult to test. Historically this was well deserved as the available perl GUI toolkits did not encourage separation of the view and controller layers. The introduction of the Glade GUI designer and Gtk2::GladeXML changed that by segregating user interface and logical components (into GladeXML and Perl files respectively).
Users who avoid creating GUI elements from within their application logic can now test each layer separately with appropriate tools. The Perl logic can be verified with standard unit tests and this module provides a way to inspect and verify the GladeXML UI specification. You can confirm that a given widget exists, that it has the correct label and other attributes, that it will be correctly placed in the interface and that it will respond to signals as expected.
<<lessSYNOPSIS
use Test::Glade tests => 2;
my $glade_xml = interface.glade;
has_widget( $glade_xml, {
name => main_window,
type => GtkWindow,
properties => {
title => Test Application,
type => GTK_WINDOW_TOPLEVEL,
resizable => 1,
},
} );
has_widget( $glade_xml, {
type => GtkButton,
properties => {label => Press me!},
signals => {clicked => button_pressed_handler},
} );
GUIs are notoriously difficult to test. Historically this was well deserved as the available perl GUI toolkits did not encourage separation of the view and controller layers. The introduction of the Glade GUI designer and Gtk2::GladeXML changed that by segregating user interface and logical components (into GladeXML and Perl files respectively).
Users who avoid creating GUI elements from within their application logic can now test each layer separately with appropriate tools. The Perl logic can be verified with standard unit tests and this module provides a way to inspect and verify the GladeXML UI specification. You can confirm that a given widget exists, that it has the correct label and other attributes, that it will be correctly placed in the interface and that it will respond to signals as expected.
Download (0.005MB)
Added: 2007-05-04 License: Perl Artistic License Price:
903 downloads
Test-Parser 1.2
Test::Parser is a collection of parsers for different test output file formats. more>>
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.
<<lessTest-Parser can also export tests in SpikeSources TRPI test description XML language.
Download (0.053MB)
Added: 2006-05-04 License: GPL (GNU General Public License) Price:
1268 downloads
Test-Run 0.0110
Test-Run is an improved test harness for scripts that emit TAP (Test Anything Protocol). more>>
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.
<<lessThe 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.
Download (0.067MB)
Added: 2007-06-12 License: MIT/X Consortium License Price:
865 downloads
Test::Lazy 0.01
Test::Lazy is a quick and easy way to compose and run tests with useful output. more>>
Test::Lazy is a quick and easy way to compose and run tests with useful output.
SYNOPSIS
use Test::Lazy qw/check try/;
check(1 => is => 1);
check(0 => isnt => 1);
check(a => like => qr/[a-zA-Z]/);
check(0 => unlike => qr/a-zA-Z]/);
check(1 => > => 0);
check(0 => < => 1);
try(qw/a/ => eq => a);
try(qw/a/ => ne => b);
try(qw/a/ => is => [a]);
try( < stmt >, < cmpr >, < expected >, [ < msg > ] )
Evaluate < stmt> and compare the result to using < cmpr>. Optionally provide a < msg> to display on failure. If < msg> is not given, then one will be automatically made from < stmt>, < cmpr>, and < expected>.
try will also try to guess what representation is best for the result of the statement, whether that be single value, ARRAY, or HASH. Itll do this based on what is returned by the statement, and the type of < expected>. See `perldoc -m Test::Lazy` for more detail.
Note, if < expected> is an ARRAY or HASH, this function will convert it to its JSON representation before comparison.
try("2 + 2" => == => 5);
# This will produce the following output:
# Failed test 2 + 2 == 5
# at __FILE__ line __LINE__.
# got: 4
# expected: 5
check( < got>, < cmpr>, < expected>, [ < msg> ] )
Compare < got> to < expected> using < cmpr>. Optionally provide a < msg> to display on failure. If < msg> is not given, then one will be automatically made from < got>, < cmpr>, and < expected>.
Note, if < got> or < expected> is an ARRAY or HASH, this function will convert them to their JSON representation before comparison.
check([qw/a b/] => is => [qw/a b c/]);
# This will produce the following output:
# Failed test ["a","b"] is ["a","b","c"]
# at __FILE__ line __LINE__.
# got: ["a","b"]
# expected: ["a","b","c"]
template( ... )
Convenience function for creating a Test::Lazy::Template. All arguments are directly passed to Test::Lazy::Template-new>.
See Test::Lazy::Template for more details.
Returns a new Test::Lazy::Template object.
cmpr
< cmpr> can be one of the following:
ok, not_ok, is, isnt, like, unlike,
, =, lt, gt, le, ge, ==, !=, eq, ne,
<<lessSYNOPSIS
use Test::Lazy qw/check try/;
check(1 => is => 1);
check(0 => isnt => 1);
check(a => like => qr/[a-zA-Z]/);
check(0 => unlike => qr/a-zA-Z]/);
check(1 => > => 0);
check(0 => < => 1);
try(qw/a/ => eq => a);
try(qw/a/ => ne => b);
try(qw/a/ => is => [a]);
try( < stmt >, < cmpr >, < expected >, [ < msg > ] )
Evaluate < stmt> and compare the result to using < cmpr>. Optionally provide a < msg> to display on failure. If < msg> is not given, then one will be automatically made from < stmt>, < cmpr>, and < expected>.
try will also try to guess what representation is best for the result of the statement, whether that be single value, ARRAY, or HASH. Itll do this based on what is returned by the statement, and the type of < expected>. See `perldoc -m Test::Lazy` for more detail.
Note, if < expected> is an ARRAY or HASH, this function will convert it to its JSON representation before comparison.
try("2 + 2" => == => 5);
# This will produce the following output:
# Failed test 2 + 2 == 5
# at __FILE__ line __LINE__.
# got: 4
# expected: 5
check( < got>, < cmpr>, < expected>, [ < msg> ] )
Compare < got> to < expected> using < cmpr>. Optionally provide a < msg> to display on failure. If < msg> is not given, then one will be automatically made from < got>, < cmpr>, and < expected>.
Note, if < got> or < expected> is an ARRAY or HASH, this function will convert them to their JSON representation before comparison.
check([qw/a b/] => is => [qw/a b c/]);
# This will produce the following output:
# Failed test ["a","b"] is ["a","b","c"]
# at __FILE__ line __LINE__.
# got: ["a","b"]
# expected: ["a","b","c"]
template( ... )
Convenience function for creating a Test::Lazy::Template. All arguments are directly passed to Test::Lazy::Template-new>.
See Test::Lazy::Template for more details.
Returns a new Test::Lazy::Template object.
cmpr
< cmpr> can be one of the following:
ok, not_ok, is, isnt, like, unlike,
, =, lt, gt, le, ge, ==, !=, eq, ne,
Download (0.006MB)
Added: 2007-07-18 License: Perl Artistic License Price:
828 downloads
Test::ISBN 1.09
Test::ISBN is a Perl module to check international standard book numbers. more>>
Test::ISBN is a Perl module to check international standard book numbers.
SYNOPSIS
use Test::More tests => 1;
use Test::ISBN;
isbn_ok( $isbn );
Functions
isbn_ok( STRING )
Ok is the STRING is a valid ISBN, in any format that Business::ISBN accepts. This function only checks the checksum. The publisher and country codes might be invalid even though the checksum is valid.
isbn_country_ok( STRING, COUNTRY )
Ok is the STRING is a valid ISBN and its country code is the same as COUNTRY.
isbn_publisher_ok( STRING, PUBLISHER )
Ok is the STRING is a valid ISBN and its publisher code is the same as PUBLISHER.
<<lessSYNOPSIS
use Test::More tests => 1;
use Test::ISBN;
isbn_ok( $isbn );
Functions
isbn_ok( STRING )
Ok is the STRING is a valid ISBN, in any format that Business::ISBN accepts. This function only checks the checksum. The publisher and country codes might be invalid even though the checksum is valid.
isbn_country_ok( STRING, COUNTRY )
Ok is the STRING is a valid ISBN and its country code is the same as COUNTRY.
isbn_publisher_ok( STRING, PUBLISHER )
Ok is the STRING is a valid ISBN and its publisher code is the same as PUBLISHER.
Download (0.004MB)
Added: 2007-05-04 License: Perl Artistic License Price:
903 downloads
OpenGuides::Test 0.57
OpenGuides::Test are methods to help test OpenGuides applications. more>>
OpenGuides::Test are methods to help test OpenGuides applications.
Provides methods to help when writing tests for OpenGuides. Distributed and installed as part of the OpenGuides project, not intended for independent installation. This documentation is probably only useful to OpenGuides developers.
SYNOPSIS
use OpenGuides;
use OpenGuides::Test;
my $config = OpenGuides::Test->make_basic_config;
$config->default_language( "nl" );
my $guide = OpenGuides->new( config => $config );
OpenGuides::Test->write_data(
guide => $guide,
node => "Crabtree Tavern",
os_x => 523465,
os_y => 177490,
categories => "Pubs",
);
<<lessProvides methods to help when writing tests for OpenGuides. Distributed and installed as part of the OpenGuides project, not intended for independent installation. This documentation is probably only useful to OpenGuides developers.
SYNOPSIS
use OpenGuides;
use OpenGuides::Test;
my $config = OpenGuides::Test->make_basic_config;
$config->default_language( "nl" );
my $guide = OpenGuides->new( config => $config );
OpenGuides::Test->write_data(
guide => $guide,
node => "Crabtree Tavern",
os_x => 523465,
os_y => 177490,
categories => "Pubs",
);
Download (0.11MB)
Added: 2006-10-31 License: Perl Artistic License Price:
1088 downloads
Test::Unit 0.25
Test::Unit is the main PerlUnit testing framework. more>>
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.
<<lessSYNOPSIS
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.
Download (0.31MB)
Added: 2007-05-07 License: Perl Artistic License Price:
900 downloads
Test::Usage 0.07
Test::Usage is a different approach to testing: selective, quieter, colorful. more>>
Test::Usage is a different approach to testing: selective, quieter, colorful.
SYNOPSIS
Lets say we are building module Foo.pm. To exercise it, we write a usage examples module, Foo_T.pm, which may eventually look something like this:
package Foo_T;
use Test::Usage;
use strict;
use warnings;
use Foo;
example(e1, sub { ... ok(...); ... die "Uh oh"; ... });
example(a1, sub { ... ok(...) or diag(...); ... });
example(a2, sub { ... ok(...); ... });
example(a3, sub {
my $f = Foo->new();
my $got_foo = $f->foo();
my $exp_foo = FOO;
ok(
$got_foo eq $exp_foo,
"Expecting foo() to return $exp_foo.",
"But got $got_foo."
);
});
Here are a few ways to test its examples:
# Run example a3 only.
perl -MFoo_T -e test(a => "a3")
# Run all examples whose label matches glob a*: a1, a2, a3.
perl -MFoo_T -e test(a => "a*")
# Run all examples found in the test module.
perl -MFoo_T -e test
# Run example a3, reporting successes also, but without color.
perl -MFoo_T -e test(a => "a3", v => 2, c => 0)
# Run and summarize all examples in all "*_T.pm" files found under
# current directory.
perl -MTest::Usage -e files
<<lessSYNOPSIS
Lets say we are building module Foo.pm. To exercise it, we write a usage examples module, Foo_T.pm, which may eventually look something like this:
package Foo_T;
use Test::Usage;
use strict;
use warnings;
use Foo;
example(e1, sub { ... ok(...); ... die "Uh oh"; ... });
example(a1, sub { ... ok(...) or diag(...); ... });
example(a2, sub { ... ok(...); ... });
example(a3, sub {
my $f = Foo->new();
my $got_foo = $f->foo();
my $exp_foo = FOO;
ok(
$got_foo eq $exp_foo,
"Expecting foo() to return $exp_foo.",
"But got $got_foo."
);
});
Here are a few ways to test its examples:
# Run example a3 only.
perl -MFoo_T -e test(a => "a3")
# Run all examples whose label matches glob a*: a1, a2, a3.
perl -MFoo_T -e test(a => "a*")
# Run all examples found in the test module.
perl -MFoo_T -e test
# Run example a3, reporting successes also, but without color.
perl -MFoo_T -e test(a => "a3", v => 2, c => 0)
# Run and summarize all examples in all "*_T.pm" files found under
# current directory.
perl -MTest::Usage -e files
Download (0.016MB)
Added: 2006-10-24 License: Perl Artistic License Price:
1096 downloads
TAHI Test Suite 1.4.8 (Self-Test Test Suite)
TAHI Test Suite provides a mechanism for validating an IPv6 implementation. more>>
TAHI Test Suite provides a mechanism for validating an IPv6 implementation against a standardized test for conformance to the IPv6 specification, extensions and directly related protocols.
TAHI Project is the joint effort formed with the objective of developing and providing the verification technology for IPv6.
The growth process of IPv4 was the history of encountering various kinds of obstacles and conquering such obstacles. However, once the position as infrastructure was established, it is not allowed to repeat the same history. This is a reason why the verification technology is essential for IPv6 deployment.
We research and develop conformance tests and interoperability tests for IPv6.
We closely work with the KAME project and USAGI project. We help activities of them in the quality side by offering the verification technology we develop in the TAHI project and improve the development efficiency.
We open the results and fruits of the project to the public for FREE. Any developer concerned with IPv6 can utilize the results and fruits of TAHI project freely. A free software plays an important role in progress of the Internet. We believe that providing the verification technology for FREE contributes to advances of IPv6. Besides the programs, the specifications and criteria of verification will be included in the Package.
Enhancements:
- Minor bugfixes in hop count validation.
<<lessTAHI Project is the joint effort formed with the objective of developing and providing the verification technology for IPv6.
The growth process of IPv4 was the history of encountering various kinds of obstacles and conquering such obstacles. However, once the position as infrastructure was established, it is not allowed to repeat the same history. This is a reason why the verification technology is essential for IPv6 deployment.
We research and develop conformance tests and interoperability tests for IPv6.
We closely work with the KAME project and USAGI project. We help activities of them in the quality side by offering the verification technology we develop in the TAHI project and improve the development efficiency.
We open the results and fruits of the project to the public for FREE. Any developer concerned with IPv6 can utilize the results and fruits of TAHI project freely. A free software plays an important role in progress of the Internet. We believe that providing the verification technology for FREE contributes to advances of IPv6. Besides the programs, the specifications and criteria of verification will be included in the Package.
Enhancements:
- Minor bugfixes in hop count validation.
Download (0.63MB)
Added: 2007-06-28 License: BSD License Price:
851 downloads
Other version of TAHI Test Suite
License:BSD License
License:BSD License
Test::Class 0.24
Test::Class is a Perl module that allows you to easily create test classes in an xUnit/JUnit style. more>>
Test::Class is a Perl module that allows you to easily create test classes in an xUnit/JUnit style.
SYNOPSIS
package Example::Test;
use base qw(Test::Class);
use Test::More;
# setup methods are run before every test method.
sub make_fixture : Test(setup) {
my $array = [1, 2];
shift->{test_array} = $array;
};
# a test method that runs 1 test
sub test_push : Test {
my $array = shift->{test_array};
push @$array, 3;
is_deeply($array, [1, 2, 3], push worked);
};
# a test method that runs 4 tests
sub test_pop : Test(4) {
my $array = shift->{test_array};
is(pop @$array, 2, pop = 2);
is(pop @$array, 1, pop = 1);
is_deeply($array, [], array empty);
is(pop @$array, undef, pop = undef);
};
# teardown methods are run after every test method.
sub teardown : Test(teardown) {
my $array = shift->{test_array};
diag("array = (@$array) after test(s)");
};
later in a nearby .t file
#! /usr/bin/perl
use Example::Test;
# run all the test methods in Example::Test
Test::Class->runtests;
Outputs:
1..5
ok 1 - pop = 2
ok 2 - pop = 1
ok 3 - array empty
ok 4 - pop = undef
# array = () after test(s)
ok 5 - push worked
# array = (1 2 3) after test(s)
<<lessSYNOPSIS
package Example::Test;
use base qw(Test::Class);
use Test::More;
# setup methods are run before every test method.
sub make_fixture : Test(setup) {
my $array = [1, 2];
shift->{test_array} = $array;
};
# a test method that runs 1 test
sub test_push : Test {
my $array = shift->{test_array};
push @$array, 3;
is_deeply($array, [1, 2, 3], push worked);
};
# a test method that runs 4 tests
sub test_pop : Test(4) {
my $array = shift->{test_array};
is(pop @$array, 2, pop = 2);
is(pop @$array, 1, pop = 1);
is_deeply($array, [], array empty);
is(pop @$array, undef, pop = undef);
};
# teardown methods are run after every test method.
sub teardown : Test(teardown) {
my $array = shift->{test_array};
diag("array = (@$array) after test(s)");
};
later in a nearby .t file
#! /usr/bin/perl
use Example::Test;
# run all the test methods in Example::Test
Test::Class->runtests;
Outputs:
1..5
ok 1 - pop = 2
ok 2 - pop = 1
ok 3 - array empty
ok 4 - pop = undef
# array = () after test(s)
ok 5 - push worked
# array = (1 2 3) after test(s)
Download (0.046MB)
Added: 2007-06-13 License: Perl Artistic License Price:
863 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above to test search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed