| 7 |
|
|
| 8 |
A script (\texttt{testreport}) for automated testing is included in |
A script (\texttt{testreport}) for automated testing is included in |
| 9 |
the model within the {\em verification} directory. While intended |
the model within the {\em verification} directory. While intended |
| 10 |
primarily advanced users, the script can be helpful for beginners. |
mostly for advanced users, the script can be helpful for beginners. |
| 11 |
|
|
| 12 |
\subsection{Using \texttt{testreport}} |
\subsection{Using \texttt{testreport}} |
| 13 |
|
|
| 14 |
On many systems, the utility can be run with a command as simple as |
On many systems, the program can be run with the command: |
| 15 |
\begin{verbatim} |
\begin{verbatim} |
| 16 |
% cd verification |
% cd verification |
| 17 |
% ./testreport -ieee |
% ./testreport -ieee |
| 18 |
\end{verbatim} |
\end{verbatim} |
| 19 |
which will do the following: |
which will do the following: |
| 20 |
\begin{enumerate} |
\begin{enumerate} |
| 21 |
\item Locate all directories within the current directory (which is |
\item Locate all ``valid'' test directories. Here, valid tests are |
| 22 |
generally {\em verification}) tha |
defined to be those directories within the current directory (which |
| 23 |
|
is generally {\em verification}) that contain a subdirectory and |
| 24 |
|
file with the names {\em results/output.txt}. |
| 25 |
|
|
| 26 |
|
\item Then within each valid test: |
| 27 |
|
\begin{enumerate} |
| 28 |
|
\item run \texttt{genmake2} to produce a {\em Makefile} |
| 29 |
|
\item build an executable |
| 30 |
|
\item run the executable |
| 31 |
|
\item compare and the output of the executable with the |
| 32 |
|
contents of certain variables within {\em |
| 33 |
|
TESTNAME/results/output.txt} |
| 34 |
|
\item print and, if requested (with the |
| 35 |
|
\texttt{-addr=EMAIL\_ADDRESS} option), send a MIME-encoded email |
| 36 |
|
with the testing results |
| 37 |
|
\end{enumerate} |
| 38 |
|
|
| 39 |
\end{enumerate} |
\end{enumerate} |
| 40 |
|
|
| 41 |
For further \texttt{testreport} details, please see the |
For further details, please see the MITgcm Developers' HOWTO at: |
| 42 |
|
\begin{rawhtml} <A href=''http://mitgcm.org/docs.html'' target="idontexist"> \end{rawhtml} |
| 43 |
|
\begin{verbatim} |
| 44 |
|
http://mitgcm.org/docs.html |
| 45 |
|
\end{verbatim} |
| 46 |
|
\begin{rawhtml} </A> \end{rawhtml} |
| 47 |
|
|
| 48 |
|
|
| 49 |
\subsection{Automated testing} |
\subsection{Automated testing} |
| 50 |
|
|
| 51 |
|
Automated testing results are produced on a regular basis and they can |
| 52 |
|
be viewed at: |
| 53 |
|
\begin{rawhtml} <A href=''http://mitgcm.org/testing.html'' target="idontexist"> \end{rawhtml} |
| 54 |
|
\begin{verbatim} |
| 55 |
|
http://mitgcm.org/testing.html |
| 56 |
|
\end{verbatim} |
| 57 |
|
\begin{rawhtml} </A> \end{rawhtml} |
| 58 |
|
which also includes links to various scripts for batch job submission |
| 59 |
|
on a variety of different machines. |
| 60 |
|
|
Parent Directory
| 
Revision Log
| 
Revision Graph
| 
Patch