-
Notifications
You must be signed in to change notification settings - Fork 383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
proxy: more tests #4709
Comments
Need some time to investigate how we can actually test something. A quick idea in my mind is to introduce failpoint and add yet another mock API besides current Postgres + control_plane API so that we can test everything purely in Rust. |
Given now we've refactored `connect_to_compute` as a generic, we can test it with mock backends. In this PR, we mock the error API and connect_once API to test the retry behavior of `connect_to_compute`. In the next PR, I'll add mock for credentials so that we can also test behavior with `wake_compute`. ref #4709 --------- Signed-off-by: Alex Chi Z <chi@neon.tech>
## Problem ref #4721, ref #4709 ## Summary of changes This PR adds unit tests for wake_compute. The patch adds a new variant `Test` to auth backends. When `wake_compute` is called, we will verify if it is the exact operation sequence we are expecting. The operation sequence now contains 3 more operations: `Wake`, `WakeRetry`, and `WakeFail`. The unit tests for proxy connects are now complete and I'll continue work on WebSocket e2e test in future PRs. --------- Signed-off-by: Alex Chi Z <chi@neon.tech>
web socket tests are running at https://github.com/neondatabase/neon/actions/workflows/pg_clients.yml daily. For the pingdom test, I would like to track it in #4851 instead, because they are basically the same thing that we run an external service to collect both metrics + check if the service is available. Therefore, I'm going to close this issue for now. |
The text was updated successfully, but these errors were encountered: