a2/1cases.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 environment?
  13 \end{enumerate}
  14
  15 \textbf{DIT MOET VERANDERD WORDEN, HET PRODUCT ZOU AFGEKEURD WORDEN!}
  16
  17 \subsection{Testing of SUT}
  18
  19 The SUT is a series of services for other computer programs with no end-user
  20 facing
  21 interface. Therefore the SUT will be tested solely by calling it's services
  22 through various automated scripts. An automated test suite will be available
  23 which executes all these automated scripts and aggregates their results to
  24 asses whether or not the SUT has passed the test.
  25
  26 The implementation of the SUT is tested using black box testing techniques. A
  27 series of tests asses the correctness of the implementation with regards to the
  28 TCP specification. These tests are specified in Table~\textbf{referentie naar
  29 tests-tabel}. The test cases aim to cover the most interesting parts of the
  30 TCP specification.
  31
  32 To cover the TCP specification as complete as possible while still maintaining
  33 a feasible test suite the tests are divided into equivalence partitions. Below
  34 these partitions are given.
  35
  36 \begin{enumerate}
  37         \item Single valid request.
  38         \item Single invalid request with.
  39         \begin{enumerate}
  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         \item Multiple valid requests received in order.
  50         \item Multiple valid requests received out of order.
  51         \item Mixed valid and invalid requests with.
  52         \begin{enumerate}
  53                 \item Missing packets.
  54                 \item Corrupted checksum.
  55                 \item Corrupted payload with.
  56                 \begin{enumerate}
  57                         \item Oven number of bits flipped.
  58                         \item Odd number of bits flipped.
  59                 \end{enumerate}
  60                 \item Corrupted source address.
  61                 \item Corrupted destination address.
  62         \end{enumerate}
  63 \end{enumerate}
  64
  65 Above enumeration results in a total of $14$ test cases.
  66
  67 \vspace{3mm}
  68 \textbf{Hier daadwerkelijke test cases tabel}
  69 \vspace{3mm}
  70
  71 To reduce the number of tests that need to be executed when testing the SUT and
  72 to construct a feasible test suite these tests are combined according
  73 to Table~(\textbf{referentie naar decision table}).
  74
  75 \vspace{3mm}
  76 \textbf{Hier daadwerkelijke decision tabel}
  77 \vspace{3mm}
  78
  79 \subsection{Quality, completeness and coverage of tests}
  80
  81 \subsubsection{Quality}
  82 The network packets used in testing are constructed from prerecorded, known to
  83 be correct, network traffic. These packets are then modified with well used and
  84 field tested tools. Due to this the chance of errors in the test cases is quite
  85 low. However, no formal proof of correctness of the test cases is present, this
  86 means that any defects found might not be the result of a fault in the SUT.
  87 Therefore detected defects should only indicate there is a high chance that
  88 there is a fault in the SUT and can not result directly in the conclusion that
  89 there actually is one.
  90
  91 \subsubsection{Coverage}
  92 Due to the nature of black-box testing coverage of the code in the
  93 implementation of the SUT is unknown. However completeness of the tests over
  94 the specification of the SUT can be assessed.
  95
  96 \subsubsection{Completeness}
  97 Due to the clear and exhaustive specification of TCP the completeness of the
  98 test suite can be clearly assessed.
  99
 100 As always, $100\%$ completeness is not feasible, therefore test cases are
 101 carefully selected to cover the most interesting parts of the TCP specification
 102 to ensure a test suite which covers at least \textbf{percentage}\% of the
 103 specification.
 104
 105 To further decrease the number of tests needed test cases are divided into
 106 equivalence partitions and the combination of cases as described in
 107 Table~(\textbf{referentie naar decision table}) ensures that all partitions are
 108 covered and the number of individual tests is still feasible.
 109