bathroom fixtures
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 12
StoryTestIQ 1.6
StoryTestIQ is a tool for creating Executable Requirements which have also been known as acceptance tests or functional tests. more>>
StoryTestIQ is a tool for creating "Executable Requirements" which have also been known as acceptance tests or functional tests. STIQ was developed based on two other open source acceptance testing tools, Selenium and FitNesse.
This combination allowed StoryTestIQ to capture the web browser based testing facilities and elegant command language of Selenium along with the wiki based editing and pluggable Fit fixture loading of FitNesse. We believe that this increases the productivity of working with StoryTestIQ and also enhances the capabilities of Selenium to test beyond the user interface.
When developing web applications it is helpful for the cross-functional team to have a definitive and executable view of the requirements for a specified iteration.
StoryTestIQ may be used to record what the teams customer needs and get sign off before developing even a single line of code. Most of the test cases which are recorded will be failing. It is the responsibility of the team to implement the requirements in order to make the test cases pass. These practices are based in the tradition of Test-Driven Development.
Although teams would benefit greatly from the above approach in which your entire cross-functional team including the customer, business analyst, QA, development, and anybody else providing input on the product benefits, StoryTestIQ does not enforce this approach.
StoryTestIQ may also be used in traditional development teams to create acceptance and functional tests. They may be used to supplement the teams unit tests with a Test-Driven Development approach or even to automate existing manual test cases.
Check out the page on how to get started. Once you have StoryTestIQ running successfully, take a look at the users guide for more details on how to create test suites and test cases. As you become familiar with creating test cases you may take advantage of more StoryTestIQ commands in your functioanl tests.
<<lessThis combination allowed StoryTestIQ to capture the web browser based testing facilities and elegant command language of Selenium along with the wiki based editing and pluggable Fit fixture loading of FitNesse. We believe that this increases the productivity of working with StoryTestIQ and also enhances the capabilities of Selenium to test beyond the user interface.
When developing web applications it is helpful for the cross-functional team to have a definitive and executable view of the requirements for a specified iteration.
StoryTestIQ may be used to record what the teams customer needs and get sign off before developing even a single line of code. Most of the test cases which are recorded will be failing. It is the responsibility of the team to implement the requirements in order to make the test cases pass. These practices are based in the tradition of Test-Driven Development.
Although teams would benefit greatly from the above approach in which your entire cross-functional team including the customer, business analyst, QA, development, and anybody else providing input on the product benefits, StoryTestIQ does not enforce this approach.
StoryTestIQ may also be used in traditional development teams to create acceptance and functional tests. They may be used to supplement the teams unit tests with a Test-Driven Development approach or even to automate existing manual test cases.
Check out the page on how to get started. Once you have StoryTestIQ running successfully, take a look at the users guide for more details on how to create test suites and test cases. As you become familiar with creating test cases you may take advantage of more StoryTestIQ commands in your functioanl tests.
Download (3.2MB)
Added: 2006-09-17 License: GPL (GNU General Public License) Price:
1135 downloads
Pub Team Football Manager 1.0
Pub Team Football Manager is a football manager software. more>>
Pub Team Football Manager is a football manager software.
From the main screen, there are six options available (yellow buttons) for showing or editing diffrent information during the game. Here is an explanation:
Info: This shows the details of your team such as kit colours and current news items. Kit colours can be changed by clicking them. The latest news from the pub team grapevine is shown, with any items directly relevant to your team are *** starred.
Squad: The place where you pick your team. Players numbered 1 to 11 will play, 12 and above are substitutes or rested. Each players current position, together with his fitness and morale, are indicated next to his name. Further vital statistics of a player are obtained by clicking on his name. To move a player in or out of your first eleven, click on the "Sub" or "Play" button. You may look at other teams squads by clicking on the < and > buttons.
Tactics: Choose the tactics and playing style of your team. A number of formations are available, and you can choose your teams passing style and aggressiveness.
Fixtures: Lists all your fixtures for the current season, including cup fixtures when drawn. You may look at other teams fixtures by clicking on the < and > buttons.
Table: The current league standings. There are two divisions, each containing 16 teams. Your team is indicated by *.
Records: Shows the best wins and record goalscorers for the current season.
Play: Click here to actually play your matches. The weeks fixtures from your division are indicated, with your match highlighted in red. Press "Start Match" to begin the match simulation, but you can later pause if things start to happen too quickly. A match report and stats are available, and are updated as the match plays. If one of your players gets injured, the game will automatically be paused.
To start a new game, select which team you wish to take charge of, and press "Start New Game". The main screen is then displayed, which is controlled by the large yellow buttons, described in the opposite panel...
Your squad consists of many players who frequent your local drinking establishment. Each player has many attributes, which are rated from A+ to F. These affect the gameplay in various ways. For example, a player who is good at tackling may make a good defender, whereas a player whose shooting attribute is high should be put up front.
All the players attributes are available in the "Squad" section by clicking on a players name. Also available is each players preferred position, indicated in brackets e.g. (Def/Mid), although this is only a guide.
The most important attribute is the players fitness. Try to pick players who are reasonably fit wherever possible. Players fitness may improve when rested, but if they are rested too long, their morale may suffer.
The chosen style of play and formation also have an influence, and some options work better with certain kinds of players. It is your job as manager to weigh up all the factors when picking your strategy and players.
As the season progresses, you will sometimes play cup matches. The Cup is a knockout tournament which includes teams from both divisions. If you are knocked out, you will not play in further rounds, but you can still watch the matches.
Occasionally, players will leave your club, and sometimes new players may join. Since it is a pub team, you dont have much control of what your players do. However, players with a low morale are more likely to leave.
At the end of the season, the top three teams from the lower division (B) are promoted to the higher division (A). The game is open-ended and you may continue for as many seasons as you like.
<<lessFrom the main screen, there are six options available (yellow buttons) for showing or editing diffrent information during the game. Here is an explanation:
Info: This shows the details of your team such as kit colours and current news items. Kit colours can be changed by clicking them. The latest news from the pub team grapevine is shown, with any items directly relevant to your team are *** starred.
Squad: The place where you pick your team. Players numbered 1 to 11 will play, 12 and above are substitutes or rested. Each players current position, together with his fitness and morale, are indicated next to his name. Further vital statistics of a player are obtained by clicking on his name. To move a player in or out of your first eleven, click on the "Sub" or "Play" button. You may look at other teams squads by clicking on the < and > buttons.
Tactics: Choose the tactics and playing style of your team. A number of formations are available, and you can choose your teams passing style and aggressiveness.
Fixtures: Lists all your fixtures for the current season, including cup fixtures when drawn. You may look at other teams fixtures by clicking on the < and > buttons.
Table: The current league standings. There are two divisions, each containing 16 teams. Your team is indicated by *.
Records: Shows the best wins and record goalscorers for the current season.
Play: Click here to actually play your matches. The weeks fixtures from your division are indicated, with your match highlighted in red. Press "Start Match" to begin the match simulation, but you can later pause if things start to happen too quickly. A match report and stats are available, and are updated as the match plays. If one of your players gets injured, the game will automatically be paused.
To start a new game, select which team you wish to take charge of, and press "Start New Game". The main screen is then displayed, which is controlled by the large yellow buttons, described in the opposite panel...
Your squad consists of many players who frequent your local drinking establishment. Each player has many attributes, which are rated from A+ to F. These affect the gameplay in various ways. For example, a player who is good at tackling may make a good defender, whereas a player whose shooting attribute is high should be put up front.
All the players attributes are available in the "Squad" section by clicking on a players name. Also available is each players preferred position, indicated in brackets e.g. (Def/Mid), although this is only a guide.
The most important attribute is the players fitness. Try to pick players who are reasonably fit wherever possible. Players fitness may improve when rested, but if they are rested too long, their morale may suffer.
The chosen style of play and formation also have an influence, and some options work better with certain kinds of players. It is your job as manager to weigh up all the factors when picking your strategy and players.
As the season progresses, you will sometimes play cup matches. The Cup is a knockout tournament which includes teams from both divisions. If you are knocked out, you will not play in further rounds, but you can still watch the matches.
Occasionally, players will leave your club, and sometimes new players may join. Since it is a pub team, you dont have much control of what your players do. However, players with a low morale are more likely to leave.
At the end of the season, the top three teams from the lower division (B) are promoted to the higher division (A). The game is open-ended and you may continue for as many seasons as you like.
Download (MB)
Added: 2006-01-13 License: Freeware Price:
1380 downloads
FITpro for Eclipse 0.51
FITpro for Eclipse allows easier creation of FIT tests and suites, more flexible test execution, and more. more>>
FITpro for Eclipse allows easier creation of FIT tests and suites, more flexible test execution, and more.
Main features:
- Create Fit tests in WYSWIG HTML Editor
- Create suites, ordered collections of Fit tests and sub-suites.
- Execute tests and suites.
- Link from tests to related fixtures.
- Insert Test Template into a Fit test, based on an existing fixture.
<<lessMain features:
- Create Fit tests in WYSWIG HTML Editor
- Create suites, ordered collections of Fit tests and sub-suites.
- Execute tests and suites.
- Link from tests to related fixtures.
- Insert Test Template into a Fit test, based on an existing fixture.
Download (2.9MB)
Added: 2007-08-06 License: Eclipse Public License Price:
811 downloads
Q Light Controller 2.6.0
Q Light Controller 2 (QLC) aims to be a free alternative to commercial lighting software and hardware. more>>
Q Light Controller 2 (QLC) aims to be a free alternative to commercial lighting software and hardware. The main emphasis is to build a software that can be used to control any kinds of lighting equipment.
QLC uses the dmx4linux driver suite to access various hardware interfaces. Currently DMX512, Analog 0-10V and MIDI control systems are being supported by dmx4linux. Refer to dmx4linux interfaces for more information on supported interfaces.
Q Light Controller is free software licensed under the GNU General Public License.
Main features:
- Easy to use device-oriented interface
- Control up to 512 DMX/Analog channels thru DMX4Linux
- Use one of the ready-made fixture definitions, or
- Define your own fixtures with the device class editor
- Create fast changing or smoothly fading scenes, chasers and sequences
- Easy programming of moving lights thru a pattern generator
- Conjure your favourite lighting desk layout with the virtual console
<<lessQLC uses the dmx4linux driver suite to access various hardware interfaces. Currently DMX512, Analog 0-10V and MIDI control systems are being supported by dmx4linux. Refer to dmx4linux interfaces for more information on supported interfaces.
Q Light Controller is free software licensed under the GNU General Public License.
Main features:
- Easy to use device-oriented interface
- Control up to 512 DMX/Analog channels thru DMX4Linux
- Use one of the ready-made fixture definitions, or
- Define your own fixtures with the device class editor
- Create fast changing or smoothly fading scenes, chasers and sequences
- Easy programming of moving lights thru a pattern generator
- Conjure your favourite lighting desk layout with the virtual console
Download (1.4MB)
Added: 2006-11-26 License: GPL (GNU General Public License) Price:
1081 downloads
MoMEUnit 1.1.1
MoMEUnit is an instance of the xUnit architecture for unit testing of J2ME applications. more>>
MoMEUnit is an instance of the xUnit architecture for unit testing of J2ME applications. The application is derived from the JUnit framework. It is only CLDC 1.1 compliant.
It overcomes the lack of a reflection API in the J2ME MIDP API and supports main features of the JUnit framework such as ease of development and running of tests, sharing of fixtures among different tests, the ability to perform simultaneous test runs, and much more.
The results of tests are displayed with a progress bar, statistics, and lists of failures or errors with detailed messages for each test.
Main features:
- Calculates list of tests to run based on Test interface implementation and specified patterns. There is no need to specify test cases to run explicitly. Developers can add test cases without configuring test runners.
- Runs test cases of already built J2ME application or builds test application on behalf of developer based on source files, classes, resources and libraries specified.
- Preverifies J2ME application before running tests on demand.
- Formats tests run output by using predefined or custom tests results formatters like in task. All test characteristics including times and stack traces are available.
- Gives developers possibility to choose emulator and/or preverify tool to run by specifying predefined or custom emulator or preverifier.
- Gives developers possibility to configure test J2ME application by specifying attributes of application JAD descriptor and/or manifest.
Enhancements:
- Timeout functionality added to ant Integration package and MIDletTestRunner and minor bugs fixed.
<<lessIt overcomes the lack of a reflection API in the J2ME MIDP API and supports main features of the JUnit framework such as ease of development and running of tests, sharing of fixtures among different tests, the ability to perform simultaneous test runs, and much more.
The results of tests are displayed with a progress bar, statistics, and lists of failures or errors with detailed messages for each test.
Main features:
- Calculates list of tests to run based on Test interface implementation and specified patterns. There is no need to specify test cases to run explicitly. Developers can add test cases without configuring test runners.
- Runs test cases of already built J2ME application or builds test application on behalf of developer based on source files, classes, resources and libraries specified.
- Preverifies J2ME application before running tests on demand.
- Formats tests run output by using predefined or custom tests results formatters like in task. All test characteristics including times and stack traces are available.
- Gives developers possibility to choose emulator and/or preverify tool to run by specifying predefined or custom emulator or preverifier.
- Gives developers possibility to configure test J2ME application by specifying attributes of application JAD descriptor and/or manifest.
Enhancements:
- Timeout functionality added to ant Integration package and MIDletTestRunner and minor bugs fixed.
Download (1.1MB)
Added: 2007-08-15 License: Common Public License Price:
805 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::C2FIT 0.07
Test::C2FIT is a direct Perl port of Ward Cunninghams FIT acceptance test framework for Java. more>>
Test::C2FIT is a direct Perl port of Ward Cunninghams FIT acceptance test framework for Java.
SYNOPSIS
FileRunner.pl input_containing_fit_tests.html test_results.html
perl -MTest::C2FIT -e file_runner input_containing_fit_tests.html test_results.html
perl -MTest::C2FIT -e fit_shell
Great software requires collaboration and communication. Fit is a tool for enhancing collaboration in software development. Its an invaluable way to collaborate on complicated problems - and get them right - early in development.
Fit allows customers, testers, and programmers to learn what their software should do and what it does do. It automatically compares customers expectations to actual results.
This port of FIT has a featureset equivalent to v1.1 of FIT. Dave W. Smiths original port was based on fit-b021021j and Ive updated most of the core to match the 1.1 version.
This port passes the current FIT spec and also implements a all of the examples.
The following functions are provided (and exported) by this module:
file_runner($infile,$outfile)
Process a FIT-document contained in $infile and writes the result to $outfile.
wiki_runer($infile,$outfile)
Same as file_runner, except that not < table >, < tr > and < td > but < wiki >, < table >, < tr > and < td > is searched for in the input document.
fit_shell
Creates an interactive shell from which you can easily run tests. Start it and enter "help" for more information.
Suppose, your tests-related files reside in a directory with three subdirectories: input - where the files come from, output - where the results will be written to and lib - where your fixtures reside, all you need to do is just to enter "runall"
Logging
The file_runner and wiki_runner support filtering of warn messages, similar to javas common logging. To change the log level, use the -L parameter, e.g.:
perl -MTest::C2FIT -e file_runner -- -L 1 input_containing_fit_tests.html test_results.html
There are following log levels defined: 0 - trace, 1 - debug, 2 - info, 3 - warn, 4 - error, 5 - fatal.
In your code, simply use warn "message" if it should be printed out unconditionally or warn 1, " message" if it should be printed out, when log level is either TRACE or DEBUG.
Naming, Namespace(s)
In your FIT-documents, please use the java-style dot-notation for qualifying package names. E.g. if you want the package Domain::Object::Simple to be used, specify it by entering Domain.Object.Simple into your fit document.
Package names should be fully qualified, case is importat. Special care is taken on the fit.* packages, these can be specified either by fit.Name as well as Test.C2FIT.Name.
<<lessSYNOPSIS
FileRunner.pl input_containing_fit_tests.html test_results.html
perl -MTest::C2FIT -e file_runner input_containing_fit_tests.html test_results.html
perl -MTest::C2FIT -e fit_shell
Great software requires collaboration and communication. Fit is a tool for enhancing collaboration in software development. Its an invaluable way to collaborate on complicated problems - and get them right - early in development.
Fit allows customers, testers, and programmers to learn what their software should do and what it does do. It automatically compares customers expectations to actual results.
This port of FIT has a featureset equivalent to v1.1 of FIT. Dave W. Smiths original port was based on fit-b021021j and Ive updated most of the core to match the 1.1 version.
This port passes the current FIT spec and also implements a all of the examples.
The following functions are provided (and exported) by this module:
file_runner($infile,$outfile)
Process a FIT-document contained in $infile and writes the result to $outfile.
wiki_runer($infile,$outfile)
Same as file_runner, except that not < table >, < tr > and < td > but < wiki >, < table >, < tr > and < td > is searched for in the input document.
fit_shell
Creates an interactive shell from which you can easily run tests. Start it and enter "help" for more information.
Suppose, your tests-related files reside in a directory with three subdirectories: input - where the files come from, output - where the results will be written to and lib - where your fixtures reside, all you need to do is just to enter "runall"
Logging
The file_runner and wiki_runner support filtering of warn messages, similar to javas common logging. To change the log level, use the -L parameter, e.g.:
perl -MTest::C2FIT -e file_runner -- -L 1 input_containing_fit_tests.html test_results.html
There are following log levels defined: 0 - trace, 1 - debug, 2 - info, 3 - warn, 4 - error, 5 - fatal.
In your code, simply use warn "message" if it should be printed out unconditionally or warn 1, " message" if it should be printed out, when log level is either TRACE or DEBUG.
Naming, Namespace(s)
In your FIT-documents, please use the java-style dot-notation for qualifying package names. E.g. if you want the package Domain::Object::Simple to be used, specify it by entering Domain.Object.Simple into your fit document.
Package names should be fully qualified, case is importat. Special care is taken on the fit.* packages, these can be specified either by fit.Name as well as Test.C2FIT.Name.
Download (0.26MB)
Added: 2007-06-07 License: Perl Artistic License Price:
869 downloads
Achievo ATK 6.0.0
Achievo ATK is an object oriented Web-application framework. more>>
Achievo ATK is an object oriented Web-application framework. Achievo ATK is targeted at developers who wish to focus on business logic instead of coding HTML.
Where other application frameworks mainly provide a large set of utility classes, ATK provides a complete framework that requires only small amounts of code to get usable applications, while maintaining full flexibility.
In other words, even 10 lines of code get you a working application, but everything that is generated for you can be completely customized.
Main features:
- Modular architecture
- GUI and data internationalisation
- Application level record locking
- Minimum amount of required coding
- Fully customisable
- Themable
- Template driven
- Database abstraction
- GUI abstraction
- User-based, group-based, level-based or custom security schemes
Enhancements:
- AJAX and JSON functionality were added.
- Transparent MySQL replication support and Oracle Savepoints support were added.
- Fixture support was added.
- The GUI has been improved significantly.
- CAPTCHA functionality was added.
- A generic class overloading mechanism was added.
- Over 400 other enhancements and fixes were made.
<<lessWhere other application frameworks mainly provide a large set of utility classes, ATK provides a complete framework that requires only small amounts of code to get usable applications, while maintaining full flexibility.
In other words, even 10 lines of code get you a working application, but everything that is generated for you can be completely customized.
Main features:
- Modular architecture
- GUI and data internationalisation
- Application level record locking
- Minimum amount of required coding
- Fully customisable
- Themable
- Template driven
- Database abstraction
- GUI abstraction
- User-based, group-based, level-based or custom security schemes
Enhancements:
- AJAX and JSON functionality were added.
- Transparent MySQL replication support and Oracle Savepoints support were added.
- Fixture support was added.
- The GUI has been improved significantly.
- CAPTCHA functionality was added.
- A generic class overloading mechanism was added.
- Over 400 other enhancements and fixes were made.
Download (1.2MB)
Added: 2007-06-13 License: GPL (GNU General Public License) Price:
864 downloads
Test::Unit::TestCase 0.14
Test::Unit::TestCase is a unit testing framework base class. more>>
Test::Unit::TestCase is a unit testing framework base class.
SYNOPSIS
package FooBar;
use base qw(Test::Unit::TestCase);
sub new {
my $self = shift()->SUPER::new(@_);
# your state for fixture here
return $self;
}
sub set_up {
# provide fixture
}
sub tear_down {
# clean up after test
}
sub test_foo {
# test the foo feature
}
sub test_bar {
# test the bar feature
}
(Taken from the JUnit TestCase class documentation)
A test case defines the "fixture" (resources need for testing) to run multiple tests. To define a test case:
implement a subclass of TestCase
define instance variables that store the state of the fixture
initialize the fixture state by overriding set_up()
clean-up after a test by overriding tear_down().
Each test runs in its own fixture so there can be no side effects among test runs. Here is an example:
package MathTest;
use base qw(Test::Unit::TestCase);
sub new {
my $self = shift()->SUPER::new(@_);
$self->{value_1} = 0;
$self->{value_2} = 0;
return $self;
}
sub set_up {
my $self = shift;
$self->{value_1} = 2;
$self->{value_2} = 3;
}
For each test implement a method which interacts with the fixture. Verify the expected results with assertions specified by calling $self->assert() with a boolean value.
sub test_add {
my $self = shift;
my $result = $self->{value_1} + $self->{value_2};
$self->assert($result == 5);
}
Once the methods are defined you can run them. The normal way to do this uses reflection to implement run_test. It dynamically finds and invokes a method. For this the name of the test case has to correspond to the test method to be run. The tests to be run can be collected into a TestSuite. The framework provides different test runners, which can run a test suite and collect the results. A test runner either expects a method suite() as the entry point to get a test to run or it will extract the suite automatically.
If you do not like the rather verbose backtrace that appears when a test fails, you can use the quell_backtrace() method. You will get any message provided, but not the backtrace.
<<lessSYNOPSIS
package FooBar;
use base qw(Test::Unit::TestCase);
sub new {
my $self = shift()->SUPER::new(@_);
# your state for fixture here
return $self;
}
sub set_up {
# provide fixture
}
sub tear_down {
# clean up after test
}
sub test_foo {
# test the foo feature
}
sub test_bar {
# test the bar feature
}
(Taken from the JUnit TestCase class documentation)
A test case defines the "fixture" (resources need for testing) to run multiple tests. To define a test case:
implement a subclass of TestCase
define instance variables that store the state of the fixture
initialize the fixture state by overriding set_up()
clean-up after a test by overriding tear_down().
Each test runs in its own fixture so there can be no side effects among test runs. Here is an example:
package MathTest;
use base qw(Test::Unit::TestCase);
sub new {
my $self = shift()->SUPER::new(@_);
$self->{value_1} = 0;
$self->{value_2} = 0;
return $self;
}
sub set_up {
my $self = shift;
$self->{value_1} = 2;
$self->{value_2} = 3;
}
For each test implement a method which interacts with the fixture. Verify the expected results with assertions specified by calling $self->assert() with a boolean value.
sub test_add {
my $self = shift;
my $result = $self->{value_1} + $self->{value_2};
$self->assert($result == 5);
}
Once the methods are defined you can run them. The normal way to do this uses reflection to implement run_test. It dynamically finds and invokes a method. For this the name of the test case has to correspond to the test method to be run. The tests to be run can be collected into a TestSuite. The framework provides different test runners, which can run a test suite and collect the results. A test runner either expects a method suite() as the entry point to get a test to run or it will extract the suite automatically.
If you do not like the rather verbose backtrace that appears when a test fails, you can use the quell_backtrace() method. You will get any message provided, but not the backtrace.
Download (0.044MB)
Added: 2007-06-13 License: Perl Artistic License Price:
864 downloads
XScanMaster 0.6
XScanMaster is a program to control lights using DMX512. more>>
XScanMaster is a program to control intelligent lights using DMX512, based on the fixture library from GrandMA-firmware. The DMX512 output is done using DMX4Linux, which offers support for most common interfaces and many DMX512 lines.
Also included are functions to control fixtures movements in calibrated reference environments. More than one reference setting can be added to any fixture, and any fixture can be selected to run in one of its reference environments or not.
In the environment the user can control the fixture in different coordinate systems. Sceens and cues can be recorded on a fixture:feature base.
Both can be included in other sceens or cues. Playing sceens/cues can be done from one or more "replay units"; each replay unit can run any program at a given speed (beatcounters are included).
<<lessAlso included are functions to control fixtures movements in calibrated reference environments. More than one reference setting can be added to any fixture, and any fixture can be selected to run in one of its reference environments or not.
In the environment the user can control the fixture in different coordinate systems. Sceens and cues can be recorded on a fixture:feature base.
Both can be included in other sceens or cues. Playing sceens/cues can be done from one or more "replay units"; each replay unit can run any program at a given speed (beatcounters are included).
Download (0.19MB)
Added: 2005-04-20 License: GPL (GNU General Public License) Price:
1648 downloads
Web-Based Adult Content Server 0.7.0
Web-Based Adult Content Server is a suite of programs which manage photo sets and video clips of an adult nature. more>>
Web-Based Adult Content Server is a suite of programs which manage photo sets and video clips of an adult nature.
It runs on a home Linux/Unix server and creates a personalized adult Web server in which to store, preuse, and catalogue a personal collection of adult material.
Web-Based Adult Content Server has many features, like model catalogs, attribute-based searching, randomized highlights, new addition lists, and a flexible bookmark mechanism.
Enhancements:
- This release has new features and many bugfixes.
- It includes a new Web-based Model Manager application, locations-based filtering (e.g. Bathroom), and a new connections infrastructure for galleries and ad-hoc collections.
<<lessIt runs on a home Linux/Unix server and creates a personalized adult Web server in which to store, preuse, and catalogue a personal collection of adult material.
Web-Based Adult Content Server has many features, like model catalogs, attribute-based searching, randomized highlights, new addition lists, and a flexible bookmark mechanism.
Enhancements:
- This release has new features and many bugfixes.
- It includes a new Web-based Model Manager application, locations-based filtering (e.g. Bathroom), and a new connections infrastructure for galleries and ad-hoc collections.
Download (0.52MB)
Added: 2007-07-09 License: GPL (GNU General Public License) Price:
848 downloads
CppUnit - C++ port of JUnit 1.12.0
CppUnit is the C++ port of the famous JUnit framework for unit testing. more>>
CppUnit is a C++ unit testing framework. CppUnit project started its life as a port of JUnit to C++ by Michael Feathers.
Main features:
- XML output with hooks for additional data
- Compiler-like text output to integrate with an IDE
- Helper macros for easier test suite declaration
- Hierarchical test fixture support
- Test registry to reduce recompilation need
- Test plug-in for faster compile/test cycle (self testable dynamic library)
- Protector to encapsulate test execution (allow capture of exception not derived from std::exception)
- MfcTestRunner
- QT based graphic test runner
<<lessMain features:
- XML output with hooks for additional data
- Compiler-like text output to integrate with an IDE
- Helper macros for easier test suite declaration
- Hierarchical test fixture support
- Test registry to reduce recompilation need
- Test plug-in for faster compile/test cycle (self testable dynamic library)
- Protector to encapsulate test execution (allow capture of exception not derived from std::exception)
- MfcTestRunner
- QT based graphic test runner
Download (0.70MB)
Added: 2006-06-30 License: LGPL (GNU Lesser General Public License) Price:
1214 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 1
- 1
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above bathroom fixtures 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