[Cluster-devel] conga/luci/test test_plan.html

Fri Oct 13 15:03:30 UTC 2006

CVSROOT:	/cvs/cluster
Module name:	conga
Changes by:	jparsons at sourceware.org	2006-10-13 15:03:29

Modified files:
	luci/test      : test_plan.html 

Log message:
	updates...

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/luci/test/test_plan.html.diff?cvsroot=cluster&r1=1.2&r2=1.3

--- conga/luci/test/test_plan.html	2006/09/26 14:57:44	1.2
+++ conga/luci/test/test_plan.html	2006/10/13 15:03:29	1.3
@@ -2,6 +2,10 @@
  <head><title>Conga Test Plan</title></head>
  <body>
   <h2>Conga Testing Plan</h2>
+  <h4>General Testing Notes</h4>
+  Most testing of Conga will undoubtedly be made through the luci user interface. This is the manner in which it is anticipated to be used. Scripts are available in the 'QA Goodies' repository detailed at the end of this document, that will test ricci directly and will be very valuable for identifying regressions and making certain upgrades go smoothly; Still, the large part of this document adddresses luci testing.<p/>
+Every page throughout the luci interface has a title, which will be rendered in the title bar area of the browser. It is hoped that using these page names will promote immediate understanding of where an issue is taking place when qa and engineering communicate. It is also hoped that URLs will be pasted into BZ tickets whenever possible.<p/>
+  As a lead developer on Conga, I hope for a thorough QA shakeout of the product before release. I can tell you my greatest worry, and perhaps it might inform testing. I worry most about corner cases being missed in the code that results in errors that are not handles properly. If, at any time, a cryptic error message (such as 'Key error: missing "statusmessage" value', or 'Type Error: cannot concatenate string and none type') appears inn the browser window, then we have failed. The source of many of these types of error messages, I fear, will be attempts to contact ricci agents that are refusing connection for some reason. Please keep a lookout for these cases. Shutting down systems registered with luci and then poking and prodding them through the interface might be a good approach.<p/>
   This document breaks the Conga remote administration tool down into 5 separate pieces for testing consideration:
   <ul>
    <li>The ricci agent</li>
@@ -12,7 +16,7 @@
   </ul>
   For additional information about Conga and how it works, please see:<br/>
   sources.redhat.com/cluster/conga  for architectural info.<br/>
-  CVS checkout of conga/luci/docs/user_manual.html for a user manual<br/>
+  sources.redhat.com/cluster/conga/doc/user_manual.html for a user manual<br/>
   sources.redhat.com/cluster/conga/usecases/usecase_index.html for use cases
   <h3>Ricci Agent Testing</h3>
   The ricci agent is installed on every system to be remotely administered. It is a daemon that runs as non-root and talks to ricci modules via Dbus and Oddjob. The main ricci agent code acts as a dispatcher for the ricci modules, by reading the incoming XML and sending it via Dbus to the correct module, and then returning the modules result to the originating luci server.<p/>
@@ -23,6 +27,15 @@
   After a luci server is installed, it is accessible via https connection to port 8084; but should be inaccessible immediately after install, until the initial admin password is set. The first time that the luci service is started, it checks to see if an admin password exists, and if it does not, it should offer the user (root user, as only root can start the luci service) the opportunity to set an initial admin password. The admin password can be changed at any time by running the luci_admin tool and restarting the luci service (more on the luci_admin tool later).<br/>
   After the luci service is up and running and an admin password has been established, the next step is to log in. Browse to https://yourserver:8084/luci. You should see a log in page. After logging in, you will not need to log in again as long as a browser window remains open. <br/>Luci is organized into three tabs: Homebase, Cluster, and Storage. After logging in, you should be at the luci Homebase tab.
   <h4>Luci Homebase Tab</h4>
-
+  In a fresh luci install, there will be three options:
+  <ul><li>Add a system</li>
+      <li>Add an existing cluster</li>
+      <li>Add a User</li>
+  </ul>
+   <h4>Testing the Add a System capability</h4>
+    This page is know as the 'luci - cluster - add system' page. <br/>
+    The 'Add a system to be managed' use case is satisfied here. The page allows for multiple systems to be added
+    Try and add systems that don't exist. Try usinng the wrong password on legitimate systems with ricci agents. See if you can add a system twice...once by hostname and once by IP address.
+    
  </body>
 </html>


