X-Git-Url: https://git.martlubbers.net/?a=blobdiff_plain;f=a2%2F1cases.tex;h=b0531b2224581da656a8780cb1e0df89e4e9bc36;hb=92ded11e5cc8e03df27e440d1d12cfaebb59e726;hp=fde211c5cb0bbebef3d17d854c816503915a65a0;hpb=d2bebd393c7e561b90fac2549d7f5af611f5ed1e;p=tt2015.git diff --git a/a2/1cases.tex b/a2/1cases.tex index fde211c..b0531b2 100644 --- a/a2/1cases.tex +++ b/a2/1cases.tex @@ -73,7 +73,7 @@ user permissions. \caption{Preflight checklist\label{tbl:preflight}} \end{longtable} -\subsection{Testing of SUT} +\subsection{Testing of SUT} \label{sec:testingofsut} The SUT is a series of services for other computer programs with no end-user facing interface. Therefore the SUT will be tested solely by calling it's services through various automated scripts. An automated test suite will be @@ -166,11 +166,11 @@ TCP guarantees that segments are delivered \emph{in order} , even when they are received out of order and that missing segments are resend. The SUT should exhibit the same behavior. If segments are received out of order it should -either reassemble them when the missing packet has arrived or request them to -be resend when the Missing segments should be re-requested (by ACK-ing -the correct sequence number). +either reassemble them when the missing segment has arrived or request them to +be resend. Missing segments should be re-requested (by ACK-ing +their sequence number). -A single request consists of a number of packets that are sent +A single request consists of a number of segments that are sent to the \emph{echo-server} and back. The TCP specification states that such a transaction requires the following messages. @@ -190,7 +190,7 @@ transaction requires the following messages. When the \emph{SUT} has received the ACK containing the message it's passed trough to the \emph{echo-server}. The \emph{echo-server} will proceed by ordering the \emph{SUT} to respond by sending the exact same message. When this happens -the \emph{SUT} has to construct the last packet in the transaction listed above. +the \emph{SUT} has to construct the last segment in the transaction listed above. \bigskip @@ -257,12 +257,12 @@ As always, $100\%$ completeness is not feasible, therefore test cases are carefully selected to cover the most interesting parts of the TCP specification to ensure a complete but feasible test suite. -To further increase the coverage of the test suites tests are randomized. The -tests which test the handling of \emph{bit errors}, changes in the \emph{packet -order} and \emph{dropped packets} randomize where they introduce an error. The -test suite runs these tests multiple times to increase the likelihood that they -discover a fault which is only present when an error occurs in a certain -position. +%To further increase the coverage of the test suites tests are randomized. The +%tests which test the handling of \emph{bit errors}, changes in the \emph{segment +%order} and \emph{dropped segments} randomize where they introduce an error. The +%test suite runs these tests multiple times to increase the likelihood that they +%discover a fault which is only present when an error occurs in a certain +%position. To further decrease the number of tests needed test cases are divided into equivalence partitions and the combination of cases as described in @@ -304,7 +304,6 @@ described in Table~\ref{tbl:testpairs}. \hline Test number & Expected results\\ \hline\hline - \doTCC & An ACK\# of the sequence number of the SYN packet + 1. \\ \hline \doTCC & An ACK\# of the send sequence number + 1.\\ \hline \doTCC & An ACK\# of the sequence number of the last send segment + the size of the payload of that segment.\\ \hline @@ -312,31 +311,24 @@ described in Table~\ref{tbl:testpairs}. size of the payload of that segment.\\ \hline \doTCC & An ACK\# of the sequence number of the last send segment + the size of the payload of that segment.\\ \hline - \doTCC & An ACK\# of the sequence number of the swapped packet with the lowest sequence number. \\ \hline \doTCC & The ACK\# for the SEQ\# of the first segments which is corrupted is received for each consecutive segment send.\\ $\vdots$ & \\ - \setcounter{TCC}{10} + \setcounter{TCC}{12} \doTCC & The ACK\# for the SEQ\# of the first segments which is corrupted is received for each consecutive segment send.\\ \hline - \doTCC & An ACK\# of the sequence number of the last send segment + the - size of the payload of that segment.\\ \hline -% \doTCC & The segment is not attributed to the current connection -% and therefore no ACK\# is received. \\ \hline -% \doTCC & The ACK\# for the SEQ\# of the first segments which is -% corrupted is received for each consecutive segment send.\\ \hline -% \doTCC & The ACK\# for the SEQ\# of the first segments which is -% corrupted is received for each consecutive segment send.\\ \hline -% \doTCC & The segment is not attributed to the current connection -% and therefore no ACK\# is received. \\ \hline -% \doTCC & The ACK\# for the SEQ\# of the first segments which is -% corrupted is received for each consecutive segment send.\\ \hline -% \doTCC & The ACK\# for the SEQ\# of the first segments which is -% corrupted is received for each consecutive segment send.\\ \hline -% \doTCC & The ACK\# for the SEQ\# of the first segments which is -% corrupted is received for each consecutive segment send.\\ \hline -% \doTCC & The ACK\# for the SEQ\# of the first segments which is -% corrupted is received for each consecutive segment send.\\ \hline + \doTCC & The segment is not attributed to the current connection + and therefore no ACK\# is received. \\ \hline + \doTCC & The ACK\# for the SEQ\# of the first segments which is + corrupted is received for each consecutive segment send.\\ \hline + \doTCC & The ACK\# for the SEQ\# of the first segments which is + corrupted is received for each consecutive segment send.\\ \hline + \doTCC & The ACK\# for the SEQ\# of the first segments which is + corrupted is received for each consecutive segment send.\\ \hline + \doTCC & The ACK\# for the SEQ\# of the first segments which is + corrupted is received for each consecutive segment send.\\ \hline + \doTCC & The ACK\# for the SEQ\# of the first segments which is + corrupted is received for each consecutive segment send.\\ \hline \end{tabular} \caption{Expected results of test cases} \label{tbl:testcases} @@ -412,7 +404,7 @@ described in Table~\ref{tbl:testpairs}. Nr & 6 \\\hline Title & 5 requests with 65495byte payload with corrupted source port, destination port and checksum. The second segment is omitted in order to simulate a packet drop on the client side. \\\hline - Input & Generated packets with 65495byte payload, second generated packet is removed. \\\hline + Input & Generated segments with 65495byte payload, second generated segment is removed. \\\hline Expected output & All packets are dropped resulting in a connection time-out. \\\hline \multirow{2}{*}{Course of action} & 1. Use the steps listed above in order to start the SUT. \\ @@ -465,7 +457,7 @@ described in Table~\ref{tbl:testpairs}. Nr & 11 \\\hline Title & 5 requests with 65495byte corrupted payload that doesn't show up in checksum and corrupted destination port. The second packet is dropped. \\\hline - Input & Generated packets with 65495byte payload, in these packets one 16bit word in the payload is increased by 1 and another 16bit word is decreased by 1. The destination port is also increase by one and the second packet is removed. \\\hline + Input & Generated packets with 65495byte payload, in these packets one 16bit word in the payload is increased by 1 and another 16bit word is decreased by 1. The destination port is also increase by one and the second segments is removed. \\\hline Expected output & All packets are dropped resulting in a connection time-out. \\\hline \multirow{2}{*}{Course of action} & 1. Use the steps listed above in order to start the SUT. \\ @@ -487,7 +479,7 @@ described in Table~\ref{tbl:testpairs}. Nr & 13 \\\hline Title & Single request with 1byte corrupted payload and corrupted source port, destination port and checksum. \\\hline - Input & Generated packet with 1byte payload, in this packet one byte in the payload, the source port and checksum are increased by one. \\\hline + Input & Generated segment with 1byte payload, in this segment one byte in the payload, the source port and checksum are increased by one. \\\hline Expected output & All packets are dropped resulting in a connection time-out. \\\hline \multirow{2}{*}{Course of action} & 1. Use the steps listed above in order to start the SUT. \\ @@ -497,7 +489,7 @@ described in Table~\ref{tbl:testpairs}. Nr & 14 \\\hline Title & 5 requests with 1byte corrupted payload and corrupted source port, destination port and checksum. \\\hline - Input & Generated packets with 1byte payload, in these packet one byte in the payload, the source port and checksum are increased by one. \\\hline + Input & Generated packets with 1byte payload, in these segment one byte in the payload, the source port and checksum are increased by one. \\\hline Expected output & All packets are dropped resulting in a connection time-out. \\\hline \multirow{2}{*}{Course of action} & 1. Use the steps listed above in order to start the SUT. \\