HTTPs interface test status change

diff --git a/org.glite.lb.doc/src/LBTP-Tests.tex b/org.glite.lb.doc/src/LBTP-Tests.tex
index b63c146..2622e2f 100644 (file)
--- a/org.glite.lb.doc/src/LBTP-Tests.tex
+++ b/org.glite.lb.doc/src/LBTP-Tests.tex
@@ -17,6 +17,8 @@ This subsection gives a comprehensive overview of all system functionality tests
 \hline
 {\tt lb-test-event-delivery.sh} & Implemented & Tries to register a job and log events. Checks if the registration worked and events resulted in state change accordingly. \\
 \hline
+{\tt lb-test-https.sh} & Implemented & Test the HTTPs interface. \\
+\hline
 {\tt lb-test-logevent.sh} & Implemented & Test if local logger accepts events correctly (i.e. returns 0). \\
 \hline
 {\tt lb-test-il-recovery.sh} & Implemented & Tests if iterlogger recovers correctly and processes events logged in between when restarted. \\
@@ -37,6 +39,8 @@ This subsection gives a comprehensive overview of all system functionality tests
 \hline
 {\tt lb-test-purge.pl} & Implemented & Test that LB server purge works correctly. \\
 \hline
+{\tt lb-test-wild.pl} & Implemented & Test LB "in the wild" (test with real-life WMS). \\ 
+\hline
 \end{tabularx}
 
 \subsubsection{Event logging examples}
@@ -391,3 +395,31 @@ do nothing (i.e. nothing was left in the database).
 The example \path{org.glite.lb.client/examples/purge\_test} does exactly this sequence of steps,
 including the checks.
 \end{hints}
+
+\subsection{LB in the Wild---Real-World WMS Test}
+\req\ All \LB services running, working grid infrastructure accessible (including permissions). 
+
+\what
+\begin{enumerate}
+\item Submit a simple \emph{hello-world}-type job.
+\item Submit a simple job and cancel it.
+\item Submit a collection of simple jobs.
+\item Submit a collection and cancel it. 
+\item Submit a simple job that is sure to fail.
+\item Submit a collection of jobs, one of which is sure to fail. 
+\end{enumerate}
+
+In all above cases: Watch the life cycle. Check the resulting state (\emph{Cleared}, \emph{Cancelled} or \emph{Aborted}). Check events received in the course of job execution; events from all relevant components must be present (NS, WM, JC, LM, and LRMS). 
+
+\how\ \ctblb{lb-test-wild.sh <LBSERVER>}
+
+\note\ The test runs automatically. Bear in mind that in a real-life grid, even valid jobs may not always finish succesfully. Analyze failures and re-run if necessary.
+
+\note\ The number of jobs to generate may be specified using the \texttt{-n} argument
+
+\note\ Job submissions are limited to VOCE CEs in normal circumstances. Use the \texttt{-w} argument to override. 
+
+\note\ Due to the nature of grid computing, this test may take hours to complete!  
+
+\result\ Jobs were submitted. Cancel operation worked where applicable. Resulting state was as expected (\emph{Cleared}, \emph{Cancelled} or \emph{Aborted}). Events were received from all components as expected.
+