a2/1manual.tex

   1 \subsection{Preflight checklist}
   2
   3 Before actual certification is commenced we perform a manual test using a
   4 checklist.
   5 If any of the checks fail we immediately reject the product.
   6
   7 \begin{enumerate}
   8         \item Is the product complete?
   9         \item Does the product come with a manual or quick start guide?
  10         \item Is it possible to get the product in a usable state?
  11         \item Can we use the product to initiate a connection in a corruption
  12         free
  13         environment?
  14 \end{enumerate}
  15
  16 \textbf{DIT MOET VERANDERD WORDEN, HET PRODUCT ZOU AFGEKEURD WORDEN!}
  17
  18 \subsection{Manual testing of SUT}
  19
  20 The following requests are taken into considering while constructing test cases.
  21
  22 \begin{enumerate}
  23         \item Single valid request.
  24         \item Single invalid request with.
  25         \begin{enumerate}
  26                 \item Corrupted checksum.
  27                 \item Corrupted payload with.
  28                 \begin{enumerate}
  29                         \item Oven number of bits flipped.
  30                         \item Odd number of bits flipped.
  31                 \end{enumerate}
  32                 \item Corrupted source address.
  33                 \item Corrupted destination address.
  34         \end{enumerate}
  35         \item Multiple valid requests received in order.
  36         \item Multiple valid requests received out of order.
  37         \item Mixed valid and invalid requests with.
  38         \begin{enumerate}
  39                 \item Missing packets.
  40                 \item Corrupted checksum.
  41                 \item Corrupted payload with.
  42                 \begin{enumerate}
  43                         \item Oven number of bits flipped.
  44                         \item Odd number of bits flipped.
  45                 \end{enumerate}
  46                 \item Corrupted source address.
  47                 \item Corrupted destination address.
  48         \end{enumerate}
  49 \end{enumerate}
  50
  51 Above enumeration results in a total of $14$ test cases.
  52
  53 \subsection{Quality, completeness and coverage of tests}
  54
  55 \subsubsection{Quality}
  56 The network packets used in testing are constructed from prerecorded, known to
  57 be correct, network traffic. These packets are then modified with well used and
  58 field tested tools. Due to this the chance of errors in the test cases is quite
  59 low. However, no formal proof of correctness of the test cases is present, this
  60 means that any defects found might not be the result of a fault in the SUT.
  61 Therefore detected defects should only indicate there is a high chance that
  62 there is a fault in the SUT and can not result directly in the conclusion that
  63 there actually is one.
  64
  65 \subsubsection{Coverage}
  66 Due to the nature of black-box testing coverage of the code in the
  67 implementation of the SUT is unknown. However completeness of the tests over
  68 the specification of the SUT can be assessed.
  69
  70 \subsubsection{Completeness}
  71 Due to the clear and exhaustive specification of TCP the completeness of the
  72 test suite can be clearly assessed (\textit{lijkt me dan... Misschien ook juist
  73 complexer?}).
  74
  75 As always, $100\%$ completeness is not feasible, therefore test cases are
  76 carefully selected to ensure a test suite which is as complete as feasible.
  77 To achieve this the test cases are divided into equivalence partitions and
  78 (\textbf{referentie naar descision table}) ensures that all partitions are
  79 covered. However, since it is not feasible to test all possible conditions on
  80 it's own, conditions are tested in groups.
  81
  82 \textit{nu iets met meten van coverage, hier kan ik geen document over vinden zo}
  83
  84