Lines Matching refs:in
4 * we test all the layers in a single test suite, unlike the way other
5 * functions are tested with each layer in its own test suite.
12 * - Correctness of outputs (well-formed, in range).
15 * We test parameter validation in a standard way, with unit tests with
22 * We test the correctness of outputs in positive tests:
31 * in mpi_random_many, which runs the function multiple times. This also
32 * helps in validating the output range, through test cases with a small
36 * in the same way as mbedtls_mpi_core_random(). This is done in
62 /* Test whether bytes represents (in big-endian base 256) a number b that
103 * Testing x >= 2^4 amounts to picking A = 1/16 in the function
118 /* Same RNG as in mpi_random_values */
150 /* Same RNG as in mpi_core_random_basic */
181 /* Also check that they have consumed the RNG in the same way. */
182 /* This may theoretically fail on rare platforms with padding in
183 * the structure! If this is a problem in practice, change to a
198 /* Same RNG as in mpi_core_random_basic */
248 /* Also check that they have consumed the RNG in the same way. */
249 /* This may theoretically fail on rare platforms with padding in
250 * the structure! If this is a problem in practice, change to a
268 /* Generate numbers in the range 1..bound-1. Do it iterations times.
270 * that iterations is large enough that a one-in-2^iterations chance
297 * fit in a byte. */
314 * necessary auxiliary functions don't exist yet in core. */
350 /* Assert that each bit has been set in at least one result and
351 * clear in at least one result. Provided that iterations is not
429 * size as the modulus, otherwise it's a mistake in the test data. */
431 /* Sanity check: check that the result is in range */