Searched refs:outcome (Results 1 – 6 of 6) sorted by relevance
16 … tools that process test descriptions (`generate_test_code.py`, [outcome file](#outcome-file) tool…18 …a failure log to the test data. Avoid confusion between cases in the [outcome file](#outcome-file).47 #### Generating an outcome file49 Unit tests, `ssl-opt.sh` and `compat.sh` record the outcome of each test case in a **test outcome f…51 If you run `all.sh --outcome-file test-outcome.csv`, this collects the outcome of all the test case…55 The outcome file is in a CSV format using `;` (semicolon) as the delimiter and no quoting. This mea…57 The outcome file has 6 fields:
318 /** \brief Write the description of the test case to the outcome CSV file.359 /* Write the beginning of the outcome line.360 * Ignore errors: writing the outcome file is on a best-effort basis. */365 /** \brief Write the result of the test case to the outcome CSV file.387 /* Write the end of the outcome line.388 * Ignore errors: writing the outcome file is on a best-effort basis. */505 mbedtls_fprintf(stderr, "Unable to open outcome file. Continuing anyway.\n");
254 --append-outcome Append to the outcome file (if used).269 --no-append-outcome Write a new outcome file and analyze it (default).276 --outcome-file=<path> File where test outcomes are written (not done if451 --append-outcome) append_outcome=1;;473 --no-append-outcome) append_outcome=0;;482 --outcome-file) shift; MBEDTLS_TEST_OUTCOME_FILE="$1";;
168 --outcome-file)916 outcome="RETRY(resend)"1317 outcome=FAIL1322 outcome="RETRY(client-timeout)"1462 outcome=PASS1662 case $outcome in1664 RETRY*) printf "$outcome ";;
185 --outcome-file)
361 `outcome-analysis.sh` in the present directory.
