Home
last modified time | relevance | path

Searched refs:expected (Results 1 – 25 of 39) sorted by relevance

12

/mbedtls-development/tests/suites/
A Dtest_suite_asn1write.function29 const data_t *expected, int ret )
33 if( data->size < expected->len )
43 expected->x, expected->len );
61 void mbedtls_asn1_write_null( data_t *expected )
81 void mbedtls_asn1_write_bool( int val, data_t *expected )
101 void mbedtls_asn1_write_int( int val, data_t *expected )
122 void mbedtls_asn1_write_enum( int val, data_t *expected )
158 if( expected->len > 10 && data.size == 8 )
159 data.size = expected->len - 2;
211 if( expected->len > 10 && data.size == 8 )
[all …]
A Dtest_suite_dhm.function6 const mbedtls_mpi *expected )
13 TEST_ASSERT( mbedtls_mpi_cmp_mpi( &actual, expected ) == 0 );
22 * syntax and check that the value is the expected one (taken from the
24 static int check_dhm_param_output( const mbedtls_mpi *expected,
41 TEST_EQUAL( n, mbedtls_mpi_size( expected ) );
44 TEST_EQUAL( 0, mbedtls_mpi_cmp_mpi( expected, &actual ) );
A Dtest_suite_base64.function57 signed char expected;
65 expected = -1;
67 expected = p - base64_digits;
72 TEST_EQUAL( actual, expected );
A Dtest_suite_psa_crypto_storage_format.function14 * Test that it has the expected representation.
36 /* Check that the key is represented as expected. */
85 /* Check that the injected key exists and looks as expected. */
157 * check that it has the expected format so that future versions
A Dtest_suite_ecp.function864 TEST_ASSERT( ret == expected );
866 if( expected == 0 )
890 TEST_ASSERT( ret == expected );
922 /* M = N - C = - ( C - N ) (expected result of fix_negative) */
937 void genkey_mx_known_answer( int bits, data_t *seed, data_t *expected )
950 ASSERT_ALLOC( actual, expected->len );
955 if( expected->len == 0 )
964 TEST_EQUAL( 0, mbedtls_mpi_write_binary( &d, actual, expected->len ) );
967 * The advantage is that it's easier to test the expected properties
975 ASSERT_COMPARE( expected->x, expected->len,
[all …]
A Dtest_suite_ecdh.function369 data_t *expected )
410 TEST_ASSERT( shared_secret_length == expected->len );
411 TEST_ASSERT( memcmp( expected->x, shared_secret,
A Dtest_suite_psa_crypto_slot_management.function282 * exist. Otherwise check that it still exists and has the expected
558 /* Test that the target slot has the expected content. */
920 * that they have the expected value and destroy them. In that process,
1001 * expected value. Then, destroy it.
1029 * expected values.
1042 * Check we can export the persistent key and that it have the expected
A Dtest_suite_dhm.data29 ## x_size = P_size. If this behavior changes in the future, change the expected
A Dtest_suite_psa_crypto_se_driver_hal.function78 * case, the test driver code is expected to have called mbedtls_test_fail()
600 /* Check that the persistent data of a driver has its expected content. */
910 /* Test that the key was created in the expected slot. */
945 /* Test that the key was created in the expected slot. */
1049 /* Test that the key was created in the expected slot. */
1053 * including the expected slot. */
1487 /* Test that the key exists and has the expected attributes. */
A Dtest_suite_psa_crypto_entropy.function72 /* This test case is only expected to pass if the signature mechanism
A Dtest_suite_net.function121 * it may still happen to return the expected failure code, but if this
A Dtest_suite_entropy.function345 * if result >= 0: result = expected number of calls to source 1
346 * if result < 0: result = expected return code from mbedtls_entropy_func()
A Dtest_suite_aes.xts.data2 # Tests for expected errors (negative tests)
A Dtest_suite_ssl.function2115 * correct and works as expected.
2232 * correct and works as expected on unconnected sockets.
3678 data_t *expected )
3696 TEST_ASSERT( (size_t) desired_length == expected->len );
3706 expected->x, (size_t) expected->len );
3764 data_t *expected )
3782 TEST_ASSERT( (size_t) desired_length == expected->len );
3793 expected->x, desired_length );
4049 data_t *expected )
4059 ASSERT_COMPARE( secret_new, (size_t) expected->len,
[all …]
A Dtest_suite_asn1parse.function15 /* Use this magic value in some tests to indicate that the expected result
237 /* full_result: expected result from parsing the given string. */
445 * expected value, but they matter for the actual value.)
A Dtest_suite_cipher.function405 iv_len = 13; /* For CCM, IV length is expected to be between 7 and 13 bytes.
652 iv_len = 13; /* For CCM, IV length is expected to be between 7 and 13 bytes.
783 * this results in the expected plaintext, and that
A Dtest_suite_psa_crypto_metadata.function102 * values) have the expected parity.
104 * The expected parity is even so that 0 is considered a valid encoding.
/mbedtls-development/tests/scripts/
A Dtest_generate_test_code.py208 expected = '''
215 self.assertEqual(code, expected)
225 expected = '''
232 self.assertEqual(code, expected)
241 expected = '''
263 expected = '''
278 expected = '''
403 expected = ['MBEDTLS_ECP_C']
1185 expected = """
1203 expected = """
[all …]
/mbedtls-development/docs/architecture/testing/
A Ddriver-interface-test-strategy.md25 …the proper function is called, that it receives the expected inputs and that it produces the expec…
41 …ons involve multiple driver methods; these should validate that all the expected driver methods ar…
45 … register multiple drivers with a key in each driver and check that the expected driver is called.…
46 …cture with multiple lifetime values and check that the driver receives the expected lifetime value.
56 …expected inputs reach the driver. This may be implicit in a test that checks the outputs if the on…
70 * Check that the storage ends up in the expected state. At least make sure that no intermediate fil…
90 * Check both that the storage has the expected content (this can be done by e.g. using a key that i…
A Dpsa-storage-format-testing.md23 …expected state of the storage after the key is created. The test case creates a key as indicated b…
25 In addition, the test case also loads the key and checks that it has the expected data and metadata…
39 … the corresponding test cases in load-only mode: create a file with the expected content, load it …
62 …ven identifier (using `psa_import_key`) and verify that a file with the expected name is created, …
68 …th `psa_import_key`. Read the file content and validate that it has the expected layout, deduced f…
/mbedtls-development/programs/psa/
A Dcrypto_examples.c34 #define ASSERT_STATUS( actual, expected ) \ argument
37 if( ( actual ) != ( expected ) ) \
41 (psa_status_t) actual, (psa_status_t) expected ); \
/mbedtls-development/ChangeLog.d/
A Dccm_star_no_tag.txt9 For decryption a minimum of 16-byte long input is expected.
A Dpsa_gcm_buffer_limitation.txt14 Alternative GCM implementations are expected to verify
/mbedtls-development/include/psa/
A Dcrypto.h3929 psa_key_id_t expected);
/mbedtls-development/docs/architecture/
A Dpsa-crypto-implementation-structure.md50 The code of most PSA APIs is expected to match precisely the above layout. However, it is likely th…

Completed in 37 milliseconds

12