There should be no reason I need to compile my tests to an output before running a test, I should be able to point the runner directly to my .ts test files.
Normally with Mocha this is easily done by just adding require: ['@swc-node/register'] and specifying ts files for the search and everything works transparently. With VSCode E2E a little more work has to be done with a bootstrap as the entrypoint but also still totally doable:
https://github.com/pester/vscode-adapter/blob/707d6a0b9aa9b42bf5454daf7bcc92e1e580ef1b/test/runTestsInnerLoader.cjs#L5-L12
vscode-cli should be able to support this natively by allowing requires to be specified and have it be able to honor the related search paths.
There should be no reason I need to compile my tests to an output before running a test, I should be able to point the runner directly to my .ts test files.
Normally with Mocha this is easily done by just adding
require: ['@swc-node/register']and specifying ts files for the search and everything works transparently. With VSCode E2E a little more work has to be done with a bootstrap as the entrypoint but also still totally doable:https://github.com/pester/vscode-adapter/blob/707d6a0b9aa9b42bf5454daf7bcc92e1e580ef1b/test/runTestsInnerLoader.cjs#L5-L12
vscode-clishould be able to support this natively by allowing requires to be specified and have it be able to honor the related search paths.