-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
Feature: Added unit test for watcher #1529
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: ayushrakesh <[email protected]>
Signed-off-by: ayushrakesh <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ayushrakesh thanks! I'm super excited about this, particularly since the watcher abstraction is such an important piece of the runtime crate. I see there's a bit more work to do here though. Let me know if you have any questions or if I can help out with anything.
// #[async_trait] | ||
// trait ApiMode { | ||
// type Value: Clone; | ||
|
||
// async fn list(&self, lp: &ListParams) -> kube_client::Result<ObjectList<Self::Value>>; | ||
// async fn watch( | ||
// &self, | ||
// wp: &WatchParams, | ||
// version: &str, | ||
// ) -> kube_client::Result<BoxStream<'static, kube_client::Result<WatchEvent<Self::Value>>>>; | ||
// } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this commented as a mistake?
#[derive(Clone)] | ||
struct TestResource { | ||
// fields here | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we actually need a TestResource? Can we have our TestApiMode
be generic over a K type that represents a k8s resource? Is the TestResource
used to simplify this?
Fixes #1528
Motivation
The primary problem is avoiding the accidental release of breaking changes to the watcher module in the future. The current testing approach was not adequate to catch all issues. particularly concerning how the watcher handles listing and watching resources in Kubernetes.
Solution
Creating a test-specific struct that implements the ApiMode trait. This test struct allows for injecting synthetic events and responses, simulating the behavior of an actual Kubernetes API server without making real API calls.