/usr/share/doc/lire/dev-manual/ch16s03.html is in lire-devel-doc 2:2.1.1-2.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 | <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Running Tests</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="Lire Developer's Manual"><link rel="up" href="ch16.html" title="Chapter 16. Making Lire “Test-infected”"><link rel="prev" href="ch16s02.html" title="Writing Tests"><link rel="next" href="ch16s04.html" title="Some “Best Practices” on Unit Testing"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Running Tests</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch16s02.html">Prev</a> </td><th width="60%" align="center">Chapter 16. Making Lire <span class="quote">“<span class="quote">Test-infected</span>”</span></th><td width="20%" align="right"> <a accesskey="n" href="ch16s04.html">Next</a></td></tr></table><hr></div><div class="section" title="Running Tests"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id417698"></a>Running Tests</h2></div></div></div><p>To run tests, you use the
<span class="command"><strong>TestRunner.pl</strong></span> script included with the
PerlUnit distribution. You'll need to add the directory
containing the Lire libraries to perl library path. For
example, if you have <span class="command"><strong>TestRunner.pl</strong></span> in
your <code class="filename">~/bin</code> directory, you can run a
test case from the top level source directory like this:
</p><pre class="programlisting">
$ perl -Iall/lib ~/bin/TestRunner.pl tests::ExtendedDlfSchemaTest
</pre><p>
</p><p><code class="systemitem">tests::ExtendedDlfSchemaTest</code>
can be replaced by your TestCase module.
</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch16s02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch16.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch16s04.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Writing Tests </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Some <span class="quote">“<span class="quote">Best Practices</span>”</span> on Unit Testing</td></tr></table></div></body></html>
|