Finalize thesis report
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
Signed-off-by: Severin Kaderli <severin@kaderli.dev>
This commit is contained in:
parent
1862068f09
commit
8fef45b856
10 changed files with 5991 additions and 55 deletions
|
@ -6,7 +6,7 @@ The following devices were used for the development and testing of MagSend. Whil
|
|||
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}}
|
||||
\begin{reqTblr}{l p{10.9cm}}
|
||||
Device & Lenovo Thinkpad T470P \\
|
||||
Operating System & Arch Linux \\
|
||||
CPU & Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz \\
|
||||
|
@ -21,7 +21,7 @@ The laptop was used as the sending device for MagSend. The Website was run on th
|
|||
The smartphone was used as the receiving device for MagSend. The app was run normally as a native Android application.
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{11.0cm}}
|
||||
\begin{reqTblr}{l p{10.9cm}}
|
||||
Device & Samsung Galaxy S9+ \\
|
||||
Operating System & Android 10 with One UI 2.5 \\
|
||||
SoC & Samsung Exynos 9810 \\
|
||||
|
@ -36,7 +36,7 @@ The smartphone was used as the receiving device for MagSend. The app was run nor
|
|||
The following test cases are all structured in the same way. The table lists the related requirements from \autoref{chapter:requirements} and describes the test case briefly. Then the expected result row lists the steps and the result that should happen for the test case to be successful. The last row describes the actual result from testing.
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T01 \\
|
||||
Related Requirement & F01 \\
|
||||
Description & The user is provided with the option to start the calibration on the website. \\
|
||||
|
@ -61,7 +61,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T02 \\
|
||||
Related Requirement & F01 \\
|
||||
Description & The user can start the calibration process on the website.\\
|
||||
|
@ -98,7 +98,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T03 \\
|
||||
Related Requirement & F01 \\
|
||||
Description & The user can stop the calibration process on the website.\\
|
||||
|
@ -127,7 +127,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T04 \\
|
||||
Related Requirement & F02 \\
|
||||
Description & The user is provided with the option to start calibration in the app.\\
|
||||
|
@ -152,7 +152,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T05 \\
|
||||
Related Requirement & F02 \\
|
||||
Description & The user can start the calibration process in the app.\\
|
||||
|
@ -177,7 +177,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
\end{figure}
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T06 \\
|
||||
Related Requirement & F02 \\
|
||||
Description & The user can stop the calibration process in the app.\\
|
||||
|
@ -196,7 +196,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
\end{table}
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T07 \\
|
||||
Related Requirement & F03 \\
|
||||
Description & The user can enter text on the website.\\
|
||||
|
@ -221,7 +221,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
\end{figure}
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T08 \\
|
||||
Related Requirement & F04 \\
|
||||
Description & The entered text is validated on the website when sending.\\
|
||||
|
@ -259,7 +259,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
\end{figure}
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T09 \\
|
||||
Related Requirement & F04 \\
|
||||
Description & The user can send text using the website.\\
|
||||
|
@ -294,7 +294,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
\end{figure}
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T10 \\
|
||||
Related Requirement & F04 \\
|
||||
Description & The user can stop the sending process.\\
|
||||
|
@ -322,7 +322,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
\end{figure}
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T11 \\
|
||||
Related Requirement & F05 \\
|
||||
Description & The user can receive data using the app.\\
|
||||
|
@ -360,7 +360,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T12 \\
|
||||
Related Requirement & F05 \\
|
||||
Description & The user can restart the reception process.\\
|
||||
|
@ -381,7 +381,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
\end{table}
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T13 \\
|
||||
Related Requirement & F05 \\
|
||||
Description & The user can stop the reception process.\\
|
||||
|
@ -402,7 +402,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T14 \\
|
||||
Related Requirement & N01 \\
|
||||
Description & The app can receive data in airplane mode.\\
|
||||
|
@ -429,7 +429,7 @@ The following test cases are all structured in the same way. The table lists the
|
|||
\end{figure}
|
||||
|
||||
\begin{table}[H]
|
||||
\begin{reqTblr}{l p{10.5cm}}
|
||||
\begin{reqTblr}{l p{10.3cm}}
|
||||
ID & T15 \\
|
||||
Related Requirement & N02 \\
|
||||
Description & The transfer speed between laptop and smartphone is \SI{1}{\bit\per\second}.\\
|
||||
|
|
Reference in a new issue