From: pimjager Date: Wed, 11 Nov 2015 15:17:28 +0000 (+0100) Subject: Merge branch 'master' of https://github.com/dopefishh/tt2015 X-Git-Url: https://git.martlubbers.net/?a=commitdiff_plain;h=a6c16f39d7bf9111a19da3020ae4c94739768f89;hp=-c;p=tt2015.git Merge branch 'master' of https://github.com/dopefishh/tt2015 --- a6c16f39d7bf9111a19da3020ae4c94739768f89 diff --combined a2/1cases.tex index 403e4d7,79da29d..21048a1 --- a/a2/1cases.tex +++ b/a2/1cases.tex @@@ -95,8 -95,8 +95,8 @@@ these partitions are given \begin{enumerate} \item 0 payload segments \item 1 payload segments - \item n=small payload segments - \item n=big payload segments + \item n=small payload segments (1 byte) + \item n=big payload segments (65495 bytes) \end{enumerate} \item \emph{source port} \begin{enumerate} @@@ -119,11 -119,11 +119,11 @@@ \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} @@@ -161,35 -161,29 +161,35 @@@ Partitions 2 to 6 are tested using pair 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{table: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} \caption{Combinations of test cases} @@@ -220,14 -214,7 +220,14 @@@ test suite can be clearly assessed 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 @@@ -243,7 -230,69 +243,69 @@@ covered and the number of individual te \subsection{Test cases} - %\begin{table} + Before every test case use the following steps to initialize the testing environment. + + \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} + \end{enumerate} + + \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 + \end{longtable} + %\begin{tabularx}{\linewidth}{| l | X|} %\hline %Nr & 1 \\\hline