small cleanup before publishing

diff --git a/org.glite.lb.doc/src/LBTP-Introduction.tex b/org.glite.lb.doc/src/LBTP-Introduction.tex
index d57c4c7..4702b03 100644 (file)
--- a/org.glite.lb.doc/src/LBTP-Introduction.tex
+++ b/org.glite.lb.doc/src/LBTP-Introduction.tex
@@ -37,8 +37,8 @@ we consider two test categories with the following test types:
 They also check for basic, not depending on other grid services, functionality
 of the component (e.g. daemon is up and running).
 \begin{itemize}
-\item Installation tests, see Section~\ref{s:installation}
-\item Configuration tests, see Section~\ref{s:configuration}
+\item Installation tests %, see Section~\ref{s:installation}
+\item Configuration tests %, see Section~\ref{s:configuration}
 \item Service ping tests: basic tests if service is up and running, see Section~\ref{s:ping}
 \end{itemize}
 %
@@ -47,8 +47,8 @@ interaction with other grid services.
 \begin{itemize}
 \item Functionality tests of fully supported functionality (including APIs and CLI), see Section~\ref{s:functionality}
 \item Performance and stress tests, see Section~\ref{s:perftests}
-\item Interoperability tests, see Section~\ref{s:interoperability}
-\item Security tests, see Section~\ref{s:security}
+\item Interoperability tests %, see Section~\ref{s:interoperability}
+\item Security tests %, see Section~\ref{s:security}
 \end{itemize}
 \end{description}
 
@@ -86,7 +86,7 @@ of probes which are submitted at regular intervals, and a database that stores
 test results. In effect, SAM provides monitoring of grid services from a user
 perspective.
 
-\TODO{ljocha: More about SAM. How LB is integrated - LB sensors for SAM}
+%\TODO{ljocha: More about SAM. How LB is integrated - LB sensors for SAM}
 
 
 \subsubsection{Nagios}
@@ -95,7 +95,7 @@ Nagios\footnote{\url{http://www.nagios.org}} is a host and service monitor
 designed to inform you of network problems before your clients, end-users or
 managers do.
 
-\TODO{ruda: More about Nagios. How LB is integrated - LB sensors for Nagios}
+%\TODO{ruda: More about Nagios. How LB is integrated - LB sensors for Nagios}
 
 
 \subsubsection{ETICS}
@@ -129,4 +129,4 @@ to test the basic functionality of the service which is stopped again at the
 end of the test
 
 \end{itemize}
-\TODO{More about LB tests for individual modules}
+%\TODO{More about LB tests for individual modules}

diff --git a/org.glite.lb.doc/src/LBTP-Tests.tex b/org.glite.lb.doc/src/LBTP-Tests.tex
index 0e005ff..d500e84 100644 (file)
--- a/org.glite.lb.doc/src/LBTP-Tests.tex
+++ b/org.glite.lb.doc/src/LBTP-Tests.tex
@@ -13,7 +13,7 @@ This subsection gives a comprehensive overview of all system functionality tests
 \hline
 {\tt lb-test-job-registration.sh} & Implemented & Tries to register a job and checks if the registration worked. \\
 \hline
-{\tt lb-test-normal-event-delivery-remote.sh} & Implemented & Tries to register a job and log events. Checks if the registration worked and events resulted in state change accordingly. \\
+{\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-logevent.sh} & Proposed & Test if local logger accepts events correctly (i.e. returns 0). \\
 \hline
@@ -178,6 +178,10 @@ in the job state same as the `*' part of the script name.
 
 
 
+\subsection{Query tests}
+\TODO{query all my jobs, query one job, query with some structured conditions, some other queries that caused problems in the past, ...}
+
+
 \subsection{LB server and proxy combined test}
 
 \req\ running \path{glite-lb-proxy}, \path{glite-lb-interlogd} and
@@ -193,7 +197,7 @@ job status and to the automatic purge from proxy.
 
 \how\ \ctblb{lb-test-proxy-delivery.sh}
 
-\TODO{mozna to ma prijit do nejakeho testsuitu, netusim} 
+%\TODO{mozna to ma prijit do nejakeho testsuitu, netusim} 
 {\tt glite-lb-running.sh -x -m LB\_HOST:PORT} \\
 - logs sequence of events and returns JOBID \\
 
@@ -215,7 +219,7 @@ are really purged from the proxy.
 
 
 \subsection{WS interface}
-\TODO{fila: ws example + html example}
+\TODO{fila, valtri: tests using java example}
 \req\ \path{glite-lb-bkserverd} running, events from \ref{normal} logged
 
 \what\ retrieve both events and job states with the \LB\ WS interface
@@ -234,17 +238,27 @@ the same form as e.g. \path{glite-lb-jobstat}.
 
 
 
+\subsection{HTML interface}
+\TODO{fila: query tests using wget/curl}
+
+
+
 \subsection{Change ACL}
-\TODO{kouril: pozdeji - s novym auth. schematem. dopsat TODO jak}
+\TODO{kouril: to be added later with new authz schema}
 
 
 
 
 \subsection{Notifications}
-\TODO{ruda: revize, doplnit nove optiony}
 % notifikace
 % regjob, reg notifikace na vsechno, poslat udalosti, hlidat notif
 
+All notification tests require the \LB server to be run with notifications enambled,
+i.e. to be run for example with options 
+\texttt{--notif-il-sock /tmp/sock.test\_notif --notif-il-fprefix /tmp/test\_notif}, 
+where \texttt{/tmp/sock.test\_notif} is a socket of notification interlogger.
+
+Plese see also \cite{lbug}, Section 2.4, for other possible scenarios how to test the notification delivery.
 
 
 \subsubsection{Single job, any state change}
@@ -266,7 +280,7 @@ and repeatedly invoke \code{edg\_wll\_NotifReceive}.
 notification client.
 
 \begin{hints}
-\path{glite-lb-notify} example can be used with its \path{test} command.
+\path{glite-lb-notify} example can be used with its commands \path{new} and \path{receive}.
 \end{hints}