morgand 01/08/20 16:03:31
Added: latka STATUS.html
Log:
latka status file
Revision Changes Path
1.1 jakarta-commons/latka/STATUS.html
Index: STATUS.html
===================================================================
<html>
<head>
<title>Status File for Jakarta Commons "Latka" Application</title>
<head>
<body bgcolor="white">
<div align="center">
<h1>The Jakarta Commons <em>Latka</em> Application</h1>
<a href="#Introduction">[Introduction]</a>
<a href="#Scope">[Scope of the Package]</a>
<a href="#Dependencies">[Dependencies]</a>
<a href="#Release Info">[Release Info]</a>
<a href="#Committers">[Committers]</a>
<br><br>
</div>
<h3><a name="Introduction">INTRODUCTION</a></h3>
<p>Testing websites is a pain. Many regression tests for a website can
be verified automatically, speeding up the quality assurance process
and allowing the engineers to focus on the more important issues.
Additionally developers may want to monitor their development, QA
and production environment, so that they can be sure that everything
is running as they expect.</p>
<p>Latka is an HTTP functional testing suite for automated QA, acceptance and
regression testing. Latka suites are XML documents, which
can be written and/or modified without writing Java code. Latka tests can be
created quickly and modified easily, even by engineers without Java experience.</p>
<h3><a name="Scope">SCOPE OF THE PACKAGE</a></h3>
<p>The <em>Latka</em> project shall develop an XML-based syntax for HTTP-based
functional tests. Latka will support, at the least, SSL communication and
cookies.</p>
<p>Included within Latka are classes that simulate a user agent. While the backend
HTTP communication is handled by the HttpClient Commons component, the Latka
interfaces simulate some of the behaviour of an actual web browser, including
automatically passing cookies from request to request in a session. We hope
to integrate these classes into a "useragent" package in HttpClient at some point,
since they are a useful abstraction and not tied to Latka in any way, nor do they
modify the core
HttpClient classes.</p>
<p>Latka also includes several validations that can be performed on the HTTP
responses, including checking the status code, byte length, or request timing.
In addition you will be able to customize Latka with your own validators by writing
a couple of simple classes (or not so simple, depending on the complexity of the
actual test).</p>
<a name="Dependencies"></a>
<h3>2. DEPENDENCIES</h3>
<p><em>Latka</em> relies on:
</p>
<ul>
<li>Java Development Kit (Version 1.3 or later)</li>
<li>A JAXP 1.1 implementation</li>
<li>A SAX 2.0 parser conforming to the JAXP 1.1 APIs</li>
<li>An XSLT parser conforming to JAXP 1.1</li>
<li>HttpClient from Commons - for HTTP communcation</li>
<li>Jakarta Log4J logging package</li>
<li>JUnit - for testing</li>
<li>JSSE - SSL support (optional at runtime)</li>
<li>Jakarta-Regexp - regular expression tests and XML preprocessing (for variable
support)</li>
<li>JDOM - for building XML reports</li>
</ul>
<a name="Release Info"></a>
<h3>3. RELEASE INFO</h3>
<p>Current Release: <strong>Unreleased, CVS Repository Only</strong></p>
<p>Planned Next Release: N/A</p>
<a name="Committers"></a>
<h3>4. COMMITTERS</h3>
<p>The following individuals are the primary developers and maintainers of this
component. Developers who plan to use <em>Latka</em> in their own
projects are encouraged to collaborate on the future development of this
component to ensure that it continues to meet a variety of needs.</p>
<ul>
<li>Morgan Delagrange</li>
<li>Doug Sale</li>
<li>Rodney Waldhoff</li>
</ul>
</body>
</html>
