You can write all these tests using TAP, Test::More and other testing
modules on the CPAN, but it's important to be aware of the distinction.
+<h2 id="smoke_tests">Smoke Tests</h2>
+<a href="http://en.wikipedia.org/wiki/Smoke_testing">“Smoke tests”</a> is a
+term referring to a subset of the tests used to see if the software application
+performs its very basic operation well enough to give way for further testing.
+It is akin to plugining in an Electronics device and making sure it doesn't
+raise smoke from mis-operation. As a result, if the entire tests suite is time
+consuming, the smoke testing should take a short time to perform.
+<h2 id="testing_other_languages">Using Perl for Testing Other Programming Languages</h2>
+You can use Perl to test software written in many other programming languages:
+If you want to perform system tests of foreign applications, you can look at
+the various way for Perl to
+other command-line programs</a>, and for its sockets and networking
+For GUI (= Graphical User-Interface) tests, you can look at
+<a href="http://search.cpan.org/dist/Win32-GuiTest/">Win32-GuiTest</a> and
+If you want to write unit-tests for these applications in Perl, you should
+family of modules</a> that allow you to write native subroutines in Perl.
+Also of interest is the <a href="http://gitorious.org/perl-ctypes">Ctypes for
+Perl</a> project (which is currently under development.).