Searched refs:outcome (Results 1 – 5 of 5) 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).41 #### Generating an outcome file43 Unit tests and `ssl-opt.sh` record the outcome of each test case in a **test outcome file**. This f…45 If you run `all.sh --outcome-file test-outcome.csv`, this collects the outcome of all the test case…49 The outcome file is in a CSV format using `;` (semicolon) as the delimiter and no quoting. This mea…51 The outcome file has 6 fields:
339 /** \brief Write the description of the test case to the outcome CSV file.380 /* Write the beginning of the outcome line.381 * Ignore errors: writing the outcome file is on a best-effort basis. */386 /** \brief Write the result of the test case to the outcome CSV file.408 /* Write the end of the outcome line.409 * Ignore errors: writing the outcome file is on a best-effort basis. */526 mbedtls_fprintf(stderr, "Unable to open outcome file. Continuing anyway.\n");
247 --append-outcome Append to the outcome file (if used).262 --no-append-outcome Write a new outcome file and analyze it (default).269 --outcome-file=<path> File where test outcomes are written (not done if426 --append-outcome) append_outcome=1;;444 --no-append-outcome) append_outcome=0;;453 --outcome-file) shift; MBEDTLS_TEST_OUTCOME_FILE="$1";;
869 outcome="RETRY(resend)"1248 outcome=FAIL1253 outcome="RETRY(client-timeout)"1393 outcome=PASS1555 case $outcome in1557 RETRY*) printf "$outcome ";;
392 `outcome-analysis.sh` in the present directory.
