these partitions are given.
\begin{enumerate}
- \item Single valid request.
- \item Single invalid request with.
- \begin{enumerate}
- \item Corrupted checksum.
- \item Corrupted payload with.
+ \item \emph{Number of packets} in request\footnotemark
+ \footnotetext{A request is considered establishing a connection
+ (handshake) and any n number of payloadpackts}
\begin{enumerate}
- \item Oven number of bits flipped.
- \item Odd number of bits flipped.
+ \item 0 payload packets
+ \item 1 payload packet
+ \item n=small payload packets
+ \item n=big payload packets
\end{enumerate}
- \item Corrupted source address.
- \item Corrupted destination address.
- \end{enumerate}
- \item Multiple valid requests received in order.
- \item Multiple valid requests received out of order.
- \item Mixed valid and invalid requests with.
- \begin{enumerate}
- \item Missing packets.
- \item Corrupted checksum.
- \item Corrupted payload with.
+ \item Correct or Incorrect \emph{source port}
+ \item Correct or Incorrect \emph{Destination port}
+ \item Bits flipped in \emph{Payload}
\begin{enumerate}
- \item Oven number of bits flipped.
- \item Odd number of bits flipped.
+ \item Correct payload
+ \item Payload with even number of bits flipped
+ \item Payload with odd number of bits flipped
\end{enumerate}
- \item Corrupted source address.
- \item Corrupted destination address.
- \end{enumerate}
+ \item Correct or Incorrect \emph{checksum}
+ \item Packets received in or out of order, or missing packets
\end{enumerate}
-Above enumeration results in a total of $14$ test cases.
+\textbf{hier iets over waarom deze partities relevant zijn!}
-\vspace{3mm}
-\textbf{Hier daadwerkelijke test cases tabel}
-\vspace{3mm}
+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.
-To reduce the number of tests that need to be executed when testing the SUT and
-to construct a feasible test suite these tests are combined according
-to Table~(\textbf{referentie naar decision table}).
+This is expressed in the table below.
\vspace{3mm}
\textbf{Hier daadwerkelijke decision tabel}
\subsection{Quality, completeness and coverage of tests}
-\subsubsection{Quality}
The network packets used in testing are constructed from prerecorded, known to
be correct, network traffic. These packets are then modified with well used and
field tested tools. Due to this the chance of errors in the test cases is quite
there is a fault in the SUT and can not result directly in the conclusion that
there actually is one.
-\subsubsection{Coverage}
+\bigskip
+
Due to the nature of black-box testing coverage of the code in the
implementation of the SUT is unknown. However completeness of the tests over
the specification of the SUT can be assessed.
-\subsubsection{Completeness}
+\bigskip
+
Due to the clear and exhaustive specification of TCP the completeness of the
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 which covers at least \textbf{percentage}\% of the
-specification.
+to ensure a test suite.
To further decrease the number of tests needed test cases are divided into
equivalence partitions and the combination of cases as described in
Table~(\textbf{referentie naar decision table}) ensures that all partitions are
covered and the number of individual tests is still feasible.
+
+ %
+ % wat ik ook probeer ik krijg de eerste collum
+ % zijn tekst niet verticaal gecentered
+ %
+ \begin{table}
+
+
+ \subsection{Test cases}
+
+ \begin{tabularx}{\linewidth}{| l | X|}
+ \hline
+ Nr & 1 \\\hline
+ Title & Single valid request. \\\hline
+ Input & Pcap file with prerecorded valid packets. \\\hline
+ Expected output & Pcap file with valid response to request. \\\hline
+ Course of action & \begin{enumerate}
+ \item Load input pcap file.
+ \item Replay pcap file using ...
+ \item Record SUT response using...
+ \item Save recorded packets as a pcap file.
+ \item Analyze packets in resulting file.
+ \end{enumerate} \\\hline
+ Valid trace & \begin{enumerate}
+ \item \textbf{Hier packets benoemen?}
+ \end{enumerate} \\\hline
+ \end{tabularx}
+
+ \begin{tabularx}{\linewidth}{| l | X|}
+ \hline
+ Nr & 2 \\\hline
+ Title & Single request with corrupted checksum. \\\hline
+ Input & Pcap file used as \emph{test-case 1} input. \\\hline
+ Expected output & No response from SUT, logs with rejected packets. \\\hline
+ Course of action & \begin{enumerate}
+ \item Load input pcap file into ....
+ \item Corrupt checksum of loaded packets.
+ \item Save resulting packets as pcap file.
+ \item Load new pcap file into ...
+ \item Replay new pcap file.
+ \item Record SUT response using...
+ \item Extract log with rejected packets.
+ \item Save recorded packets as a pcap file.
+ \item Analyze packets in resulting file.
+ \end{enumerate} \\\hline
+ Valid trace & \begin{enumerate}
+ \item \textbf{Aangeven welke packets corrupted zijn?}
+ \end{enumerate} \\\hline
+ \end{tabularx}
+ \end{table}
+
+ \newpage
repositories / tt2015.git / commitdiff