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
E2E testing for Vector should only be run on the all package test only since it focuses on interactions between components - see #211 for some thoughts on this.
Initial thoughts on testing areas:
Input handling: Ensure that Vector is picking up the expected files (pod + node logs), possibly via the API?
Output handling: Ensure that Vector is able to ship to the destinations, possibly via the API or a test with Vector connected to MinIO and checking bucket contents?
Other testing: This is not super well defined but we should evaluate if there are other health endpoints or metrics that would be helpful to look at
Vector's API is not enabled by default so we may need to enable it in CI at minimum and use it to access some of these data points.
The text was updated successfully, but these errors were encountered:
E2E testing for Vector should only be run on the all package test only since it focuses on interactions between components - see #211 for some thoughts on this.
Initial thoughts on testing areas:
Vector's API is not enabled by default so we may need to enable it in CI at minimum and use it to access some of these data points.
The text was updated successfully, but these errors were encountered: