Skip to content
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

Switch to built-in VS Code test UI unconditionally #3232

Merged
merged 6 commits into from
Jan 11, 2024
Merged

Conversation

dbartol
Copy link
Contributor

@dbartol dbartol commented Jan 11, 2024

Now that we've been using the new test UI for several months in canary builds, I've enabled that new UI unconditionally. This removes our dependency on the Test Explorer UI" and "Test Adapter Converter" extensions and related packages.

The initial commit just removes the old implementation from test-adapter.ts, but leaves the shared base class in test-manager-base.ts intact. A later commit merges all of that code into test-manager.ts now that we don't have two different test managers to worry about.

I've also updated both the repo readme and the extension readme to remove mentions of those two external extensions.

Fixes #1099

@dbartol dbartol requested a review from a team as a code owner January 11, 2024 16:52
@dbartol dbartol added the Complexity: Low A good task for newcomers to learn, or experienced team members to complete quickly. label Jan 11, 2024
@@ -977,27 +971,8 @@ async function activateWithInstalledDistribution(
const testRunner = new TestRunner(dbm, cliServer);
ctx.subscriptions.push(testRunner);

let testManager: TestManagerBase | undefined = undefined;
if (isCanary()) {
Copy link
Contributor

Choose a reason for hiding this comment

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

So previously, only our canary users were using this feature? And with this change, all users will be using it. It's probably safe since most users of the testing feature are internal and therefore using canary.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes.

@dbartol dbartol merged commit b67efee into main Jan 11, 2024
14 checks passed
@dbartol dbartol deleted the dbartol/new-test-api branch January 11, 2024 21:48
koesie10 added a commit that referenced this pull request Jan 12, 2024
The custom Jest test runner was originally written to install the
required extensions for the CLI integration tests. This is no longer
necessary as of #3232, so
we can remove all code that deals with downloading VS Code and
installing extensions. The download of VS Code will now be handled by
the base `VSCodeTestRunner`.
@koesie10 koesie10 mentioned this pull request Jan 12, 2024
3 tasks
koesie10 added a commit that referenced this pull request Jan 12, 2024
The custom Jest test runner was originally written to install the
required extensions for the CLI integration tests. This is no longer
necessary as of #3232, so
we can remove all code that deals with downloading VS Code and
installing extensions. The download of VS Code will now be handled by
the base `VSCodeTestRunner`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Low A good task for newcomers to learn, or experienced team members to complete quickly.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate to new vscode testing APIs
2 participants