Home
last modified time | relevance | path

Searched refs:outcome (Results 1 – 9 of 9) sorted by relevance

/openthread-3.7.0/third_party/mbedtls/repo/docs/architecture/testing/
Dtest-framework.md16 … 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 file
49 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:
/openthread-3.7.0/src/core/net/
Dmdns.cpp1666 AppendOutcome outcome; in AppendNameTo() local
1668 outcome = aTxMessage.AppendMultipleLabels(aSection, mName.AsCString(), mNameOffset); in AppendNameTo()
1669 VerifyOrExit(outcome != kAppendedFullNameAsCompressed); in AppendNameTo()
2511 AppendOutcome outcome; in AppendServiceNameTo() local
2513 outcome = aTxMessage.AppendLabel(aSection, mServiceInstance.AsCString(), mServiceNameOffset); in AppendServiceNameTo()
2514 VerifyOrExit(outcome != kAppendedFullNameAsCompressed); in AppendServiceNameTo()
2529 AppendOutcome outcome; in AppendSubServiceTypeTo() local
2531 outcome = aTxMessage.AppendLabel(aSection, kSubServiceLabel, mSubServiceTypeOffset); in AppendSubServiceTypeTo()
2532 VerifyOrExit(outcome != kAppendedFullNameAsCompressed); in AppendSubServiceTypeTo()
2542 AppendOutcome outcome; in AppendSubServiceNameTo() local
[all …]
/openthread-3.7.0/third_party/mbedtls/repo/tests/suites/
Dhost_test.function318 /** \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.
385 /* Write the end of the outcome line.
386 * Ignore errors: writing the outcome file is on a best-effort basis. */
548 mbedtls_fprintf(stderr, "Unable to open outcome file. Continuing anyway.\n");
Dmain_test.function248 * test-specific files such as the outcome file, which is arguably
/openthread-3.7.0/third_party/mbedtls/repo/tests/
Dcompat.sh187 --outcome-file)
Dssl-opt.sh169 --outcome-file)
957 outcome="RETRY(resend)"
1358 outcome=FAIL
1363 outcome="RETRY(client-timeout)"
1503 outcome=PASS
1715 case $outcome in
1717 RETRY*) printf "$outcome ";;
/openthread-3.7.0/third_party/mbedtls/repo/tests/scripts/
Dall.sh268 --append-outcome Append to the outcome file (if used).
283 --no-append-outcome Write a new outcome file and analyze it (default).
290 --outcome-file=<path> File where test outcomes are written (not done if
450 --append-outcome) append_outcome=1;;
472 --no-append-outcome) append_outcome=0;;
480 --outcome-file) shift; MBEDTLS_TEST_OUTCOME_FILE="$1";;
/openthread-3.7.0/third_party/mbedtls/repo/docs/architecture/psa-migration/
Dstrategy.md361 `outcome-analysis.sh` in the present directory.
/openthread-3.7.0/third_party/mbedtls/repo/docs/architecture/
Dpsa-shared-memory.md58 … the intermediate data back and continues the calculation, leading to an outcome that would not be…