Lines Matching refs:internal
32 ### Reliance on internal details
34 In unit tests and in test programs, it's ok to include internal header files from `library/`. Do no…
38 If test code or test data depends on internal details of the library and not just on its documented…
73 In unit test code that needs to modify the internal behavior:
89 …umented behavior of the product, to avoid extra work when the product's internal or implementation…
125 Sometimes it is useful to peek or poke internal data.
127 * Check consistency of internal data (e.g. output of key generation).
162 …internal interfaces, mostly intended for cross-module abstraction leakage rather than for testing.…
174 We can write tests that call internal functions that are not exposed in the public interfaces. This…
178 …internal interfaces need to be used correctly. We may accidentally rely on internal details in the…
184 | Coverage | ~ Many useful tests require additional internal interfaces |
186 | | ~ The tests may call internal functions in a way that does not reflect actual usage…
187 | Effacement | ++ Fine as long as the internal interfaces aren't added solely for test purposes |
189 | | ~ Doesn't work if the users rewrite an internal module |
218 | | ~ Doesn't work if the users rewrite an internal module |
298 Solution ([internal interface](#internal-interfaces)): in most tests involving PSA functions, the c…
330 Solution ([internal interface](#internal-interfaces)): call `psa_its` functions to modify the stora…
348 Solution ([internal interface](#internal-interfaces)): call internal functions to inspect the conte…