severinkaderli/bachelor-thesis
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

More work on thesis report

Browse source 
Signed-off-by: Severin Kaderli <severin@kaderli.dev>
This commit is contained in:
Severin Kaderli 2023-01-11 22:41:11 +01:00
parent 1168270444
commit bb50116cbe
Signed by: severinkaderli
GPG key ID: F419F8835B72F0C4
13 changed files with 179 additions and 131 deletions
Download patch file Download diff file Expand all files Collapse all files

12
documentation/thesis/content/06_testing.tex
View file

@ -2,8 +2,6 @@
\section{Devices}
The following devices were used for the development and testing of MagSend. While theoretically MagSend should work on other Laptops and Smartphones I have only tested in on specified devices. For each device the most important specifications are listed.
// TOOD: Explain problem of testing over video calls
\subsection{Laptop}
The laptop was used as the sending device for MagSend. The Website was run using the Firefox browser and the laptop was always plugged in to the power grid to ensure that CPU doesn't throttle.
@ -196,7 +194,7 @@ The following test cases are all structured in the same way. The table lists the
\item{The user can enter any text between 0 and 16 characters}
\end{enumerate} \\
Actual Result &
The user can enter any character in the input he wants but he is not able to enter more than 16 characters (see \autoref{figure:t07}).
The user can enter any character in the input they want but they are not able to enter more than 16 characters (see \autoref{figure:t07}).
\\
\end{reqTblr}
\caption{Test Case 07}
@ -223,9 +221,9 @@ The following test cases are all structured in the same way. The table lists the
\item{When the user hasn't entered any text or the text contains non-ASCII characters a fitting message is displayed and the sending process is not started.}
\end{enumerate} \\
Actual Result &
When the user attempts to start sending when he hasn't entered any text, a message is displayed (see \autoref{figure:t08}).
When the user attempts to start sending when they haven't entered any text, a message is displayed (see \autoref{figure:t08}).
When the user attempts to start sending when he has entered any non-ASCII characters, a message is diplayed. (see \autoref{figure:t08_2}).
When the user attempts to start sending when they have entered any non-ASCII characters, a message is diplayed. (see \autoref{figure:t08_2}).
In both cases the sending process is not started.
\\
@ -319,7 +317,7 @@ The following test cases are all structured in the same way. The table lists the
\item{The app will start the receive process and will indicate if the preamble was detected, the length of the received payload, and if the checksum is valid. The received text is also displayed.}
\end{enumerate} \\
Actual Result &
When the users starts the receiving process he is informed about the current process of the receive status. He is informed whether the preamble was detected, the length of the payload and if the checksum is valid. He can also see the currently received text at all times (see \autoref{figure:t11}).
When the users starts the receiving process they are informed about the current process of the receive status. They are informed whether the preamble was detected, the length of the payload and if the checksum is valid. They can also see the currently received text at all times (see \autoref{figure:t11}).
When the checksum is invalid the user is informed about it (see \autoref{figure:t11_2}).
\\
@ -427,4 +425,4 @@ The following test cases are all structured in the same way. The table lists the
\caption{Test Case 15}
\end{table}
// TODO: Fix up layout of images
// TODO: Fix up sizing of images