Skip to content

Conversation

@jpinkney-aws
Copy link
Contributor

Problem

  • we have tests for the amazon q lsp installer but not the workspace context lsp installer

Solution

  • add tests for the workspace context lsp installer
  • add a test for language server activation

  • 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.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@jpinkney-aws jpinkney-aws requested review from a team as code owners March 12, 2025 01:41
@jpinkney-aws
Copy link
Contributor Author

jpinkney-aws commented Mar 12, 2025

/runIntegrationTests

@Hweinstock
Copy link
Contributor

The E2E failures seen here should be fixed in 643ae10.

describe('AmazonQLSP', () => {
createLspInstallerTests({
suiteName: 'AmazonQLSPInstaller',
lspConfig: getAmazonQLspConfig(),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you stubbing the DevSettings.Instance (part of this config) to avoid bleed through between the tests?

Is there any reason we should/shouldn't reset this between tests so you can use the real object?

Copy link
Contributor Author

@jpinkney-aws jpinkney-aws Mar 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good call out, I think for these tests we can just use the default config directly instead of the one that pulls from default/env vars/settings. I made a fixup pr that changes that

@jpinkney-aws jpinkney-aws merged commit 09b5557 into aws:feature/amazonqLSP Mar 13, 2025
22 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants