If the information below does not answer your question about results from the test suite, ask on the HipChat pageon /wiki/spaces/ED/pages/36864779.
Test result output looks like the following:
...
The following table, assembled from the Automated Test System slides presented by CSEG, describes the result codes of tests that have passed, failed, or are still running.
| Result Code | Meaning | Where to Look First |
|---|---|---|
| Good results | ||
| PASS | Test passed | |
| Bad results | ||
| FAIL | Test failed (either due to run failure or, e.g., no-exact restarts for an ERS test) | (1) TestStatus.out file in case directory: this will help you see the cause of failure – e.g., run didn’t complete vs. test requirements (such as exact restart) weren’t met. Look for FAIL in this file, and any messages above the FAIL line. (2) If run didn’t complete, check log files and core files in run directory (3) If requirements of test weren’t met,TestStatus.out will generally refer to differences in coupler log files and/or coupler history files. History file differences can be seen in the cprnc.out file in the run directory. |
| Test not yet complete | ||
| PEND | Test submitted, waiting in queue, or currently running | |