Go to the previous, next section.
@everyfooting Author: hiren // Editor: ensley // Texinfo: ensley @| @| 3 December 1994
Functional testing can be broken in several parts.
This testing should make sure
that the email parser is capable enough of receiving the
email messages and parsing them and saving the necessary
database or not. This can be done by sending different
email messages with either valid or invalid messages and
see that the parser handles them well or not.
Checking as to the commands in
the received email are valid commands or not. This can be done
by sending several mails to the archie server with a combination
of valid and invalid commands. A simple debugger in the parser
should be a great help in this case.
This part of the testing deals with the
database that email interface stores off and uses as part
of the communication mechanism with the sender of the email
as well as the queuer and sitelist builder. This can be
achieved by sending a several test mails for either
requesting searches or addition or deletion of an FTP site.
By monitoring the parser's dealing with those email messages
and the database that it creates/works with, the testing of the
database can be tested.
This testing deals with making sure that the communications with
the queuer and sitelist builder works fine or not. This should
be one of the heavily tested areas as there is a lot of
dependencies on unix network communication, FTP protocol
(for site list builder) etc. etc. and a fair amount of database
handling. While queuer is very busy with other tasks that it is
handling, a testing should be carried out to make sure that the
communication link with the email interface work fine with the
queuer or not. Database should be looked at for the correctness
while the email interface talks to queuer. Responses from the
queuer and sitelist builder results into proper action or not
is another testing action.
Go to the previous, next section.