\subsection{Preflight checklist}

Before actual certification is commenced we perform a manual test using a 
checklist.
If any of the checks fail we immediately reject the product.

\begin{enumerate}
	\item Is the product complete?
	\item Does the product come with a manual or quick start guide?
	\item Is it possible to get the product in a usable state?
	\item Can we use the product to initiate a connection in a corruption
	free environment?
\end{enumerate}

\textbf{DIT MOET VERANDERD WORDEN, HET PRODUCT ZOU AFGEKEURD WORDEN!}

\subsection{Testing of SUT}

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 available
which executes all these automated scripts and aggregates their 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
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 specification. 

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.

\begin{enumerate}
	\item Single valid request.
	\item Single invalid request with.
	\begin{enumerate}
		\item Corrupted checksum.
		\item Corrupted payload with.
		\begin{enumerate}
			\item Oven number of bits flipped.
			\item Odd number of bits flipped.
		\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.
		\begin{enumerate}
			\item Oven number of bits flipped.
			\item Odd number of bits flipped.
		\end{enumerate}
		\item Corrupted source address.
		\item Corrupted destination address.
	\end{enumerate}
\end{enumerate}

Above enumeration results in a total of $14$ test cases.

\vspace{3mm}
\textbf{Hier daadwerkelijke test cases tabel}
\vspace{3mm}

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}). 

\vspace{3mm}
\textbf{Hier daadwerkelijke decision tabel}
\vspace{3mm}

\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
low. However, no formal proof of correctness of the test cases is present, this
means that any defects found might not be the result of a fault in the SUT.
Therefore detected defects should only indicate there is a high chance that 
there is a fault in the SUT and can not result directly in the conclusion that
there actually is one. 

\subsubsection{Coverage}
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}
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 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. 

