max / synckit
| 1 | //! Integration tests against a wiremock stand-in for the MNW SyncKit server. |
| 2 | //! |
| 3 | //! One binary, one module per domain. Each module verifies the full HTTP |
| 4 | //! round-trip for its surface: the request the client builds, the retry and error |
| 5 | //! classification around it, and the encryption on either side. |
| 6 | //! |
| 7 | //! Shared fixtures live in [`common`] and the mock harness in [`mockkit`]; a |
| 8 | //! module reaches both with `use crate::common::*;`. |
| 9 | |
| 10 | |
| 11 | |
| 12 | |
| 13 | |
| 14 | |
| 15 | |
| 16 | |
| 17 | |
| 18 | |
| 19 | |
| 20 | |
| 21 | |
| 22 | |
| 23 | // `rotate_key` finishes by caching the new key through `keystore::store_key`. |
| 24 | // Under `keychain` that would reach the OS secret service, so the harness |
| 25 | // installs `keyring_core`'s in-memory mock as the process default store |
| 26 | // (`common::ensure_mock_keystore`) and the shipping code path runs hermetically. |
| 27 | // Runs in both feature configurations; the two tests that assert on keychain |
| 28 | // contents are gated to the one where there is a keychain to assert on. |
| 29 | |
| 30 | |
| 31 | |
| 32 | |
| 33 | |
| 34 |