From: Charlie Gerhardus Date: Thu, 8 Oct 2015 15:44:31 +0000 (+0200) Subject: testware gedoe X-Git-Url: https://git.martlubbers.net/?a=commitdiff_plain;h=f533cfe3ad90ef2202b7563979384fdcccea9ab3;p=tt2015.git testware gedoe --- diff --git a/3eval.tex b/3eval.tex index 19a1441..ee0a965 100755 --- a/3eval.tex +++ b/3eval.tex @@ -10,6 +10,14 @@ are reached the testing will terminate but there is no confidence in the quality of the product. \subsection{Test ware} +As stated in Section \ref{section:levels} a basic \emph{manual test} is performed in order to detect a faulty project early on. +If the SUT fails all second stage test cases we will try to expand the checklist in order to make sure that a similar faulty SUT can be detected during the first stage of testing. + +The packets composed according to \textit{RFC793} as described in Section \ref{section:testenv} are saved for possible reuse. +Since they are created by hand this is a labor intensive task. +It makes sense to keep them around in case the SUT fails certification and the client would request reevaluation of a updated version of the SUT. +If the SUT does in fact pass certification the packets could still be reused in the event an other client would request \textit{RFC793} certification of a similar product. +The same is true for the \emph{Java TCP driven echo server}. \subsection{Issue tracking} Whenever an issue is detected (a test fails) this issue needs to be recorded