diff options
| author | AidenRushbrooke <72034940+AidenRushbrooke@users.noreply.github.com> | 2021-12-15 11:05:25 +0000 |
|---|---|---|
| committer | AidenRushbrooke <72034940+AidenRushbrooke@users.noreply.github.com> | 2021-12-15 11:05:25 +0000 |
| commit | b0f81d4902e1d16640dbaa9fe4fcf8e49b01966a (patch) | |
| tree | fdcefb124499fa0794fe1667592faf6ff492d410 /report | |
| parent | db297ba9b53b41dd732cd14e6fcfad83b52e0f64 (diff) | |
| download | esotericFORTRAN-b0f81d4902e1d16640dbaa9fe4fcf8e49b01966a.tar.gz esotericFORTRAN-b0f81d4902e1d16640dbaa9fe4fcf8e49b01966a.zip | |
adjusted image positions
Diffstat (limited to 'report')
| -rw-r--r-- | report/esoteric_project_report.pdf | bin | 281078 -> 360333 bytes | |||
| -rw-r--r-- | report/esoteric_project_report.tex | 8 |
2 files changed, 4 insertions, 4 deletions
diff --git a/report/esoteric_project_report.pdf b/report/esoteric_project_report.pdf Binary files differindex 21bf6c7..89540da 100644 --- a/report/esoteric_project_report.pdf +++ b/report/esoteric_project_report.pdf diff --git a/report/esoteric_project_report.tex b/report/esoteric_project_report.tex index acad3f2..f239eed 100644 --- a/report/esoteric_project_report.tex +++ b/report/esoteric_project_report.tex @@ -396,7 +396,7 @@ The second sprint tested the implementation of various different functionalities \subsection{Sprint 3 testing} -\begin{table}[h] +\begin{table}[!htb] \caption[]{Sprint 3 Tests and their results} \begin{center} \begin{tabular}{|l|l|l|l|}\hline @@ -413,7 +413,7 @@ The second sprint tested the implementation of various different functionalities \end{table} Testing during this sprint focused on more advanced program functionality, including conditional testing, and the concatenation of multiple strings for a print statement. These tests ensured that the logical and conditional parts of our compiler worked as expected. - +\newpage \section{Fortran Source File Testing} Once the compiler was fully implemented, testing was moved to custom harnesses that were written in Fortran. Each test file was run and the output carefully checked to ensure that the language and compiler were working as expected. @@ -421,14 +421,14 @@ In addition, example source code files were written to demonstrate the capabilit 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. Below are some examples of output testing harnesses, run through the IDE program. -\begin{figure}[h] +\begin{figure}[!htb] \centering \includegraphics[scale=0.5]{images/test_harness_1.png} \caption{Mathematical testing} \label{test_harness_one} \end{figure} -\begin{figure}[h] +\begin{figure}[!htb] \centering \includegraphics[scale=0.5]{images/test_harness_2.png} \caption{Logical testing} |