red ipv ref gefixed.

[tt2015.git] / a2 / 1cases.tex

diff --git a/a2/1cases.tex b/a2/1cases.tex
index ce1031d..d339dfa 100644 (file)
--- a/a2/1cases.tex
+++ b/a2/1cases.tex
@@ -82,8 +82,7 @@ results to asses whether or not the SUT has passed the test.
 
 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
 
 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. 
 
 To cover the TCP specification as complete as possible while still maintaining
 specification. 
 
 To cover the TCP specification as complete as possible while still maintaining


@@ -130,7 +129,22 @@ these partitions are given.
 \end{enumerate}
 
 These partitions were chosen since they correspond to key parts of the TCP
 \end{enumerate}
 
 These partitions were chosen since they correspond to key parts of the TCP

-specification. 
+specification. A single request consists of a number of packets that sent a
+to the \emph{echo-server} and back. The TCP specification state that such a
+transaction requires the following messages.
+
+\begin{center}
+       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{center}
+
+%
+% éé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
 
 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


@@ -260,7 +274,7 @@ 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
 \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{table:testpairs}. 
+described in Table~\ref{tbl:testpairs}. 

 
 \setcounter{TCC}{1}
 \begin{table}[H]
 
 \setcounter{TCC}{1}
 \begin{table}[H]


@@ -298,10 +312,9 @@ described in Table~\ref{table:testpairs}.
                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
                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

-       \hline

     \end{tabular}
 \caption{Expected results of test cases}
     \end{tabular}
 \caption{Expected results of test cases}

-\label{table:preflightresults}
+\label{tbl:testcases}

 \end{table}
 
 % Bij Ramons afwezigheid
 \end{table}
 
 % Bij Ramons afwezigheid