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
Currently, our e2e test for policy recommendation only covers a single execution of run/status/retrieve CLI commands. And only one single Pod-to-Pod flow traffic is generated for the test of the retrieve command.
Tasks
To have better e2e test coverage, we are planning to add these test cases:
Add test cases covering policy recommendations for Pod-to-Service, and Pod-to-External flows.
Add coverage for the failed cases.
Notes
Because a recommendation job may take several minutes to complete, to minimize the test running time, I'm considering adding the Pod-to-Service and Pod-to-External flows into the current test of the retrieve command instead of creating separate test cases.
To test the failed cases, we could simulate a test case where the Driver Pod is destroyed and unavailable when the policy recommendation job is still running. Then we could check the Status and FailedReason of this job through the status command.
The text was updated successfully, but these errors were encountered:
Background
Currently, our e2e test for policy recommendation only covers a single execution of
run/status/retrieve
CLI commands. And only one single Pod-to-Pod flow traffic is generated for the test of theretrieve
command.Tasks
To have better e2e test coverage, we are planning to add these test cases:
list
anddelete
command. List and delete policy recommendation jobs #49Notes
Because a recommendation job may take several minutes to complete, to minimize the test running time, I'm considering adding the Pod-to-Service and Pod-to-External flows into the current test of the
retrieve
command instead of creating separate test cases.To test the failed cases, we could simulate a test case where the Driver Pod is destroyed and unavailable when the policy recommendation job is still running. Then we could check the Status and FailedReason of this job through the
status
command.The text was updated successfully, but these errors were encountered: