-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Test Explorer #99838
Comments
I disagree. Doing that would add bloat for people who don't need it. |
I agree. But not for a specific testing framework It is abstracted into a general purpose, similar to view Such different test framework extensions can create test legends interface TestCase {
label: string
location: {
file: Uri
start: number
end: number
}
}
export async function activate(
context: vscode.ExtensionContext
): Promise<void> {
vscode.test.add({
label: 'testxxx',
location: {xxxxx}
})
// defined how to run this test case
vscode.test.registry(function (test: TestCase) {
})
// defined how to run all test case
vscode.test.registryRunAll(function (test: TestCase) {
// defined how to run this test case
})
} Then add a test case in the sidebar Each test case added by the extension has a different tree view in sidebar |
The idea is not to have it in VS Code by default, but rather just having such extension exist for people who need it - so there would be not bloating |
Yes, I just meant to give an example. It should support popular test automation frameworks out of the box ideally. |
Then I'm not clear why you asked for an official one. This one seems popular and well rated. https://marketplace.visualstudio.com/items?itemName=hbenl.vscode-test-explorer But it seems you already tried it and had a problem - hbenl/vscode-test-explorer#108 Maybe try this Test Adapter extension, which seems to be actively developed, and allows issues to be raised: https://marketplace.visualstudio.com/items?itemName=kavod-io.vscode-jest-test-adapter |
/duplicate #9505 |
VS Code should have an official extension for a test explorer, that supports Jest, Jest-Cucumber and automation tests of PlayWright out of the box.
The text was updated successfully, but these errors were encountered: