\hline\hline
Check 3 & \multicolumn{2}{l|}{Initialize the testing environment..}\\
\hline
- \multirow{5}{*}{Course of action}
+ \multirow{6}{*}{Course of action}
& 1. & Boot the SUT as in \emph{Check 1}.\\
& 2. & Setup iptables by executing
\texttt{\# code/iptables.sh}~\footnote{The IPTables script ensures
& 3. & Navigate to the working directory by running
\texttt{\$ cd /home/student/tt2015}\\
& 4. & Compile the echo server by running
- \texttt{\# cd code/server \&\& make \&\& cd -}\\
+ \texttt{\# cd code/server \&\& make}\\
& 5. & Start the echo server by running
\texttt{\# cd code/server \&\& java Main}\\
+ & 6. & Generate all test cases by running
+ \texttt{\$ python code/client/gen.py}\\
\hline
Passed & \multicolumn{2}{l|}{\textit{Yes/No}}\\
\hline\hline
The implementation of the SUT is tested using black box testing techniques. A
series of tests asses the correctness of the implementation with regards to the
-TCP specification. These tests are specified in Table~\textbf{referentie naar
-tests-tabel}. The test cases aim to cover the most interesting parts of the TCP
+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.
\item Correct
\item Incorrect
\end{enumerate}
- \item \emph{Packet order}
+ \item \emph{Segment order}
\begin{enumerate}
\item Correct
\item Out of order
- \item Missing packets
+ \item Missing Segments
\end{enumerate}
\end{enumerate}
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).
+A single request consists of a number of packets 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 packet in the transaction listed above.
+
\bigskip
Partitions 2 to 6 are tested using pairwise testing to keep the number of test
cases feasible. The pairs are then all *except some where it does not make sense
to do so) tested with the different request sizes of partition 1.
-This is expressed in Table~\ref{table:testpairs}.
+This is expressed in Table~\ref{tbl:testpairs}. In this table the first five
+columns represent the different options for the partitions 2 to 6 of the above
+enumeration. The last four columns are the different number segments as
+described in the partition 1 of the above enumeration. These cells identify
+individual test cases by a number. An \xmark in the cell indicates that this
+test case can not be created as it is not possible with that number of segments
+(eg. sending segments out of order when the number of segments is 1).
-\newcounter{TCC}
\setcounter{TCC}{1}
-\newcommand{\doTCC}{\theTCC \stepcounter{TCC}}
\begin{table}[H]
\centering
- \begin{tabular}{|l|l|l|l|l|l|l|l|l|l|l|}
+ \begin{tabular}{|l|l|l|l|l|l||l|l|l|l|}
\hline
- & \multicolumn{10}{c|}{\textbf{Partition}}\\
+ & \multicolumn{9}{c|}{\textbf{Partition}}\\
\hline
- & \# & 4 & 5 & 3 & 6 & 2 & 1a & 1b & 1c & 1d\\
+ & 4 & 5 & 3 & 6 & 2 & 1a & 1b & 1c & 1d\\
\hline\hline
\multirow{9}{*}{Instance}
- & 1 & a & a & a & a & a & \doTCC & \doTCC & \doTCC & \doTCC\\
- & 2 & a & b & b & c & b & \xmark & \xmark & \doTCC & \doTCC\\
- & 3 & c & a & b & a & b & \xmark & \xmark & \doTCC & \doTCC\\
- & 4 & c & b & a & c & a & \xmark & \xmark & \doTCC & \doTCC\\
- & 5 & b & a & b & c & a & \xmark & \xmark & \doTCC & \doTCC\\
- & 6 & b & b & a & b & b & \xmark & \xmark & \doTCC & \doTCC\\
- & 7 & c & b & b & a & b & \doTCC & \doTCC & \doTCC & \doTCC\\
- & 8 & b & b & b & a & b & \doTCC & \doTCC & \doTCC & \doTCC\\
- & 9 & a & b & b & b & a & \xmark & \xmark & \doTCC & \doTCC\\
+ & a & a & a & a & a & \doTCC & \doTCC & \doTCC & \doTCC\\
+ & 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\\
+ & c & b & b & a & b & \xmark & \doTCC & \doTCC & \doTCC\\
+ & b & b & b & a & b & \xmark & \doTCC & \doTCC & \doTCC\\
+ & a & b & b & b & a & \xmark & \xmark & \doTCC & \doTCC\\
\hline
-\end{tabular}
+ \end{tabular}
\caption{Combinations of test cases}
-\label{table:testpairs}
+\label{tbl:testpairs}
\end{table}
\subsection{Quality, completeness and coverage of tests}
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 test suite.
+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 decrease the number of tests needed test cases are divided into
equivalence partitions and the combination of cases as described in
-Table~\ref{table:testpairs} ensures that all partitions are
+Table~\ref{tbl:testpairs} ensures that all partitions are
covered and the number of individual tests is still feasible.
%
-\subsection{Test cases}
+\subsection{Test suite}
-Before every test case use the following steps to initialize the testing environment.
+Before executing the test suite the test environment has to be initialized.
\begin{enumerate}
\item Boot the vm using VirtualBox.
\item Setup iptables by executing \texttt{\# code/iptables.sh}
- \item Navigate to the working directory by running \texttt{\$ cd /home/student/tt2015}
- \item Start the echo server by running \texttt{\# cd code/server \&\& java Main}
+ \item Navigate to the working directory by running
+ \texttt{\$ cd /home/student/tt2015}
+ \item Start the echo server by running
+ \texttt{\# cd code/server \&\& Java Main}
\end{enumerate}
+\subsubsection{Preflight checks}
+The we do the preflight checks as defined in Table~\ref{tbl:preflight}.
+
+\subsubsection{Test Cases}
+If the SUT passes the preflight checks the actual test cases can be executed.
+Table~\ref{tbl:testcases} shows the expected results of each of the test cases
+described in Table~\ref{tbl:testpairs}.
+
+\setcounter{TCC}{1}
+\begin{table}[H]
+ \centering
+ \begin{tabular}{|l|p{.7\linewidth}|}
+ \hline
+ Test number & Expected results\\
+ \hline\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
+ \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 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}
+ \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
+ \end{tabular}
+\caption{Expected results of test cases}
+\label{tbl:testcases}
+\end{table}
+
+% Bij Ramons afwezigheid
+% Paul Vitero (linkerkant lange gang)
+% verdieping Mercator
+
+
\begin{longtable}{|p{.2\linewidth}|p{.8\linewidth}|}
\hline
Nr & 1 \\\hline
& 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
& 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
+ the swapped packet with the lowest sequence number, the remaining packets are ropped. \\\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
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
+ Input & Generated packets with 1byte payload, in these packets the source port Number is increased by one. \\\hline
+ Expected output & The Echo server will receive the packet but is not able to respond with a ACK, this will result 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
\hline
- Nr & 6 \\\hline
+ Nr & 7 \\\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
+ Expected output & The packets will never reach the Echo-server 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
+ & 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 & Request with corrupted source address. \\\hline
+ Input & Generated packets with 1byte payload, in these packets the source address is replaced with 255.255.255.255. \\\hline
+ Expected output & The Echo-server will receive packet and is unable to respond with a ACK 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 & Request with corrupted destination address. \\\hline
+ Input & Generated packets with 1byte payload, in these packets the destination address is replaced with 255.255.255.255. \\\hline
+ Expected output & The packets will never reach the Echo-server 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 & Request with corrupted payload detectable by checksum. \\\hline
+ Input & Generated packets with 1byte payload, in these packets one byte is increased by 1 after the checksum has been calculated. \\\hline
+ Expected output & The \emph{SUT} will drop packets before sending them resulting in a runtime error of the test script. \\\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 & Request with corrupted payload undetectable by checksum. \\\hline
+ Input & Generated packets with 1byte payload, in these packets one 16bit word is increased by 1 and an other 16bit word is decreased by 1, after the checksum has been calculated. \\\hline
+ Expected output & Echo-server receives the corrupted segment. \\\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
+
\end{longtable}
%\begin{tabularx}{\linewidth}{| l | X|}
repositories / tt2015.git / blobdiff