Added framework for report
authorpimjager <pim@pimjager.nl>
Wed, 16 Dec 2015 14:58:32 +0000 (15:58 +0100)
committerpimjager <pim@pimjager.nl>
Wed, 16 Dec 2015 14:58:32 +0000 (15:58 +0100)
a3/1modelingTCP.tex [moved from a3/1modelinvestigation.tex with 97% similarity]
a3/2tools.tex [new file with mode: 0644]
a3/3architecture.tex [new file with mode: 0644]
a3/4tests.tex [new file with mode: 0644]
a3/5discussion.tex [new file with mode: 0644]
a3/Makefile [new file with mode: 0644]
a3/preamble.tex [new file with mode: 0644]
a3/tt3.bib [new file with mode: 0644]
a3/tt3.tex [new file with mode: 0644]

similarity index 97%
rename from a3/1modelinvestigation.tex
rename to a3/1modelingTCP.tex
index f0f6718..6449dcc 100644 (file)
@@ -1,4 +1,3 @@
-\section{Modeling TCP}
 In previous assignments our group has viewed the SUT as a stateful input-output
 system. 
 
diff --git a/a3/2tools.tex b/a3/2tools.tex
new file mode 100644 (file)
index 0000000..eaf6fbb
--- /dev/null
@@ -0,0 +1,5 @@
+% Possible tools and which ones did we chose:
+
+% Search for model-based testing tools, select two MBT tools, and 
+% argue why you selected these
+% tools. (See also the list of MBT tools below.)
\ No newline at end of file
diff --git a/a3/3architecture.tex b/a3/3architecture.tex
new file mode 100644 (file)
index 0000000..9ebbecf
--- /dev/null
@@ -0,0 +1,9 @@
+% the test architecture.
+
+% Develop a test environment or test architecture which will be used 
+% for model-based testing of your SUT. Give a sketch of the test 
+% architecture, i.e., the positioning of the SUT, test tool(s), 
+% adapter(s), logging tool(s), ..., and their connections and 
+% interfaces; explain your choices. Try to reuse (parts of) the 
+% test-execution automation environment that you developed during the 
+% second assignment.
diff --git a/a3/4tests.tex b/a3/4tests.tex
new file mode 100644 (file)
index 0000000..6c5269c
--- /dev/null
@@ -0,0 +1,5 @@
+% testcases, results and discussion on results:
+
+% Write your model in the input language of the selected MBT tools, generate
+%  tests, and execute
+% them on your SUT. Explain your observations and analyse the test results.
\ No newline at end of file
diff --git a/a3/5discussion.tex b/a3/5discussion.tex
new file mode 100644 (file)
index 0000000..4faa6f2
--- /dev/null
@@ -0,0 +1,11 @@
+% Comparison between tools and how fit the tools we choose were
+
+% Discuss and classify the MBT tools that you used, compare them, compare with 
+% Manual testing, and reflect on the theory:
+% • What is implementation relation?
+% • Is there support for non-determinism, concurrency?
+% • Are the generated tests sound, exhaustive? Why do you think so? 
+% • Which method of test test selection is used?
+% • What is the modeling notation, its expressiveness, and ease of use? 
+% • Do the tools use on/off-line testing (on-the-fly/batch)?
+% • Do they support both: test input generation and output checking?
\ No newline at end of file
diff --git a/a3/Makefile b/a3/Makefile
new file mode 100644 (file)
index 0000000..2615255
--- /dev/null
@@ -0,0 +1,23 @@
+LATEX:=latex
+
+DOCUMENT:=tt3
+SOURCES:=$(filter-out preamble.tex,$(shell ls *.tex))
+
+.SECONDARY: $(addsuffix .fmt,$(DOCUMENT))
+.PHONY: clean
+
+all: $(DOCUMENT).pdf
+
+%.pdf: %.dvi
+       dvipdfm $<
+
+%.dvi: %.tex %.fmt $(SOURCES)
+       $(LATEX) $(basename $@)
+       $(LATEX) $(basename $@)
+       $(LATEX) $(basename $@)
+
+%.fmt: preamble.tex
+       $(LATEX) -ini -jobname="$(basename $@)" "&$(LATEX) $<\dump"
+
+clean:
+       $(RM) -v $(addprefix $(DOCUMENT).,fmt aux bbl blg dvi log out toc pdf)
diff --git a/a3/preamble.tex b/a3/preamble.tex
new file mode 100644 (file)
index 0000000..36f5fb9
--- /dev/null
@@ -0,0 +1,31 @@
+\documentclass[titlepage]{article}
+
+\usepackage{a4wide}
+\usepackage[dvipdfm]{hyperref}
+\usepackage{listings}
+\usepackage{graphicx}
+\usepackage{multirow}
+\usepackage{float}
+\usepackage{tabu}
+\usepackage{tabularx}
+\usepackage{longtable}
+\usepackage{amsfonts}
+\newcommand{\xmark}{\texttt{\textbf{x}}}
+
+\newcounter{TCC}
+\newcommand{\doTCC}{\theTCC \stepcounter{TCC}}
+
+\lstset{%
+  breakatwhitespace=false,         % sets if automatic breaks should only happen at whitespace
+  breaklines=true,                 % sets automatic line breaking
+  frame=single,                           % adds a frame around the code
+  tabsize=4
+}
+
+\author{%
+       Charlie Gerhardus\and
+       Pim Jager\and
+       Mart Lubbers
+}
+\title{Model based testing of TCP} 
+\date{\today}
diff --git a/a3/tt3.bib b/a3/tt3.bib
new file mode 100644 (file)
index 0000000..2a937c4
--- /dev/null
@@ -0,0 +1,61 @@
+@incollection{pol1997,
+       title = {A {Test} {Management} approach for structured testing},
+       booktitle = {Achieving {Software} {Product} {Quality}},
+       publisher = {UTN publishers},
+       author = {Pol, M. and van Veenendaal, Erik},
+       editor = {van Veenendaal, Erik and McMullen, Julie},
+       year = {1997},
+}
+
+@misc{muller2011,
+       title = {Certified {Tester}. {Foundation} {Level} {Syllabus}},
+       author = {Müller, Thomas},
+       editor = {Friedenberg, Debra},
+       year = {2011},
+}
+
+@book{iso9126,
+       title = {{ISO}/{IEC} 9126. {Software} engineering – {Product} quality},
+       publisher = {ISO/IEC},
+       author = {{ISO/IEC}},
+       year = {2001}
+}
+
+@book{iso25010,
+       title = {{ISO}/{IEC} 25010:2011. {Systems} and software engineering -- {Systems} and software {Quality} {Requirements} and {Evaluation} ({SQuaRE}) -- {System} and software quality models.},
+       publisher = {ISO/IEC},
+       author = {{ISO/IEC}},
+       year = {2011}
+}
+
+@misc{veenendaal2012,
+       title = {Standard glossary of terms used in {Software} {Testing}},
+       editor = {van Veenendaal, Erik van},
+       year = {2012},
+}
+
+@book{rfc793,
+       series = {Request for {Comments}},
+       title = {Transmission {Control} {Protocol}},
+       url = {http://www.ietf.org/rfc/rfc793.txt},
+       number = {793},
+       publisher = {IETF},
+       author = {Postel, J.},
+       month = sep,
+       year = {1981},
+       note = {Published: RFC 793 (INTERNET STANDARD)
+Updated by RFCs 1122, 3168, 6093, 6528},
+}
+
+@article{whittaker2000,
+       title = {What is software testing? {And} why is it so hard?},
+       volume = {17},
+       shorttitle = {What is software testing?},
+       url = {http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=819971},
+       number = {1},
+       urldate = {2015-09-20},
+       journal = {Software, IEEE},
+       author = {Whittaker, James},
+       year = {2000},
+       pages = {70--79},
+}
diff --git a/a3/tt3.tex b/a3/tt3.tex
new file mode 100644 (file)
index 0000000..847fa47
--- /dev/null
@@ -0,0 +1,25 @@
+%&tt3
+\begin{document}
+\maketitle
+\tableofcontents
+\newpage
+
+\section{Modeling TCP}
+\input{1modelingTCP.tex}
+
+\section{Tools}
+\input{2tools.tex}
+
+\section{Test Architecture}
+\input{3architecture.tex}
+
+\section{Tests}
+\input{4tests.tex}
+
+\section{Discussion}
+\input{5discussion.tex}
+
+%\nocite{*} %% weghalen bij daadwerkelijke cite
+%\bibliographystyle{plain}
+%\bibliography{tt2}
+\end{document}