Skip to content

Consider migrating to VSCode's integration test scaffolding #3737

Open
@firelizzard18

Description

@firelizzard18

vscode-go uses extension/test/runTest.ts to execute integration tests. Consider migrating to @vscode/test-cli and .vscode-test.js (or .mjs/.cjs). Looking at runTest.ts, I think it should be feasible. The only part I see that might be tricky is the two separate test runs, other than that everything looks pretty straightforward. I am interested in trying this myself.

vscode-go's integration test setup is a little janky. It executes two different sets of tests (two calls to runTest); if all the tests in the second run pass, it's not obvious whether any tests in the first run failed because I have to scroll to the ~middle of the output (which is quite long) to find the report from the first run. Also the Testing UI is very convenient but vscode-go's setup seems to confuse it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    chore/testingissues related to bugs in test, CI setup

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions