From 9ed3b998ef62b6b1020b523bdfb9a3887598a9b0 Mon Sep 17 00:00:00 2001 From: pimjager Date: Sun, 15 Nov 2015 20:35:03 +0100 Subject: [PATCH] Added passing grade to report and removed discussion on randomisation --- a2/1cases.tex | 12 +++++------ a2/2results.tex | 56 ++++++++++++++++++++++--------------------------- 2 files changed, 31 insertions(+), 37 deletions(-) diff --git a/a2/1cases.tex b/a2/1cases.tex index d30a937..b0531b2 100644 --- a/a2/1cases.tex +++ b/a2/1cases.tex @@ -257,12 +257,12 @@ As always, $100\%$ completeness is not feasible, therefore test cases are carefully selected to cover the most interesting parts of the TCP specification to ensure a complete but feasible test suite. -To further increase the coverage of the test suites tests are randomized. The -tests which test the handling of \emph{bit errors}, changes in the \emph{segment -order} and \emph{dropped segments} randomize where they introduce an error. The -test suite runs these tests multiple times to increase the likelihood that they -discover a fault which is only present when an error occurs in a certain -position. +%To further increase the coverage of the test suites tests are randomized. The +%tests which test the handling of \emph{bit errors}, changes in the \emph{segment +%order} and \emph{dropped segments} randomize where they introduce an error. The +%test suite runs these tests multiple times to increase the likelihood that they +%discover a fault which is only present when an error occurs in a certain +%position. To further decrease the number of tests needed test cases are divided into equivalence partitions and the combination of cases as described in diff --git a/a2/2results.tex b/a2/2results.tex index eaa1731..cfde7c7 100644 --- a/a2/2results.tex +++ b/a2/2results.tex @@ -8,11 +8,11 @@ following results: \begin{tabular}{|l|l|} \hline Check \# & result \\ \hline \hline - 1 & RESULT\\ \hline - 2 & RESULT\\ \hline - 3 & RESULT\\ \hline - 4 & RESULT\\ \hline - 5 & RESULT\\ \hline + 1 & Passed\\ \hline + 2 & Passed\\ \hline + 3 & Passed\\ \hline + 4 & Passed\\ \hline + 5 & Passed\\ \hline \end{tabular} \caption{Results of the preflight checks} \label{tbl:preflightresults} @@ -29,30 +29,24 @@ Table~\ref{tbl:testcases} yields the following results: \begin{tabular}{|l|l|} \hline Test case \# & result \\ \hline \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline - \doTCC & RESULT\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline + \doTCC & Passed\\ \hline \end{tabular} \caption{Results of the test cases} \label{tbl:testcasesresults} @@ -60,10 +54,10 @@ Table~\ref{tbl:testcases} yields the following results: \subsection{Result} To pass the test the SUT has to pass all the specified test cases ( -Table~\ref{tbl:tpreflight} and Table~\ref{tbl:testpairs}). As can be seen in +Table~\ref{tbl:preflight} and Table~\ref{tbl:testpairs}). As can be seen in Table~\ref{tbl:preflightresults} and Table~\ref{tbl:testcasesresults} this is %not %remove first % in case of any failure -the case. Therefore the SUT has PASSED/FAILED this test. +the case. Therefore the SUT has Passed this test suite. %This failure is due to the failure of the test case(s) 1,2,3,n as specified %where the SUT failed to behave in the expected way by... %behavior dat SUT wel %%liet zien -- 2.20.1