summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorchris.sutcliffe <ctd.sutcliffe@gmail.com>2021-12-15 11:15:44 +0000
committerchris.sutcliffe <ctd.sutcliffe@gmail.com>2021-12-15 11:15:44 +0000
commit26d16d270860ace187c16e2ebc82767155b31af9 (patch)
tree0603b75e0be0e2ef40d032a8c35453543a361a1f
parentdb297ba9b53b41dd732cd14e6fcfad83b52e0f64 (diff)
downloadesotericFORTRAN-26d16d270860ace187c16e2ebc82767155b31af9.tar.gz
esotericFORTRAN-26d16d270860ace187c16e2ebc82767155b31af9.zip
added screenshots of harnesses
-rw-r--r--report/esoteric_project_report.tex26
-rw-r--r--report/images/test_harness_code_1.pngbin0 -> 82267 bytes
-rw-r--r--report/images/test_harness_code_2.pngbin0 -> 51093 bytes
-rw-r--r--report/images/test_harness_code_3.pngbin0 -> 42628 bytes
4 files changed, 26 insertions, 0 deletions
diff --git a/report/esoteric_project_report.tex b/report/esoteric_project_report.tex
index acad3f2..e355224 100644
--- a/report/esoteric_project_report.tex
+++ b/report/esoteric_project_report.tex
@@ -419,6 +419,9 @@ Once the compiler was fully implemented, testing was moved to custom harnesses t
Each test file was run and the output carefully checked to ensure that the language and compiler were working as expected.
In addition, example source code files were written to demonstrate the capabilities of the implemented Fortran language.
The use of actual source files in testing meant that compiler and program behaviour, as well as that of the implemented IDE could be checked on tandem, thus ensuring that the software worked properly.
+Logical testing using test harnesses was particularly thorough, ensuring that the parser was able to handle comparing integers, as well as real numbers.
+In addition, extensive logical testing for the AND and OR operators was carried out to ensure that there were no bugs from the position of particular variables being evaluated.
+In other words, the software was tested so that the order of variables in a logical test did not matter, for example A AND B is equivalent to B AND A (see appendix for examples of this).
Below are some examples of output testing harnesses, run through the IDE program.
\begin{figure}[h]
@@ -478,5 +481,28 @@ State here the \% contribution to the project of each individual member of the g
\end{center}
\end{figure}
+
+\begin{figure}[h!]
+ \begin{center}
+ \includegraphics[scale=0.55]{images/test_harness_code_1.png}
+ \caption{Excerpt of test harness showing mathematical expression testing}
+ \end{center}
+\end{figure}
+
+\begin{figure}[h!]
+ \begin{center}
+ \includegraphics[scale=0.55]{images/test_harness_code_2.png}
+ \caption{Excerpt from test harness showing array and string testing}
+ \end{center}
+\end{figure}
+
+
+\begin{figure}[h!]
+ \begin{center}
+ \includegraphics[scale=0.55]{images/test_harness_code_3.png}
+ \caption{Excerpt of test harness showing conditional and logical testing}
+ \end{center}
+\end{figure}
+
\end{document}
diff --git a/report/images/test_harness_code_1.png b/report/images/test_harness_code_1.png
new file mode 100644
index 0000000..4a10a8c
--- /dev/null
+++ b/report/images/test_harness_code_1.png
Binary files differ
diff --git a/report/images/test_harness_code_2.png b/report/images/test_harness_code_2.png
new file mode 100644
index 0000000..135fa18
--- /dev/null
+++ b/report/images/test_harness_code_2.png
Binary files differ
diff --git a/report/images/test_harness_code_3.png b/report/images/test_harness_code_3.png
new file mode 100644
index 0000000..b881882
--- /dev/null
+++ b/report/images/test_harness_code_3.png
Binary files differ