Added a few test desriptions.

[gnucomo.git] / doc / test.xml

diff --git a/doc/test.xml b/doc/test.xml
index fa04f23..aad6716 100644 (file)
--- a/doc/test.xml
+++ b/doc/test.xml
@@ -6,7 +6,7 @@
 <!--
       Gnucomo - Gnu Computer Monitoring Test description
       Original author :  Arjen Baart - arjen@andromeda.nl
-      Version         : $Revision: 1.1 $
+      Version         : $Revision: 1.2 $
 
       This document is prepared for XMLDoc. Transform to HTML,
       LaTeX, Postscript or plain text with XMLDoc utilities and
@@ -144,6 +144,84 @@ This tests problem report nr. 30.
 </para>
 </section>
 
+<section>
+<heading>Test 0013: RPM package updates</heading>
+<para>
+Create an object and parse an RPM package list and another RPM package
+list where some packages are upgraded and removed.
+Parameters and properties are created in the database.
+Reading the second list should lead to notifications and additional
+records in the parameter history table.
+</para>
+</section>
+
+<section>
+<heading>Test 0014: RPM package update repeats</heading>
+<para>
+Create an object and parse an RPM package list and another RPM package
+list where some packages are upgraded and removed.
+The second package list is read twice.
+Parameters and properties are created in the database.
+Reading the second list should lead to notifications and additional
+records in the parameter history table.
+Reading the second list another time should not change anything in the
+database.
+This tests PR 31.
+</para>
+</section>
+<section>
+<heading>Test 0015: Debian package list and repeated updates</heading>
+<para>
+
+ Debian package list and repeated updates
+
+This is basically the same test as test 0014, except we are now using
+a Debian list from 'dpkg -l' instead of RPM.
+Create an object and parse a Debian package list and another Debian package
+list where some packages are upgraded and removed.
+The second package list is read twice.
+Parameters and properties are created in the database.
+Reading the second list should lead to notifications and additional
+records in the parameter history table.
+Reading the second list another time should not change anything in the
+database.
+This tests PR 31.
+</para>
+
+</section>
+
+<section>
+<heading>Test 0020: Logrunner normal operation</heading>
+<para>
+Read a small logfile and check the XML output created
+by logrunner.
+Logrunner will put the hostname of the system where the test
+is run in the ouput file.
+</para>
+</section>
+
+<section>
+<heading>Test 0021: Logrunner continuation</heading>
+<para>
+Read a small logfile in two parts and check the XML output created
+by logrunner.
+After reading the log for the first time, additional content is added
+to the file and logrunner is called a second time.
+This tests whether logrunner will continue a log file after additional
+data is appended to that log file.
+</para>
+</section>
+
+<section>
+<heading>Test 0022: Logrunner long lines</heading>
+<para>
+Read a small logfile with a long (> 4096 bytes) line.
+Logrunner should create an XML message with the long
+line intact.
+Note that the line is longer than logrunner's input buffer.
+</para>
+</section>
+
 </chapter>
 
 </book>