\subsection{Preflight checklist}
-Before actual certification is commenced we perform a manual test using a 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}
\end{enumerate}
Above enumeration results in a total of $14$ test cases.
+
+\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 (\textit{lijkt me dan... Misschien ook juist
+complexer?}).
+
+As always, $100\%$ completeness is not feasible, therefore test cases are
+carefully selected to ensure a test suite which is as complete as feasible.
+To achieve this the test cases are divided into equivalence partitions and
+(\textbf{referentie naar descision table}) ensures that all partitions are
+covered. However, since it is not feasible to test all possible conditions on
+it's own, conditions are tested in groups.
+
+\textit{nu iets met meten van coverage, hier kan ik geen document over vinden zo}
+
+