You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current end-to-end tests for xdsclient utilize a watcher implementation with a channel size of 1. This limitation prevents us from testing scenarios involving multiple updates with a combination of errors and successful updates.
To overcome this, we should modify the test watcher implementations to incorporate three separate channels:
Update Channel: For successful updates
Error Channel: For error updates
Resource Not Found Channel: For "resource not found" updates
Each channel should have a configurable size, allowing tests to adjust it as needed. This enhancement will enable comprehensive testing of various update scenarios, including those with mixed successes and failures.
The text was updated successfully, but these errors were encountered:
The current end-to-end tests for xdsclient utilize a watcher implementation with a channel size of 1. This limitation prevents us from testing scenarios involving multiple updates with a combination of errors and successful updates.
To overcome this, we should modify the test watcher implementations to incorporate three separate channels:
Each channel should have a configurable size, allowing tests to adjust it as needed. This enhancement will enable comprehensive testing of various update scenarios, including those with mixed successes and failures.
The text was updated successfully, but these errors were encountered: