Set up vscode integration test

[ColemanRoo]

Description

This PR adds a full integration test that runs against a live running version of Roo Cline. The test does the following:

• The test opens a new instance of VS Code
• The test activates Roo Cline
• The test sets the OpenRouter API key from a local .test_env file
• The test sends in the prompt "Hello world, what is your name?"
• The test verifies an appropriate response is returned

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Test runs locally

Checklist:

• My code follows the patterns of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation

Additional context

This is a very simple test, but in the future we can use this format to run complex tests to verify Roo Cline's full functionality.

Related Issues

n/a

Reviewers

---

Important

Adds integration tests for Roo Cline VS Code extension, verifying activation, command registration, and prompt handling.

• Integration Test Setup:
  • Adds src/test/extension.test.ts to test Roo Cline extension in VS Code.
  • Configures test environment using .test_env file for OpenRouter API key.
  • Tests extension activation, command registration, and view registration.
  • Verifies prompt handling and response correctness.
• Configuration Changes:
  • Updates .vscode-test.mjs to specify test files and launch arguments.
  • Adds test:extension script in package.json for running VS Code tests.
  • Includes dotenv in devDependencies for environment variable management.
• API and Model Handling:
  • Ensures OpenRouter API key is set and models are loaded in extension.test.ts.
  • Checks for expected Claude models availability.

^{This description was created by for 8e54360. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 66c5485

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[ellipsis-dev]

Use import instead of require for module imports to adhere to the Airbnb JavaScript style guide. This is from our Development Standards: https://www.notion.so/Development-Standards-59febcf8ead647fd9c2ec3f60c22f3df?pvs=4#11869ad2d58180f3b596d34d01891cb5

[mrubens]

@ColemanRoo definitely not the most important thing, but is there a reason these needed to change to require?