\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
TCP specification. These tests are specified in Table~\ref{tbl:testpairs}. The test cases aim to cover the most interesting parts of the TCP
specification.
+In this test suite the behavior of the outwards (network) interface of the SUT
+is assessed. This is, the behavior of the SUT as
+observed by another system on the network trying to communicate with (a system
+running on the same host as the SUT using) the SUT. This is achieved by running
+man
+echo-server on the system which runs the SUT (a virtual machine) which
+echos back all messages received to the sender. The test scripts will send
+packets to the echo-server and then checks the received
+response to asses whether or not the SUT is preforming as expected.
+
To cover the TCP specification as complete as possible while still maintaining
a feasible test suite the tests are divided into equivalence partitions. Below
these partitions are given.
These partitions were chosen since they correspond to key parts of the TCP
specification.
+%
+% één na laatste packket, moet dit B+3 of B+2 zijn?
+%
+
TCP segments are send over a TCP connection from a \emph{source} to a \emph{destination port}. Therefore segments which are received that have a
source or destination port set to an incorrect value should not be regarded
as segments belonging to the connection by the SUT.
of bit errors occur.
TCP guarantees that segments are delivered \emph{in order}
-,even when they are received
+, 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 segments that are sent
+to the \emph{echo-server} and back. The TCP specification states that such a
+transaction requires the following messages.
+
+\begin{flushleft}
+ Script $-$ SYN $A$ $\rightarrow$ SUT \\
+ Script $\leftarrow$ SYN-ACK $(A+1)$ $B$ $-$ SUT \\
+ Script $-$ ACK $(A+1)$ $(B+1)$ $\rightarrow$ SUT \\
+ Script $-$ ACK-PUSH $(A+1)$ $(B+2)$ \emph{msg} $\rightarrow$ SUT \\
+ Script $\leftarrow$ ACK $(A+2+msg_{length})$ $(B+3)$ $-$ SUT \\
+ Script $\leftarrow$ ACK-PUSH $(A+2+msg_{length})$ $(B+3)$ \emph{msg} $-$ SUT
+\end{flushleft}
+
+%
+% RS ook? FIN?
+%
+
+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 segment in the transaction listed above.
\bigskip
& a & b & b & c & b & \xmark & \xmark & \doTCC & \doTCC\\
& c & a & b & a & b & \xmark & \xmark & \doTCC & \doTCC\\
& c & b & a & c & a & \xmark & \xmark & \doTCC & \doTCC\\
- & b & a & b & c & a & \xmark & \xmark & \doTCC & \doTCC\\
- & b & b & a & b & b & \xmark & \xmark & \doTCC & \doTCC\\
+ & b & a & b & c & a & \xmark & \xmark & \xmark & \doTCC\\
+ & b & b & a & b & b & \xmark & \xmark & \xmark & \doTCC\\
& c & b & b & a & b & \xmark & \doTCC & \doTCC & \doTCC\\
- & b & b & b & a & b & \xmark & \doTCC & \doTCC & \doTCC\\
+ & b & b & b & a & b & \xmark & \xmark & \xmark & \doTCC\\
& a & b & b & b & a & \xmark & \xmark & \doTCC & \doTCC\\
\hline
\end{tabular}
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
\doTCC & The ACK\# for the SEQ\# of the first segments which is
corrupted is received for each consecutive segment send.\\
$\vdots$ & \\
- \setcounter{TCC}{14}
+ \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 & The segment is not attributed to the current connection
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
% verdieping Mercator
-%\begin{longtable}{|p{.2\linewidth}|p{.8\linewidth}|}
- %\hline
- %Nr & 1 \\\hline
- %Title & Single valid request with 1byte payload. \\\hline
- %Input & Generated packets. \\\hline
- %Expected output & Packets echoed back by Echo-Server. \\\hline
- %\multirow{2}{*}{Course of action}
- %& 1. Use the steps listed above in order to start the SUT. \\
- %& 2. Execute the script by running \texttt{\# code/client/tests/1.py} \\\hline
- %Valid trace & Verify that the script prints 'Success'. \\\hline
- %\hline
-%
- %Nr & 2 \\\hline
- %Title & Single valid request with 65495bytes payload. \\\hline
- %Input & Generated packets. \\\hline
- %Expected output & Packets echoed back by Echo-Server. \\\hline
- %\multirow{2}{*}{Course of action}
- %& 1. Use the steps listed above in order to start the SUT. \\
- %& 2. Execute the script by running \texttt{\# code/client/tests/2.py} \\\hline
- %Valid trace & Verify that the script prints 'Success'. \\\hline
- %\hline
-%
- %Nr & 3 \\\hline
- %Title & 5 valid requests with 1byte payload. \\\hline
- %Input & Generated packets. \\\hline
- %Expected output & Packets echoed back by Echo-Server, in the same order as the client sent them. \\\hline
- %\multirow{2}{*}{Course of action}
- %& 1. Use the steps listed above in order to start the SUT. \\
- %& 2. Execute the script by running \texttt{\# code/client/tests/3.py} \\\hline
- %Valid trace & Verify that the script prints 'Success'. \\\hline
- %\hline
-%
- %Nr & 4 \\\hline
- %Title & 5 valid requests with 65495bytes payload. \\\hline
- %Input & Generated packets with 65495bytes payload. \\\hline
- %Expected output & Packets echoed back by Echo-Server, in the same order as the client sent them. \\\hline
- %\multirow{2}{*}{Course of action}
- %& 1. Use the steps listed above in order to start the SUT. \\
- %& 2. Execute the script by running \texttt{\# code/client/tests/4.py} \\\hline
- %Valid trace & Verify that the script prints 'Success'. \\\hline
- %\hline
-%
- %Nr & 5 \\\hline
- %Title & 5 valid requests with 1byte payload sent out of order. \\\hline
- %Input & Generated packets with 1byte payload, two packets are swapped in position. \\\hline
- %Expected output & All requests sent up to and including
- %the swapped packet with the lowest sequence number, the remaining packets are dropped. \\\hline
- %\multirow{2}{*}{Course of action}
- %& 1. Use the steps listed above in order to start the SUT. \\
- %& 2. Execute the script by running \texttt{\# code/client/tests/5.py} \\\hline
- %Valid trace & Verify that the script prints 'Success'. \\\hline
- %\hline
-%
- %Nr & 6 \\\hline
- %Title & Request with corrupted source port. \\\hline
- %Input & Generated packets with 1byte payload, in these packets the source port number is increased by one. \\\hline
- %Expected output & - \\\hline
- %\multirow{2}{*}{Course of action}
- %& 1. Use the steps listed above in order to start the SUT. \\
- %& 2. Execute the script by running \texttt{\# code/client/tests/6.py} \\\hline
- %Valid trace & Verify that the script prints 'Success'. \\\hline
- %\hline
-%
-%
- %Nr & 6 \\\hline
- %Title & Request with corrupted destination port. \\\hline
- %Input & Generated packets with 1byte payload, in these packets the destination port number is increased by one. \\\hline
- %Expected output & - \\\hline
- %\multirow{2}{*}{Course of action}
- %& 1. Use the steps listed above in order to start the SUT. \\
- %& 2. Execute the script by running \texttt{\# code/client/tests/6.py} \\\hline
- %Valid trace & Verify that the script prints 'Success'. \\\hline
- %\hline
-%
-%\end{longtable}
+\begin{longtable}{|p{.2\linewidth}|p{.8\linewidth}|}
+ \hline
+
+ Nr & 1 \\\hline
+ Title & Connect to the \emph{echo-server} without sending a payload. \\\hline
+ Input & Generated packets. \\\hline
+ Expected output & \emph{Echo-server} accepts the connection. \\\hline
+ \multirow{2}{*}{Course of action}
+ & 1. Use the steps listed above in order to start the SUT. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/1.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ Nr & 2 \\\hline
+ Title & Single valid request with 1byte payload. \\\hline
+ Input & Generated packets. \\\hline
+ Expected output & Packets echoed back by Echo-Server. \\\hline
+ \multirow{2}{*}{Course of action}
+ & 1. Use the steps listed above in order to start the SUT. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/1.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+% Nr & 3 \\\hline
+% Title & Single valid request with 65495bytes payload. \\\hline
+% Input & Generated packets. \\\hline
+% Expected output & Packets echoed back by Echo-Server. \\\hline
+% \multirow{2}{*}{Course of action}
+% & 1. Use the steps listed above in order to start the SUT. \\
+% & 2. Execute the script by running \texttt{\# code/client/tests/2.py} \\\hline
+% Valid trace & Verify that the script prints 'Success'. \\\hline
+% \hline
+
+ Nr & 3 \\\hline
+ Title & 5 valid requests with 1byte payload. \\\hline
+ Input & Generated packets. \\\hline
+ Expected output & Packets echoed back by Echo-Server, in the same order as the client sent them. \\\hline
+ \multirow{2}{*}{Course of action}
+ & 1. Use the steps listed above in order to start the SUT. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/3.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ Nr & 4 \\\hline
+ Title & 5 valid requests with 65495bytes payload. \\\hline
+ Input & Generated packets with 65495bytes payload. \\\hline
+ Expected output & Packets echoed back by Echo-Server, in the same order as the client sent them. \\\hline
+ \multirow{2}{*}{Course of action}
+ & 1. Use the steps listed above in order to start the SUT. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/4.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ Nr & 5 \\\hline
+ Title & 5 requests with 1byte 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 1byte 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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/5.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ 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 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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/6.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ %% HIER
+
+ Nr & 7 \\\hline
+ Title & 5 requests with 1byte corrupted payload, corrupted source and destination port. \\\hline
+ Input & Generated packets with 1byte payload, in these packets the payload byte, source and destination ports 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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/7.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ Nr & 8 \\\hline
+ Title & 5 requests with 65495byte corrupted payload, corrupted source and destination port. \\\hline
+ Input & Generated packets with 65495byte payload, in these packets one of the payload bytes, source and destination ports 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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/8.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+
+ Nr & 9 \\\hline
+ Title & 5 requests with 1byte corrupted payload, invalid checksum and the second packet is dropped. \\\hline
+ Input & Generated packets with 1byte payload, in these packets the payload byte and checksum are increased by one. The second 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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/9.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ Nr & 10 \\\hline
+ Title & 5 requests with 65495byte corrupted payload, invalid checksum and the second packet is dropped. \\\hline
+ Input & Generated packets with 65495byte payload, in these packets one of the payload bytes and the checksum are increased by one. The second packet 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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/10.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ 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 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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/11.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+
+ Nr & 12 \\\hline
+ Title & 5 requests with 65495byte corrupted payload that doesn't show up in checksum and corrupted source port and checksum. The 2nd and 3rd packets are swapped. \\\hline
+ Input & Generated packets with 65495byte payload, in these packets one 16bit word in the payload, the source port and checksum are increased by one. A different 16bit word in the payload is decreased by one. The 2nd and 3rd packets are swapped in order to simulate a out-of-order transmission. \\\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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/12.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+
+ Nr & 13 \\\hline
+ Title & Single request with 1byte corrupted payload and corrupted source port, destination port and checksum. \\\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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/13.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ 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 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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/14.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ Nr & 15 \\\hline
+ Title & 5 requests with 65495byte corrupted payload and corrupted source port, destination port and checksum. \\\hline
+ Input & Generated packets with 65495byte payload, in these packets 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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/15.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+ Nr & 16 \\\hline
+ Title & 5 requests with 65495byte corrupted payload that doesn't show up in the checksum, corrupted source port, destination port and checksum. \\\hline
+ Input & Generated packets with 65495byte payload, in these packets one 16bit word in the payload, the source port and checksum are increased by one. Another 16bit word in the payload is decreased by 1. \\\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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/16.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+
+ Nr & 17 \\\hline
+ Title & 5 requests with 1byte payload, corrupted destination port and checksum. The 2nd and 3rd packets are swapped \\\hline
+ Input & Generated packets with 1byte payload, in these packets the destination port and checksum are increased by one. The 2nd and 3rd packets are swapped in order to simulate an out-of-order transmission. \\\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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/17.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+
+
+ Nr & 18 \\\hline
+ Title & 5 requests with 65495byte payload, corrupted destination port and checksum. The 2nd and 3rd packets are swapped \\\hline
+ Input & Generated packets with 65495byte payload, in these packets the destination port and checksum are increased by one. The 2nd and 3rd packets are swapped in order to simulate an out-of-order transmission. \\\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. \\
+ & 2. Execute the script by running \texttt{\# code/client/tests/18.py} \\\hline
+ Valid trace & Verify that the script prints 'Success'. \\\hline
+ \hline
+\end{longtable}
%\begin{tabularx}{\linewidth}{| l | X|}
%\hline
repositories / tt2015.git / blobdiff