a3/2tools.tex

   1 % Possible tools and which ones did we chose:
   2
   3 % Search for model-based testing tools, select two MBT tools, and
   4 % argue why you selected these
   5 % tools. (See also the list of MBT tools below.)
   6
   7 To test the SUT using the model from Section~\ref{sec:modeling} we have
   8 considered two tools, namely \GAST and JTorx. The sections below discuss the
   9 upsides and downsides of these tools in regard to testing the SUT.
  10
  11 \subsection{JTorX}
  12 JTorX is an open source model based test tool developed by
  13 Belinfante\cite{belinfante2010jtorx} featuring a GUI, all possible graph file
  14 formats and can connect to the SUT via TCP or stdin/stdout. JTorX generates
  15 input enabled traces and automatically executes them via the adapter. In our
  16 setup we use TCP as the desired communication method between the SUT and the
  17 tool.
  18
  19 \subsection{\GAST}
  20 \GAST is an open source model based test tool developed by Koopman et
  21 al.\cite{koopman2003gast} and is a domain specific language written in the
  22 functional programming language Clean. Models in \GAST must be expressed as
  23 functions. \GAST supports two different types of testing. Standard model
  24 checking and property based testing. As discussed earlier we are not using
  25 property based testing. \GAST can communicate with the SUT via TCP or embedded
  26 C code. In our setup we use TCP as the desired communication method between the
  27 SUT and the tool. In order to enable \GAST to communicate with our adapter
  28 (written in Python)
  29 we needed to slightly modify the \GAST source. The modified source is provided
  30 with this report.
  31
  32 % Misschien hier iets over het feit dat we TCP gebruiken als communicatie