-
Notifications
You must be signed in to change notification settings - Fork 751
test(amazonq): E2E test for /doc #6215
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
Conversation
|
/runIntegrationTests |
|
Approved for next week's release |
| import { i18n } from 'aws-core-vscode/shared' | ||
| import { docGenerationProgressMessage, DocGenerationStep, Mode } from 'aws-core-vscode/amazonqDoc' | ||
|
|
||
| describe('Amazon Q Doc', async function () { |
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.
| describe('Amazon Q Doc', async function () { | |
| describe('Amazon Q /doc', async function () { |
|
|
||
| async waitForText(text: string, waitOverrides?: MessengerOptions) { | ||
| await this.waitForEvent(() => { | ||
| console.log(this.getChatItems()) |
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.
remove this
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.
tbh i think the console logs are useful. When you have a set of e2e tests that take a look time to run its usually a lot easier to see why they failed by looking at what chat items are present
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.
We should technically only log chat items when we encounter an error'd test though, otherwise theres just going to be a lot of spam in the logs
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.
yeah this was accidentally added to the commit
|
/runIntegrationTests |
| afterEach(() => { | ||
| framework.removeTab(tab.tabID) | ||
| framework.dispose() | ||
| sinon.restore() |
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.
why is sinon needed in e2e tests? if this is part of the qTestingFramework, then I would expect framework.dispose() to take care of it.
Add an E2E test for Creating a README using /doc Moved reusable functions out of featureDev.test.ts to shared test framework --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). License: I confirm that my contribution is made under the terms of the Apache 2.0 license.
Add an E2E test for Creating a README using /doc Moved reusable functions out of featureDev.test.ts to shared test framework --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). License: I confirm that my contribution is made under the terms of the Apache 2.0 license.
Add an E2E test for Creating a README using /doc
Moved reusable functions out of featureDev.test.ts to shared test framework
feature/xbranches will not be squash-merged at release time.License: I confirm that my contribution is made under the terms of the Apache 2.0 license.