written driving test
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 7605
Remote Monitoring Agent 1.25
Remote Monitoring Agent (RMA) is an auxiliary application for HostMonitor. more>>
Remote Monitoring Agent (RMA in short) is an auxiliary application for HostMonitor. Enterprise license for Advanced Host Monitor already includes license for 10 installations of the agent. Holders of a Lite, Standard or Professional licenses may buy an additional license for Remote Monitoring Agent separately.
HostMonitor 4.0+ can monitor remote networks using Remote Monitoring Agents (RMA). RMA is small application that accepts requests from HostMonitor, performs test and provides information about test result back to HostMonitor.
Why you may need RMA? Here are just several reasons:
RMA increases security of the network. When you have to run the tests such as CPU Usage test or Performance Counters tests on a remote Windows system, HostMonitor must be able to log in to that system with administrators privileges. Instead you may now use an agent installed on that remote system. In this case HostMonitor will not have to log on to that system at all. HostMonitor needs just one TCP port to communicate with the RMA agent (by default it uses #1055 port, however you may set an agent to use any other port).
Remote Monitoring Agent is also a very useful tool when you have to monitor two (or many) separated networks (connected through Internet). In this case installing just one instance of RMA behind the firewall in network "A" will allow to monitor entire network "A" using the HostMonitor located in the network "B" with just one open TCP port.
RMA decreases the network traffic. E.g. frequent use of "File Integrity" or "Compare Files" tests in an array of remote systems may apply significant load on the network. The more and the bigger files you test the more traffic increase you get. RMA runs locally and sends only the test results to the HostMonitor thus decreasing the amount of network traffic.
Remote Monitoring Agent simplifies network administration. You no longer need to share local drives/folders to perform tests such as File Integrity, Folder/File Size, File Availability, Count Files, etc
RMA for Linux / BSD / Solaris allows you to perform tests that HostMonitor cannot perform. For example HostMonitor cannot monitor processes that are running on Linux systems. RMA can do that.
Main features:
- All traffic between Remote Monitoring Agents and HostMonitor is encrypted.
- It is possible to customize the list of enabled tests for each of the agents (e.g. living only Count Files and UNC tests only).
- You can restrict incoming TCP connections with the list of acceptable addresses.
- With RMA Manager you may configure, restart and even upgrade agent(s) remotely.
<<lessHostMonitor 4.0+ can monitor remote networks using Remote Monitoring Agents (RMA). RMA is small application that accepts requests from HostMonitor, performs test and provides information about test result back to HostMonitor.
Why you may need RMA? Here are just several reasons:
RMA increases security of the network. When you have to run the tests such as CPU Usage test or Performance Counters tests on a remote Windows system, HostMonitor must be able to log in to that system with administrators privileges. Instead you may now use an agent installed on that remote system. In this case HostMonitor will not have to log on to that system at all. HostMonitor needs just one TCP port to communicate with the RMA agent (by default it uses #1055 port, however you may set an agent to use any other port).
Remote Monitoring Agent is also a very useful tool when you have to monitor two (or many) separated networks (connected through Internet). In this case installing just one instance of RMA behind the firewall in network "A" will allow to monitor entire network "A" using the HostMonitor located in the network "B" with just one open TCP port.
RMA decreases the network traffic. E.g. frequent use of "File Integrity" or "Compare Files" tests in an array of remote systems may apply significant load on the network. The more and the bigger files you test the more traffic increase you get. RMA runs locally and sends only the test results to the HostMonitor thus decreasing the amount of network traffic.
Remote Monitoring Agent simplifies network administration. You no longer need to share local drives/folders to perform tests such as File Integrity, Folder/File Size, File Availability, Count Files, etc
RMA for Linux / BSD / Solaris allows you to perform tests that HostMonitor cannot perform. For example HostMonitor cannot monitor processes that are running on Linux systems. RMA can do that.
Main features:
- All traffic between Remote Monitoring Agents and HostMonitor is encrypted.
- It is possible to customize the list of enabled tests for each of the agents (e.g. living only Count Files and UNC tests only).
- You can restrict incoming TCP connections with the list of acceptable addresses.
- With RMA Manager you may configure, restart and even upgrade agent(s) remotely.
Download (0.088MB)
Added: 2007-05-09 License: Freeware Price:
904 downloads
Running Unix Memory Test 0.2
Running Unix Memory Test is a tool to check the memory without interrupting the service. more>>
The goal of RUMT is to check the memory of a computer over a long period of time and almost-real load conditions without having to interrupt the services.
RUMT exploits the possibility of some Unix kernels to selectivly disable some memory areas while still accessing them through the /dev/mem device. The principle of RUMT is to write pseudo-random data in these disabled memory areas, and later check them. This principle and the original code for the deterministic pseudo-random generator are from David Madore.
This distribution contains another variant on the same theme: URUMT allocates a large chunk of memory, locks it in memory using the mlock(2) system call, and scans /dev/mem to find where in physical memory the allocated area is. Then it continuously runs the same tests in that memory.
URUMT can not be used to test a particular area of memory: the kernel will give it whatever physical memory it feels like. But URUMT can be restarted now and then, hopefully getting different physical memory each time.
This is perfect if you suspect you have bad bits, but do not know at all where they are. Once you have sighted the bad bits, you can use a plain RUMT to test more extensively the neighborhood.
<<lessRUMT exploits the possibility of some Unix kernels to selectivly disable some memory areas while still accessing them through the /dev/mem device. The principle of RUMT is to write pseudo-random data in these disabled memory areas, and later check them. This principle and the original code for the deterministic pseudo-random generator are from David Madore.
This distribution contains another variant on the same theme: URUMT allocates a large chunk of memory, locks it in memory using the mlock(2) system call, and scans /dev/mem to find where in physical memory the allocated area is. Then it continuously runs the same tests in that memory.
URUMT can not be used to test a particular area of memory: the kernel will give it whatever physical memory it feels like. But URUMT can be restarted now and then, hopefully getting different physical memory each time.
This is perfect if you suspect you have bad bits, but do not know at all where they are. Once you have sighted the bad bits, you can use a plain RUMT to test more extensively the neighborhood.
Download (0.015MB)
Added: 2005-04-11 License: GPL (GNU General Public License) Price:
1663 downloads
Generic Test Processor 0.79.9d
Generic Test Processor is a processor for a generic test procedure language. more>>
Generic test processor is a language and processor for a language aiming to automatically apply or generate test source code in another language.
It is taken from a library of tests and data conversion operations.
These so generated instances shall be capable of inspecting a system by gathering data and screening this data to meet certain criteria, in other words to have certain attributes.
Enhancements:
- Fixed a bug in results reporting.
<<lessIt is taken from a library of tests and data conversion operations.
These so generated instances shall be capable of inspecting a system by gathering data and screening this data to meet certain criteria, in other words to have certain attributes.
Enhancements:
- Fixed a bug in results reporting.
Download (0.081MB)
Added: 2005-04-14 License: GPL (GNU General Public License) Price:
1654 downloads
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
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
Chart::EPS_graph::Test 0.01d
Chart::EPS_graph::Test is a module for use only with the Chart::EPS_graph module. more>>
SYNOPSIS
From the CLI, call as below where /some/dir/ is any directory you have permission to write to.
perl -e "use Chart::EPS_graph::Test;
print Chart::EPS_graph::Test->full_test(/some/dir);"
From anywhere else call...
use Chart::EPS_graph::Test;
print Chart::EPS_graph::Test->full_test(/some/dir);
With the parent module (Chart::EPS_graph.pm) loaded, call as below. The $foo may be either class or instance (of module Chart::EPS_graph) as it will be ignored. The test module auto-instanciates its own object without need of a new() method. It is just a test, after all.
$foo->full_test(/some/dir);
Then look for both foo.eps and foo.eps.png to be created in /some/dir/.
SUBROUTINES/METHODS
There is but a single method of interest as detailed in the synopsis above.
A special default is in effect if called without /some/dir as an argument. Then output will default to the /home/your_id directory on UNIX or the desktop in Win32 with only the foo.eps (and not the foo.eps.png) being written there. This default behavior exists to allow for the module to be called as a test when first building the module freshly downloaded from CPAN.
In the ordinary, user-diven, case (when /some/dir is supplied as an argument) then this module will allow itself a free hand to search for wherever it is that Ghostscript and/or The GIMP have been installed. It calls the special Perl module File::Find to do this. It must because those programs may be installed in various paths depending upon their version number.
But while being built as a brand new module freshly downloaded from CPAN, taint mode will be in effect. This is a security precaution that disallows many an unsafe condition. Taint mode will disallow that File::Find be free to look about where it likes. Thus, since at time of build we cannot know where Ghostscript and The GIMP might be, and also cannot look for them, then the test must do without them such that only foo.eps and not foo.eps.png may be created during the test.
For use only with the Chart::EPS_graph module...as a full, user-like test thereof.
How this test works is that two files, foo.eps and foo.eps.png will be (over-)written into /some/dir/. The test itself will inspect each of these files for date, size and content. Based upon what it finds it will return a string as its pronouncement on the health of Chart::EPS_graph as a module. That string will contain several lines, all of which should start with "Okay:" and none of which should start with "Oops!".
<<lessFrom the CLI, call as below where /some/dir/ is any directory you have permission to write to.
perl -e "use Chart::EPS_graph::Test;
print Chart::EPS_graph::Test->full_test(/some/dir);"
From anywhere else call...
use Chart::EPS_graph::Test;
print Chart::EPS_graph::Test->full_test(/some/dir);
With the parent module (Chart::EPS_graph.pm) loaded, call as below. The $foo may be either class or instance (of module Chart::EPS_graph) as it will be ignored. The test module auto-instanciates its own object without need of a new() method. It is just a test, after all.
$foo->full_test(/some/dir);
Then look for both foo.eps and foo.eps.png to be created in /some/dir/.
SUBROUTINES/METHODS
There is but a single method of interest as detailed in the synopsis above.
A special default is in effect if called without /some/dir as an argument. Then output will default to the /home/your_id directory on UNIX or the desktop in Win32 with only the foo.eps (and not the foo.eps.png) being written there. This default behavior exists to allow for the module to be called as a test when first building the module freshly downloaded from CPAN.
In the ordinary, user-diven, case (when /some/dir is supplied as an argument) then this module will allow itself a free hand to search for wherever it is that Ghostscript and/or The GIMP have been installed. It calls the special Perl module File::Find to do this. It must because those programs may be installed in various paths depending upon their version number.
But while being built as a brand new module freshly downloaded from CPAN, taint mode will be in effect. This is a security precaution that disallows many an unsafe condition. Taint mode will disallow that File::Find be free to look about where it likes. Thus, since at time of build we cannot know where Ghostscript and The GIMP might be, and also cannot look for them, then the test must do without them such that only foo.eps and not foo.eps.png may be created during the test.
For use only with the Chart::EPS_graph module...as a full, user-like test thereof.
How this test works is that two files, foo.eps and foo.eps.png will be (over-)written into /some/dir/. The test itself will inspect each of these files for date, size and content. Based upon what it finds it will return a string as its pronouncement on the health of Chart::EPS_graph as a module. That string will contain several lines, all of which should start with "Okay:" and none of which should start with "Oops!".
Download (0.024MB)
Added: 2006-10-27 License: Perl Artistic License Price:
1093 downloads
WebInject - Web/HTTP Test Tool 1.35
WebInject is a tool for automated testing of web applications and services. more>>
WebInject is a free tool for automated testing of web applications and services. It can be used to test individual system components that have HTTP interfaces (JSP, ASP, CGI, PHP, Servlets, HTML Forms, etc), and can be used as a test harness to create a suite of [HTTP level] automated functional, acceptance, and regression tests. A test harness, also referred to as a test driver or a test framework, allows you to run many test cases and collect/report your results. WebInject offers real-time results display and may also be used for monitoring system response times.
WebInject can be used as a complete test framework that is controlled by the WebInject User Interface (GUI). Optionally, it can be used as a standalone test runner (text/console application) which can be integrated and called from other test frameworks or applications.
WebInject uses an XML API (interface). This means you can use WebInject without ever seeing its internal implementation (no scripting or programming necessary to use it).
WebInject is written in Perl and can run on any platform that a Perl interpreter can be installed on (MS Windows, GNU/Linux, BSD, Solaris, MAC OS, and many more). Currently, binary executables of WebInject are only available for MS Windows. If you would like to run on other platforms, you must have a Perl interpreter and run it from the Perl source code.
Test cases are written in XML files, using XML tags and attributes, and passed to the WebInject engine for execution against the application/service under test. This abstracts the internals of WebInjects implementation away from the non-technical tester, while using an open architecture [written in Perl] for those that require more customization or modifications.
Result reports are generated in HTML (for viewing) and XML (for tranformation by external programs). These detailed results include pass/fail status, errors, response times, etc. Results are also displayed in a window on the User Interface if you are running the WebInject GUI, and are sent to the STDOUT channel if you are running the WebInject Engine as a standalone (console) application.
HTTP response times can be collected and monitored in real-time during test execution. Timer statistics are calculated and displayed in a monitor window during runtime. When used along with gnuplot (a plotting utility), a response time graph is generated and updated in real-time as the test runs. This is used to verify responses from the application/service under test are within an acceptable range (to meet your SLA or quality of service criteria). This also enables WebInject to be run as a performance probe for application/service monitoring.
<<lessWebInject can be used as a complete test framework that is controlled by the WebInject User Interface (GUI). Optionally, it can be used as a standalone test runner (text/console application) which can be integrated and called from other test frameworks or applications.
WebInject uses an XML API (interface). This means you can use WebInject without ever seeing its internal implementation (no scripting or programming necessary to use it).
WebInject is written in Perl and can run on any platform that a Perl interpreter can be installed on (MS Windows, GNU/Linux, BSD, Solaris, MAC OS, and many more). Currently, binary executables of WebInject are only available for MS Windows. If you would like to run on other platforms, you must have a Perl interpreter and run it from the Perl source code.
Test cases are written in XML files, using XML tags and attributes, and passed to the WebInject engine for execution against the application/service under test. This abstracts the internals of WebInjects implementation away from the non-technical tester, while using an open architecture [written in Perl] for those that require more customization or modifications.
Result reports are generated in HTML (for viewing) and XML (for tranformation by external programs). These detailed results include pass/fail status, errors, response times, etc. Results are also displayed in a window on the User Interface if you are running the WebInject GUI, and are sent to the STDOUT channel if you are running the WebInject Engine as a standalone (console) application.
HTTP response times can be collected and monitored in real-time during test execution. Timer statistics are calculated and displayed in a monitor window during runtime. When used along with gnuplot (a plotting utility), a response time graph is generated and updated in real-time as the test runs. This is used to verify responses from the application/service under test are within an acceptable range (to meet your SLA or quality of service criteria). This also enables WebInject to be run as a performance probe for application/service monitoring.
Download (0.029MB)
Added: 2005-04-12 License: GPL (GNU General Public License) Price:
1662 downloads
Bundle::Test 1.07
Bundle::Test is a set of modules for software and hardware testing using Perl. more>>
Bundle::Test is a set of modules for software and hardware testing using Perl.
SYNOPSIS
A bundle does not have code in it. It is only a list of related modules. It exists only to make it easier to install these modules with one command:
perl -MCPAN -e install Bundle::Test
This bundle, however, in addition to the plain list of modules, also contains some explanation about the modules. There are explanataion even about modules not installed by this bundle but related to testing. Read on.
This bundle installs a set of modules you can use to build all kinds of tests both for your Perl modules and for applications written in any language.
If you know what would you like to test and are looking for the tools, you came to the right place. After reading a short explanation here youll be redirected to the documentation of the respective modules.
If youd like to learn about the testing framework in Perl you should start by reading Test::Tutorial which is a good introduction. After that go on and read the documentation of Test::Simple and Test::More.
Fields that can be tested using Perl
Web Applications
Web Services
Networking devices using Command Line Interface (CLI)
Databases
GUI based applications on Windows
GUI based applications on X-Windows
<<lessSYNOPSIS
A bundle does not have code in it. It is only a list of related modules. It exists only to make it easier to install these modules with one command:
perl -MCPAN -e install Bundle::Test
This bundle, however, in addition to the plain list of modules, also contains some explanation about the modules. There are explanataion even about modules not installed by this bundle but related to testing. Read on.
This bundle installs a set of modules you can use to build all kinds of tests both for your Perl modules and for applications written in any language.
If you know what would you like to test and are looking for the tools, you came to the right place. After reading a short explanation here youll be redirected to the documentation of the respective modules.
If youd like to learn about the testing framework in Perl you should start by reading Test::Tutorial which is a good introduction. After that go on and read the documentation of Test::Simple and Test::More.
Fields that can be tested using Perl
Web Applications
Web Services
Networking devices using Command Line Interface (CLI)
Databases
GUI based applications on Windows
GUI based applications on X-Windows
Download (0.006MB)
Added: 2007-01-09 License: Perl Artistic License Price:
1018 downloads
BwentBot 2.4.5
BwentBot in an event driven IRC bot completely written in Perl. more>>
BwentBot in an event driven IRC bot completely written in Perl. Its goal is to be functional without becoming bloated, and to keep overhead low to run on older systems. BwentBot has many features that make it an ideal bot for IRC channels.
BwentBot is an event driven IRC bot that is completely written in Perl utilizing NET::IRC as its backbone. NET::Google and SOAP::Lite are used for BwentBots !google capability and GDBM_File is used to statically store its hashed databases. BwentBot is made for giving information in channel not to do administration (like #linuxhelp) in storing their massive amounts of relative links and keeping commonly used answers as
information blocks.
Currently, BwentBot works on all Linux and BSD architechtures tested on (redhat x86, fedora c1/2 x86, FreeBSD x86, Debian x86, and Slackware x86) with minimal errors. No other applications are needed to run BwentBot aside from Perl and the associated modules.
Main features:
- info database
- link database
- google search (5 links return by default)
- google powered spell check
- list (to display learned info/links)
- learn/unlearn capabilities (to teach BwentBot links/info/bans/admins/users)
- seen database (list of most recent activity on a channel)
- say and action commands
- ability to ban users
- admin only commands and maintinence
- mid level registered users with limited power
- logging capability
- stats display
- help capability to show how to use commands
<<lessBwentBot is an event driven IRC bot that is completely written in Perl utilizing NET::IRC as its backbone. NET::Google and SOAP::Lite are used for BwentBots !google capability and GDBM_File is used to statically store its hashed databases. BwentBot is made for giving information in channel not to do administration (like #linuxhelp) in storing their massive amounts of relative links and keeping commonly used answers as
information blocks.
Currently, BwentBot works on all Linux and BSD architechtures tested on (redhat x86, fedora c1/2 x86, FreeBSD x86, Debian x86, and Slackware x86) with minimal errors. No other applications are needed to run BwentBot aside from Perl and the associated modules.
Main features:
- info database
- link database
- google search (5 links return by default)
- google powered spell check
- list (to display learned info/links)
- learn/unlearn capabilities (to teach BwentBot links/info/bans/admins/users)
- seen database (list of most recent activity on a channel)
- say and action commands
- ability to ban users
- admin only commands and maintinence
- mid level registered users with limited power
- logging capability
- stats display
- help capability to show how to use commands
Download (0.033MB)
Added: 2006-06-19 License: GPL (GNU General Public License) Price:
1222 downloads
TAHI Test Suite (Upper Layer Protocol) 1.0
TAHI Test Suite provides a mechanism for validating an IPv6 implementation against a standardized test. 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.
Enhancements:
- Ported FreeBSD-4.x
- Dont support FreeBSD 2.x
- pa can decode MIP6 packets
- All interoperability test tools is included.
<<lessEnhancements:
- Ported FreeBSD-4.x
- Dont support FreeBSD 2.x
- pa can decode MIP6 packets
- All interoperability test tools is included.
Download (0.10MB)
Added: 2006-03-14 License: BSD License Price:
1320 downloads
Other version of TAHI Test Suite
mechanism for validating an IPv6 implementation against a standardized test. mechanism for validating an IPv6 implementation against a standardized test for conformanceLicense:BSD License
mod_virgule 1.1
mod_virgule is the Apache C module that powers the Advogato web site. more>>
mod_virgule is the Apache C module that powers the Advogato web site.
XML Virgule Language is an XML data-driven scripting language. Conceptually similar to Lisp and Scheme, at its simplest it is just an HTML parser. Anything that does not have a plug-in module to activate on a tagname in the input is just passed
straight to the output.
xvl, a command-line implementation of the script language, has dynamically loadable modules in c-code that are activated when a tagname in the input is reached. This effectively turns data into code, with the tags properties and child nodes as input.
Some of the tags are very simple, and are implemented in tens of lines of c code. Others activate file or socket I/O operations that can be nested recursively, providing
the means to write XML data-driven client and server applications [I still cant get used to not having to recompile].
This documentation is therefore written as a guide to this fledgling scripting language, and also as an aid to its designer to understand what is really going on.
lsect(intro-example)
(Example Test Tag)
The module can decide what to do with its input. For example, the simple code(< test:tag/ >) in HOWTO-add-new-tags will output a Header "I am a test tag!" at any point in the data stream where code(< test:tag/ >) is placed. If the tag has a property testprop, for example code(< test:tag testprop="brown cows are fun!"/ >) then
it will place the string of the testprop property in the output as well. Additionally, if there is em(not) a property named stop, with any string, then any child nodes of code(< test:tag/ >) will also be processed.
<<lessXML Virgule Language is an XML data-driven scripting language. Conceptually similar to Lisp and Scheme, at its simplest it is just an HTML parser. Anything that does not have a plug-in module to activate on a tagname in the input is just passed
straight to the output.
xvl, a command-line implementation of the script language, has dynamically loadable modules in c-code that are activated when a tagname in the input is reached. This effectively turns data into code, with the tags properties and child nodes as input.
Some of the tags are very simple, and are implemented in tens of lines of c code. Others activate file or socket I/O operations that can be nested recursively, providing
the means to write XML data-driven client and server applications [I still cant get used to not having to recompile].
This documentation is therefore written as a guide to this fledgling scripting language, and also as an aid to its designer to understand what is really going on.
lsect(intro-example)
(Example Test Tag)
The module can decide what to do with its input. For example, the simple code(< test:tag/ >) in HOWTO-add-new-tags will output a Header "I am a test tag!" at any point in the data stream where code(< test:tag/ >) is placed. If the tag has a property testprop, for example code(< test:tag testprop="brown cows are fun!"/ >) then
it will place the string of the testprop property in the output as well. Additionally, if there is em(not) a property named stop, with any string, then any child nodes of code(< test:tag/ >) will also be processed.
Download (0.27MB)
Added: 2006-04-06 License: GPL (GNU General Public License) Price:
1298 downloads
GTestRunner 0.04
GTestRunner is a GTK+-based graphical frontend for running unit tests in Perl. more>>
GTestRunner is a Gtk+ based testrunner module for Perl, inspired by JUnit, but with a slightly different user interface and functionality.
If you were not satisfied with the Tk based graphical frontend that ships with Test-Unit, then GTestRunner is probably the tool of choice when you want to do test driven development in Perl.
It also offers some improvements over the other test runner modules that ship with Test-Unit. You can browse through the tree of test suites, and select individual test suites, test cases and even individual tests to run.
You can use this module in two different ways. Most users will just want to run the script "gtestrunner" to run their test suites. If you want to integrate unit testing into your own software, you will probably use the module Test::Unit::GTestRunner.
Some stupid test suites and test cases are included with this package. Try
gtestrunner Suites/TS_TopLevel.pm
or
gtestrunner Suites::TS_TopLevel
to see gtestrunner in action. The test suites fails five times, and you have probably guessed that this is intentionally, so that you can see all features.
GTestRunner is fully internationalized. See the file README-NLS for details. See the file TRANSLATIONS for information about the currently available languages. Feel free to contact the author if you want to contribute a translation for your own native langauge.
<<lessIf you were not satisfied with the Tk based graphical frontend that ships with Test-Unit, then GTestRunner is probably the tool of choice when you want to do test driven development in Perl.
It also offers some improvements over the other test runner modules that ship with Test-Unit. You can browse through the tree of test suites, and select individual test suites, test cases and even individual tests to run.
You can use this module in two different ways. Most users will just want to run the script "gtestrunner" to run their test suites. If you want to integrate unit testing into your own software, you will probably use the module Test::Unit::GTestRunner.
Some stupid test suites and test cases are included with this package. Try
gtestrunner Suites/TS_TopLevel.pm
or
gtestrunner Suites::TS_TopLevel
to see gtestrunner in action. The test suites fails five times, and you have probably guessed that this is intentionally, so that you can see all features.
GTestRunner is fully internationalized. See the file README-NLS for details. See the file TRANSLATIONS for information about the currently available languages. Feel free to contact the author if you want to contribute a translation for your own native langauge.
Download (0.040MB)
Added: 2006-05-13 License: GPL (GNU General Public License) Price:
1259 downloads
Acme::Tests 0.03
Acme::Tests is a Perl module to see how much do you know. more>>
Acme::Tests is a Perl module to see how much do you know.
SYNOPSIS
perl Makefile.PL
make test
This module is a "test software", it has tests in the software rather then software tests. Upon installation, you are reqruied to answered several question, and the installation would be only successful if all you pass them all.
<<lessSYNOPSIS
perl Makefile.PL
make test
This module is a "test software", it has tests in the software rather then software tests. Upon installation, you are reqruied to answered several question, and the installation would be only successful if all you pass them all.
Download (0.011MB)
Added: 2007-03-07 License: GPL (GNU General Public License) Price:
961 downloads
phpautotest 1.0.3
phpautotest is a tool for conducting automated regression tests on PHP-driven Web sites. more>>
phpautotest is a tool for conducting automated regression tests on PHP-driven Web sites. Variable values as well as HTTP output can be tested.
HTTP output is tested using regular expressions.
<<lessHTTP output is tested using regular expressions.
Download (0.18MB)
Added: 2006-05-11 License: MIT/X Consortium License Price:
1264 downloads
wipe 2.2.0
Wipe is a file and block device wiping utility. more>>
Wipe is a file and block device wiping utility. It is based on work by Peter Gutmann.
There are some low level issues that must be taken into consideration. One of these is that there must be some sort of write barrier between passes. Wipe uses fdatasync(2)
(or fsync(2)) as a write barrier, or if fsync(2) isnt available, the file is opened with the O_DSYNC or O_SYNC flag.
For wipe to be effective, each pass must be completely written. To ensure this, the drive must support some form of a write barrier, write cache flush, or write cache disabling. SCSI supports ordered command tags, has a force
media access bit for commands, and write cache can be disable on mode page 8. IDE/ATA drives support write cache flushes and write cache disabling.
Unfortunetly, not all drives actually disable write cache when yjhis is set up.Those drives are broken. Write caching should always be disabled, unless your system is battery backed and always powers down cleanly.
Enhancements:
- typo in Makefile.in (Ricardo Branco)
<<lessThere are some low level issues that must be taken into consideration. One of these is that there must be some sort of write barrier between passes. Wipe uses fdatasync(2)
(or fsync(2)) as a write barrier, or if fsync(2) isnt available, the file is opened with the O_DSYNC or O_SYNC flag.
For wipe to be effective, each pass must be completely written. To ensure this, the drive must support some form of a write barrier, write cache flush, or write cache disabling. SCSI supports ordered command tags, has a force
media access bit for commands, and write cache can be disable on mode page 8. IDE/ATA drives support write cache flushes and write cache disabling.
Unfortunetly, not all drives actually disable write cache when yjhis is set up.Those drives are broken. Write caching should always be disabled, unless your system is battery backed and always powers down cleanly.
Enhancements:
- typo in Makefile.in (Ricardo Branco)
Download (0.068MB)
Added: 2006-07-13 License: GPL (GNU General Public License) Price:
1947 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 written driving 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
