Home
last modified time | relevance | path

Searched refs:tests (Results 1 – 25 of 115) sorted by relevance

12345

/mbedtls-latest/tests/scripts/
Dcomponents-configuration-tls.sh22 tests/ssl-opt.sh
105 tests/ssl-opt.sh -f "TLS 1.2"
134 tests/ssl-opt.sh -f "TLS 1.2"
162 tests/ssl-opt.sh -f "TLS 1.2"
191 tests/ssl-opt.sh -f "TLS 1.2"
216 P_SRV=../s2_no_use_psa tests/ssl-opt.sh -f "ECJPAKE: working, TLS"
218 P_SRV=../s2_no_use_psa tests/ssl-opt.sh -f "ECJPAKE: opaque password client only, working, TLS"
220 P_CLI=../c2_no_use_psa tests/ssl-opt.sh -f "ECJPAKE: working, TLS"
222 P_CLI=../c2_no_use_psa tests/ssl-opt.sh -f "ECJPAKE: opaque password server only, working, TLS"
235 tests/ssl-opt.sh -f "Max fragment\|Large packet"
[all …]
Dcomponents-configuration.sh25 tests/scripts/run_demos.py
37 tests/scripts/run_demos.py
43 tests/scripts/run-metatests.sh any asan poison
46 tests/ssl-opt.sh
49 tests/compat.sh
52 tests/context-info.sh
68 tests/ssl-opt.sh
71 tests/compat.sh
74 tests/context-info.sh
90 tests/ssl-opt.sh
[all …]
Dcomponents-basic-checks.sh14 tests/scripts/recursion.pl library/*.c
20 tests/scripts/check-generated-files.sh
23 tests/scripts/check-generated-files.sh -u
25 tests/scripts/check-generated-files.sh
29 tests/scripts/check-generated-files.sh -u
31 tests/scripts/check-generated-files.sh
39 tests/scripts/check-doxy-blocks.pl
44 tests/scripts/check_files.py
61 tests/scripts/check_names.py -v
71 tests/scripts/check_test_cases.py -q $opt
[all …]
Dbasic-in-docker.sh23 source tests/scripts/docker_env.sh
25 run_in_docker tests/scripts/all.sh 'check_*'
32 run_in_docker -e OSSL_NO_DTLS=1 tests/compat.sh
33 run_in_docker tests/ssl-opt.sh -e '\(DTLS\|SCSV\).*openssl'
34 run_in_docker tests/scripts/test-ref-configs.pl
35 run_in_docker tests/scripts/depends.py curves
36 run_in_docker tests/scripts/depends.py kex
Dcomponents-sanitizers.sh17 git -C tests/suites grep -L TEST_CF_ 'test_suite_*.function' |
26 ls -1 tests/suites/test_suite_*.function |
155 tests/scripts/run-metatests.sh any msan
158 tests/scripts/run_demos.py
161 tests/ssl-opt.sh
167 tests/compat.sh
185 tests/ssl-opt.sh --memcheck
190 tests/compat.sh --memcheck
195 tests/context-info.sh --memcheck
Dcomponents-configuration-crypto.sh56 check_renamed_symbols tests/include/spe/crypto_spe.h library/libmbedcrypto.a
143 tests/ssl-opt.sh
156 tests/ssl-opt.sh -f RSA
159 tests/compat.sh -t RSA
162 tests/context-info.sh
182 tests/ssl-opt.sh -f 'Default\|SSL async private.*delay=\|tickets enabled on server'
185 tests/compat.sh -m tls12 -t 'ECDSA PSK' -V NO -p OpenSSL
204 tests/ssl-opt.sh -f 'Default\|SSL async private.*delay=\|tickets enabled on server'
207 tests/compat.sh -m tls12 -t 'ECDSA PSK' -V NO -p OpenSSL
230 tests/ssl-opt.sh -f 'Default\|SSL async private: sign'
[all …]
Dall.sh237 if [[ -e ${PWD}/tests/scripts/quiet ]]; then
238 export PATH=${PWD}/tests/scripts/quiet:$PATH
260 Run mbedtls release validation tests.
261 By default, run all tests. With one or more COMPONENT, run only those.
277 -f|--force Force the tests to overwrite any modified files.
278 -k|--keep-going Run all tests and report errors at the end.
279 -m|--memory Additional optional memory tests.
299 --no-memory No additional memory tests (default).
301 --out-of-source-dir=<path> Directory used for CMake out-of-source build tests.
304 --random-seed Use a random seed value for randomized tests (default).
[all …]
Dbasic-build-test.sh33 if [ -d library -a -d include -a -d tests ]; then :; else
82 cd tests
121 } | tee tests/cov-$TEST_OUTPUT
142 cd tests
Dtest_psa_constant_names.py184 tests = Tests(options)
185 tests.run_all(inputs)
186 tests.report(sys.stdout)
187 if tests.errors:
Dcomponents-compiler.sh89 …w64-mingw32-ar LD=i686-w64-minggw32-ld CFLAGS='-Werror -maes -msse2 -mpclmul' WINDOWS_BUILD=1 tests
94 …w64-minggw32-ld CFLAGS='-Werror -Wall -Wextra -maes -msse2 -mpclmul' WINDOWS_BUILD=1 SHARED=1 tests
138 …gdb -ex "$gdb_disable_aslr" -x tests/scripts/test_zeroize.gdb -nw -batch -nx 2>&1 | tee test_zeroi…
Dall-in-docker.sh22 source tests/scripts/docker_env.sh
25 run_in_docker tests/scripts/all.sh \
/mbedtls-latest/
DMakefile7 .PHONY: all no_test programs lib tests install uninstall clean test check lcov apidoc apidoc_clean
9 all: programs tests
20 tests: lib mbedtls_test target
21 $(MAKE) -C tests
24 $(MAKE) -C tests mbedtls_test
30 tests/%:
31 $(MAKE) -C tests $*
36 generated_files: tests/generated_files
138 $(MAKE) -C tests clean
148 $(MAKE) -C tests neat
[all …]
DCMakeLists.txt93 option(ENABLE_TESTING "Build Mbed TLS tests." OFF)
95 option(ENABLE_TESTING "Build Mbed TLS tests." ON)
312 # The C files in tests/src directory contain test code shared among test suites
322 # target. This library of objects is used by tests and programs CMake files
327 ${CMAKE_CURRENT_SOURCE_DIR}/tests/src/*.c
328 ${CMAKE_CURRENT_SOURCE_DIR}/tests/src/drivers/*.c)
333 ${CMAKE_CURRENT_SOURCE_DIR}/tests/src/test_keys.h
335 ${CMAKE_CURRENT_SOURCE_DIR}/tests
340 "${CMAKE_CURRENT_SOURCE_DIR}/tests/src/test_keys.h"
344 … add_custom_target(test_keys_header DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/tests/src/test_keys.h)
[all …]
DCONTRIBUTING.md11 - [Tests](#tests): please ensure the PR includes adequate tests.
17tests, as mentioned in the [Tests](#tests) and [Continuous Integration](#continuous-integration-te…
58 As mentioned, tests that show the correctness of the feature or bug fix should be added to the pull…
60 Mbed TLS includes a comprehensive set of test suites in the `tests/` directory that are dynamically…
62 [A Knowledge Base article describing how to add additional tests is available on the Mbed TLS websi…
64 A test script `tests/scripts/basic-build-test.sh` is available to show test coverage of the library…
70 …n made, the Continuous Integration (CI) tests are triggered and run. You should follow the result …
72 …e [githooks scripts](https://github.com/Mbed-TLS/mbedtls/tree/development/tests/git-scripts) prior…
DREADME.md52 * Perl to run the tests, and to generate some source files in the development branch.
82 * On Unix/POSIX systems, run `tests/scripts/check-generated-files.sh -u` to generate all the config…
95 In order to run the tests, enter:
99 The tests need Python to be built and Perl to be run. If you don't have one of them installed, you …
103 You'll still be able to run a much smaller set of tests with:
113 …o some issues. Please check the Makefiles in `library/`, `programs/` and `tests/` for options to m…
125 In order to run the tests, enter:
133 …the test suites, but kept the programs enabled, you can still run a much smaller set of tests with:
230 …c projects needed to build the library and all the programs. The files in tests are not generated …
243 Mbed TLS includes an elaborate test suite in `tests/` that initially requires Python to generate th…
[all …]
/mbedtls-latest/docs/architecture/
Dpsa-crypto-implementation-structure.md81 * [ ] `include/psa/crypto_config.h`, `tests/include/test/drivers/crypto_config_test_driver_extensio…
86 * [ ] `tests/suites/test_suite_psa_crypto_metadata.data` — [New functions and macros](#new-function…
87 * (If adding `PSA_IS_xxx`) `tests/suites/test_suite_psa_crypto_metadata.function` — [New functions …
88 * [ ] `tests/suites/test_suite_psa_crypto*.data`, `tests/suites/test_suite_psa_crypto*.function` — …
89 …ledge.py`, `framework/scripts/mbedtls_framework/asymmetric_key_data.py` — [Unit tests](#unit-tests)
97tests/suites/test_suite_psa_crypto.data`, `tests/suites/test_suite_psa_crypto.function`, `tests/su…
121tests/suites/test_suite_psa_crypto_metadata.data` that verifies that `PSA_IS_xxx` macros behave pr…
131 * For the testing of the driver dispatch code, `tests/include/test/drivers/crypto_config_test_drive…
154 ### Unit tests
156 A number of unit tests are automatically generated by `framework/scripts/generate_psa_tests.py` bas…
[all …]
Dpsa-shared-memory.md293 Proposed general idea: have tests where the test code calling API functions allocates memory in a c…
330 …precisely test the property we want to validate, so we are relying on the tests to fail if given r…
340 …tion (unless Valgrind is simply more poorly documented). However, running tests under Valgrind cau…
342 **Design decision: Implement memory poisoning tests with both Valgrind's memcheck and ASan manual p…
344 ##### Validation with new tests
346tests would be simpler to implement than using existing tests, since the tests can be written to t…
350 ##### Validation with existing tests
352 An alternative approach would be to integrate memory poisoning validation with existing tests. This…
354 * All of the tests are written already, potentially saving development time.
355tests is greater than would be achievable writing new tests from scratch. In practice this advanta…
[all …]
/mbedtls-latest/docs/architecture/testing/
Dinvasive-testing.md34 In unit tests and in test programs, it's ok to include internal header files from `library/`. Do no…
36tests on functions that aren't part of the public API. Declare such functions in `library/*.h` and…
61 * **Where tests must be able to change the behavior, do it by function substitution.** See [“rules …
88 * Portability: tests should work on every platform. Skipping tests on certain platforms may hide er…
89tests should only enforce the documented behavior of the product, to avoid extra work when the pro…
102 * Files in storage (PSA API only — in the Mbed TLS API, black-box unit tests are sufficient).
143 We can include all the features we want to test in the public interface. Then the tests can be trul…
145 …main purpose of `mbedtls_psa_crypto_free` is to clean up all resources in tests, but this is also …
151 | Coverage | ~ Many useful tests are not reasonably achievable |
166 | Coverage | ~ Many useful tests are not reasonably achievable |
[all …]
Dtest-framework.md7 ## Unit tests
25 `tests/scripts/check_test_cases.py` enforces some rules and warns if some guidelines are violated.
27 ## TLS tests
29 ### SSL extension tests argument
37 ### SSL cipher suite tests argument
43 ## Running tests
49 Unit tests, `ssl-opt.sh` and `compat.sh` record the outcome of each test case in a **test outcome f…
/mbedtls-latest/docs/architecture/psa-migration/
Dtesting.md12 `MBEDTLS_USE_PSA_CRYPTO` and runs the full battery of tests; currently that's
53 new API to be used, and one or more tests in `ssl-opt.sh` using that.
78 - usually already covered by existing tests for higher-level modules:
80 covered by running the existing TLS tests in a build with
94 be already be covered by running the existing tests in a build with
99 whether to use the PSA or legacy code paths, specific tests might be in order.
Doutcome-analysis.sh42 tests/ssl-opt.sh
81 data_files=$(cd tests/suites && echo *.data)
90 extra_files=$(cd tests/opt-testcases && echo *.sh)
/mbedtls-latest/tests/
DDescriptions.txt2 The various 'test_suite_XXX' programs from the 'tests' directory, executed
13 The 'tests/compat.sh' script checks interoperability with OpenSSL and
20 The 'tests/ssl-opt.sh' script checks various options and/or operations not
Dcompat-in-docker.sh27 source tests/scripts/docker_env.sh
54 tests/compat.sh \
/mbedtls-latest/tests/git-scripts/
DREADME.md7 …<Mbed TLS root>/tests/git-scripts` directory, and one must create a soft link from `<Mbed TLS root…
12 `ln -s ../../tests/git-scripts/pre-push.sh pre-push`
/mbedtls-latest/tests/suites/
Dtest_suite_platform_printf.function5 * - For some tests, it makes sense to vary the format.
6 * - For all tests, it means we're testing the actual printf function
8 * (It may be useful to add tests that allow compiler optimizations.

12345