Skip to content
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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

ayushrakesh
Copy link

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.

Copy link
Contributor

@mateiidavid mateiidavid left a 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.

Comment on lines +160 to +170
// #[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>>>>;
// }
Copy link
Contributor

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?

Comment on lines +180 to +183
#[derive(Clone)]
struct TestResource {
// fields here
}
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add better unit tests for watcher
2 participants