-
Notifications
You must be signed in to change notification settings - Fork 2
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
chore: Refactor ai-api E2E tests #187
Conversation
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.
Will continue reviewing the PR once I have more time. Left some comments.
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.
Cleanup looks good to me, I noticed that currently the samples are not really samples and I think this will not be very helpful to users. I believe it is ok to use the samples for the E2E tests, but the tests should not guide how we structure our samples, because the purpose is a different one: Samples are for users, tests are for automatic quality insurance.
Was finally able to get to the changes for this. I've changed the sample code to hopefully have something useful now. The new retry values and timeouts seem to work well from my testing. |
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.
LGTM
Context
AI/gen-ai-hub-sdk-js-backlog#142.
DeploymentApi
andScenarioApi
endpoints, some of which are now used in the e2e-tests.Definition of Done
[ ] (Optional) Aligned changes with the Java SDK