Changeset 1742 for XIOS/dev/dev_trunk_omp/doc/XIOS_testcase_user_guide.tex
- Timestamp:
- 10/15/19 11:37:29 (5 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
XIOS/dev/dev_trunk_omp/doc/XIOS_testcase_user_guide.tex
r1741 r1742 19 19 % read geometry.pdf for detailed page layout information 20 20 21 \usepackage{graphicx} % support the \includegraphics command and options i21 \usepackage{graphicx} % support the \includegraphics command and options 22 22 23 23 % \usepackage[parfill]{parskip} % Activate to begin paragraphs with an empty line rather than an indent … … 26 26 \usepackage{booktabs} % for much better looking tables 27 27 \usepackage{array} % for better arrays (eg matrices) in maths 28 \usepackage{paralist} % very flexible & customi sable lists (eg. enumerate/itemize, etc.)28 \usepackage{paralist} % very flexible & customizable lists (eg. enumerate/itemize, etc.) 29 29 \usepackage{verbatim} % adds environment for commenting out blocks of text & for better verbatim 30 30 \usepackage{subfig} % make it possible to include more than one captioned figure/table in a single float … … 34 34 \usepackage{fancyhdr} % This should be set AFTER setting up the page geometry 35 35 \pagestyle{fancy} % options: empty , plain , fancy 36 \renewcommand{\headrulewidth}{0pt} % customi se the layout...36 \renewcommand{\headrulewidth}{0pt} % customize the layout... 37 37 \lhead{}\chead{}\rhead{} 38 38 \lfoot{}\cfoot{\thepage}\rfoot{} … … 117 117 118 118 The XIOS generic testcase is a set of unit tests that test functionalities of 119 XIOS. It is reserved for XIOS develop pers and it is designed to ensure that the119 XIOS. It is reserved for XIOS developers and it is designed to ensure that the 120 120 XIOS does not introduce errors after each code modification. 121 121 122 \section{Org nization of the testcase}122 \section{Organization of the testcase} 123 123 The XIOS generic testcase is located in the \verb|GENERIC_TESTCASE| folder inside 124 124 the XIOS directory. Inside the \verb|GENERIC_TESTCASE| folder, we have for the moment … … 157 157 158 158 Besides of the default value, one can also set a temporal value for the configuration variables in the file \verb|user_params.def|. 159 In this file, each variable can have multiple values sep erated by a semecolon. For example, \verb|NumberServers=2,4,6|.159 In this file, each variable can have multiple values separated by a semicolon. For example, \verb|NumberServers=2,4,6|. 160 160 From such definition, the testcase will generate 3 different configurations and tests will be run for each configuration. 161 161 162 162 163 163 \subsection{Define the output file check list} 164 The validation of the testcase is ensured by the compar aison between the newly generated output165 \verb|NetCDF| files and the pre stored reference results. In some cases, one maybe interested in only one or serveral output files.166 It will not be necessary to compare all output files for this will slow down the whole test execu ition.164 The validation of the testcase is ensured by the comparison between the newly generated output 165 \verb|NetCDF| files and the pre-stored reference results. In some cases, one maybe interested in only one or several output files. 166 It will not be necessary to compare all output files for this will slow down the whole test execution. 167 167 To specify the output files to compare with the reference, one can modify the \verb|checkfile.def| file. 168 If nothing is set in this file, or \verb|all| is set, then all output files will be examin ated.168 If nothing is set in this file, or \verb|all| is set, then all output files will be examined. 169 169 170 170 \section{How to launch XIOS testcase} … … 204 204 \end{lstlisting} 205 205 206 This C test style summary report shows the overall execution status of all unit tests.206 This CTest style summary report shows the overall execution status of all unit tests. 207 207 Besides of this console output, we also have \verb|report.html| which can be viewed 208 208 by any web browser.
Note: See TracChangeset
for help on using the changeset viewer.