Go to the previous, next section.
@everyfooting Author: ensley // Editor: ensley // Texinfo: ensley @| @| 3 December 1994
This Chapter describes the test plan associated witht the Queuer module.
The input to the queuer comes from the interface modules via the named
pipe. As the queuer reads in the data, it will test for validity of
the strings. If the interfaces correctly sent data into the named
pipe and there is a problem when the queuer recieves them, then there
must have been a problem with the operating system (perhaps the file
system) and I would suggest a shutdown because there is no way to
resynchronize the data packets reliably. After the search has been
completed the queuer must then signal the correct interface to tell it
the search is complete. The queuer must test for the pid to be
correct or still existant. If it doesn't exist or can't be signalled
for some reason, the queuer must remove the search result file and
continue on. The testing of this can be done by writing the data
recieved from the interfaces into a log file. This file can be
checked as the interface module is run.
The queuer sends data to the searcher via a pipe. To make sure this
pipe is being used correctly, the queuer can write what it is doing
into a log file. This can be compared to what the searcher has recieved.
They should be the same. Whether the data is actually valid for
searching is not a job for the queuer. The queuer only acts as a
buffer between the interfaces and the searcher.
The queue itself can be tested by having the queue be printed (file or
screen) everytime an action takes place. This can be verified by the
tester for correctness.
Go to the previous, next section.