update met figuur en paar spelfouten/stijldingen eruit

[tt2015.git] / 3eval.tex

diff --git a/3eval.tex b/3eval.tex
old mode 100644 (file)
new mode 100755 (executable)
index 76da37c..19a1441
--- a/3eval.tex
+++ b/3eval.tex
@@ -1,6 +1,34 @@
-Hello world
-%13
-%14
-%15
+\subsection{Exit criteria}
+\label{sec:exitcriteria}
+The testing will be complete and the SUT will pass if and only if all the
+functionality tests are a success. Functionality tests are very important since
+the SUT has to adhere to a specification of a computer-to-computer protocol and
+therefore the impact of a defect in the system is very high.
+
+Other exit criteria are schedule deadline and cost limits. When these limits
+are reached the testing will terminate but there is no confidence in the
+quality of the product.
+
+\subsection{Test ware}
+
+\subsection{Issue tracking}
+Whenever an issue is detected (a test fails) this issue needs to be recorded
+such that this incident is added to the test report. It can then be determined
+if the incident was the result of a fault in the SUT or was caused by something
+else, e.g. an error in the test.
+
+The record of a incident needs to hold all relevant data such that the incident
+can easily be reproduced later. Therefore each incident will be recorded in an
+incident report, which will include the following details:
+\begin{itemize}
+       \item When the issue was detected and by whom.
+       \item Which test detected the issue.
+       \item Expected results.
+       \item Actual Results.
+       \item Relevant logs, screenshots or other data which is needed in
+                       addition to the test itself to reproduce the incident and which
+                       might be beneficial to it's resolution.
+       \item Other areas of the SUT which might be affected by the incident or by
+                       a change resulting from the incident.
+\end{itemize} 
 
-\label{sec:exitcriteria}
\ No newline at end of file