-
Notifications
You must be signed in to change notification settings - Fork 501
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
test(amazonq): Add inline completion e2e tests #6486
base: master
Are you sure you want to change the base?
Conversation
/runIntegrationTests |
/runIntegrationTests |
4 similar comments
/runIntegrationTests |
/runIntegrationTests |
/runIntegrationTests |
/runIntegrationTests |
/runIntegrationTests |
4 similar comments
/runIntegrationTests |
/runIntegrationTests |
/runIntegrationTests |
/runIntegrationTests |
cc95b91
to
5e95fa6
Compare
5e95fa6
to
8d16b78
Compare
/runIntegrationTests |
It flaked 1 time over 30 executions (~10 requests + minimum/stable/insiders). I haven't been able to reproduce it again though |
@@ -0,0 +1,179 @@ | |||
/*! |
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.
this file is located at a new place, whereas all the other Q features are located in packages/amazonq/test/e2e/amazonq
maybe the e2e/amazonq/*
files should be lifted up into this location (followup PR)? since the e2e/amazonq
subdir seems redundant.
const ok = await waitUntil( | ||
async () => | ||
globals.telemetry.logger.query({ |
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.
Doesn't assertTelemetry()
do this, or what is it missing?
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.
assertTelemetry does the querying but it doesn't wait for the event to appear as far as I can tell. I want the tests to explicitly wait until those telemetry events appear and then finally assert on them
Problem
Solution
feature/x
branches will not be squash-merged at release time.