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

Correct thesis report

Browse source 
Signed-off-by: Severin Kaderli <severin@kaderli.dev>
This commit is contained in:
Severin Kaderli 2023-01-17 16:15:14 +01:00
parent 2f8b0b524a
commit 1862068f09
Signed by: severinkaderli
GPG key ID: F419F8835B72F0C4
10 changed files with 70 additions and 50 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -1,9 +1,9 @@
\chapter{Testing}
\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.
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 it on the specified devices. For each device, the most important specifications are listed.
\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.
The laptop was used as the sending device for MagSend. The Website was run on the Firefox browser. The laptop was always plugged in to the power grid to ensure that the CPU throttles less often.
\begin{table}[H]
\begin{reqTblr}{l p{11.0cm}}
@ -39,7 +39,7 @@ The following test cases are all structured in the same way. The table lists the
\begin{reqTblr}{l p{10.5cm}}
ID & T01 \\
Related Requirement & F01 \\
Description & The user is provided with the option to the start calibration on the website. \\
Description & The user is provided with the option to start the calibration on the website. \\
Expected Result &
\begin{enumerate}
\item{The user opens the website in a web browser}
@ -110,7 +110,7 @@ The following test cases are all structured in the same way. The table lists the
\item{The calibration is stopped, and the CPU should not be utilized anymore}
\end{enumerate} \\
Actual Result &
When the user clicks on the "Stop Calibration" button, the message about the calibration disappears and the button switches back to "Start Calibration" and the website should look like if it has just opened.
When the user clicks on the "Stop Calibration" button, the message about the calibration disappears and the button switches back to "Start Calibration". In the end, the website should look like if it has just opened.
After stopping the calibration, the CPU utilization also goes back down to normal levels (see \autoref{figure:t03_2}).
\\
@ -137,12 +137,20 @@ The following test cases are all structured in the same way. The table lists the
\item{The user is provided with a button to start the calibration}
\end{enumerate} \\
Actual Result &
Upon opening the app, the user is greeted with an option to start the calibration (see autoref{figure:t04}).
Upon opening the app, the user is greeted with an option to start the calibration (see \autoref{figure:t04}).
\\
\end{reqTblr}
\caption{Test Case 04}
\end{table}
\begin{figure}[H]
\centering
\fbox{\includegraphics[width=0.4\linewidth]{test_cases/t4.jpg}}
\caption{Test Case 04 - Home Screen in the App}
\label{figure:t04}
\end{figure}
\begin{table}[H]
\begin{reqTblr}{l p{10.5cm}}
ID & T05 \\
@ -152,10 +160,10 @@ The following test cases are all structured in the same way. The table lists the
\begin{enumerate}
\item{The user opens the app}
\item{The user clicks on the "Calibrate" button}
\item{The user is shown the current measured magnetic field strength as well as a chart of the historical values}
\item{The user is shown the current measured magnetic flux density as well as a chart of the historical values}
\end{enumerate} \\
Actual Result &
After starting the calibration in the app, the user can see the magnetic field strength and historical data in a chart. (see autoref{figure:t05}).
After starting the calibration in the app, the user can see the magnetic flux density and historical data in a chart. (see \autoref{figure:t05}).
\\
\end{reqTblr}
\caption{Test Case 05}
@ -196,10 +204,10 @@ The following test cases are all structured in the same way. The table lists the
\begin{enumerate}
\item{The user opens the website in a web browser}
\item{The user clicks into the text input}
\item{The user can enter any text between 0 and 16 characters}
\item{The user can enter any text between 0 and 16 characters in length}
\end{enumerate} \\
Actual Result &
The user can enter any character in the input they want, but they unable to enter more than 16 characters (see \autoref{figure:t07}).
The user can enter any character in the input they want, but they are unable to enter more than 16 characters (see \autoref{figure:t07}).
\\
\end{reqTblr}
\caption{Test Case 07}
@ -228,7 +236,7 @@ The following test cases are all structured in the same way. The table lists the
Actual Result &
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 they have entered any non-ASCII characters, a message is diplayed. (see \autoref{figure:t08_2}).
A message also appears, when the user attempts to start sending when they have entered any non-ASCII characters (see \autoref{figure:t08_2}).
In both cases, the sending process is not started.
\\
@ -298,7 +306,7 @@ The following test cases are all structured in the same way. The table lists the
\item{The sending is stopped, and the CPU should not be utilized anymore}
\end{enumerate} \\
Actual Result &
When the user clicks on the "Stop Sending" button, the message about the sending disappears and the button switches back to "Start Sending" and the website should look like if it has just been opened.
When the user clicks on the "Stop Sending" button, the message about the sending disappears and the button switches back to "Start Sending". In the end, the website should look like if it has just opened.
After stopping the sending, the CPU utilization also goes back down to normal levels (see \autoref{figure:t10}).
\\
@ -327,7 +335,7 @@ The following test cases are all structured in the same way. The table lists the
\item{The app will start the reception 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 reception 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 users starts the reception process they are informed about the current process of the receive status. They are informed whether the preamble was detected, about 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}).
\\
@ -339,13 +347,13 @@ The following test cases are all structured in the same way. The table lists the
\begin{minipage}{.5\textwidth}
\centering
\fbox{\includegraphics[width=0.8\linewidth]{test_cases/t11.jpg}}
\caption{Test Case 11 - Reception Process without any Errors}
\caption{Test Case 11 - Reception Process\\ without any Errors}
\label{figure:t11}
\end{minipage}
\begin{minipage}{.5\textwidth}
\centering
\fbox{\includegraphics[width=0.8\linewidth]{test_cases/t11_2.jpg}}
\caption{Test Case 11 - Reception Process with Invalid Checksum}
\caption{Test Case 11 - Reception Process\\ with Invalid Checksum}
\label{figure:t11_2}
\end{minipage}
\end{figure}
@ -434,8 +442,7 @@ The following test cases are all structured in the same way. The table lists the
\item{The transfer speed between laptop and smartphone should at least be \SI{1}{\bit\per\second}}
\end{enumerate} \\
Actual Result &
The clock speed of the transmitted signal is 500ms. As the MagSend payload is encoded using a manchester code, which doubles the data size, this means every second 1 bit gets transmitted. For more information about data rate benchmarks, please refer to \autoref{chapter:benchmarking}.
\\
The clock speed of the transmitted signal is 500ms. The MagSend payload is encoded using a manchester code, which doubles the data size. This means every second 1 bit gets transmitted. For more information about data rate benchmarks, please refer to \autoref{chapter:benchmarking}.
\end{reqTblr}
\caption{Test Case 15}
\end{table}