Create transport for Test Proxy #1876
Assignees
Labels
Client
This issue points to a problem in the data-plane of the library.
test-enhancement
test-reliability
Issue that causes tests to be unreliable
Comments
heaths
added
Client
heaths
added a commit
to heaths/azure-sdk-for-rust
that referenced
this issue
Jan 29, 2025
heaths
added a commit
to heaths/azure-sdk-for-rust
that referenced
this issue
Jan 30, 2025
heaths
added a commit
to heaths/azure-sdk-for-rust
that referenced
this issue
Feb 1, 2025
heaths
added a commit
that referenced
this issue
Feb 3, 2025
* Automatically record and play back test recordings Resolves #1876 * Require `Result<T, E>` from recorded tests This is simpler to support in the `#[recorded::test]` macro and sets a good precedent we want to show users anyway instead of `unwrap()` or `expect()`. * Fix azure_core_test_macro tests * Switch to multi-threaded async runtime and send correct headers The default single-threaded async runtime runner was deadlocking in `Recording::drop()`. I opened #2049 to revisit this but I don't foresee any problem. We already don't support test-proxy on wasm32 and our mix of agents we do test on support multi-threaded async runtimes just fine. * Fix Windows tests * Safely log headers and body We need to sanitize the headers later, but easier just to sanitize them all right now. This is still better than before which only showed how many headers were in the request. * Fix regression to auto-start of test-proxy * Resolve PR feedback
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Maybe this is just our normal transport, but we should create the wiring necessary to hook it up either implicitly in integration tests (maybe via
#[cfg(test)]attribute?) or make it really easy to do in integration tests like some sort ofinit()func to wire everything up (much like tracing subscribers).The text was updated successfully, but these errors were encountered: