Security News
ESLint is Now Language-Agnostic: Linting JSON, Markdown, and Beyond
ESLint has added JSON and Markdown linting support with new officially-supported plugins, expanding its versatility beyond JavaScript.
vscode-test
Advanced tools
This module helps you test VS Code extensions.
Supported:
See ./sample for a runnable sample, with Azure Devops Pipelines configuration.
import * as path from 'path'
import { runTests, downloadAndUnzipVSCode } from 'vscode-test'
async function go() {
const extensionPath = path.resolve(__dirname, '../../')
const testRunnerPath = path.resolve(__dirname, './suite')
const testWorkspace = path.resolve(__dirname, '../../test-fixtures/fixture1')
/**
* Basic usage
*/
await runTests({
extensionPath,
testRunnerPath,
testWorkspace
})
const testRunnerPath2 = path.resolve(__dirname, './suite2')
const testWorkspace2 = path.resolve(__dirname, '../../test-fixtures/fixture2')
/**
* Running a second test suite
*/
await runTests({
extensionPath,
testRunnerPath: testRunnerPath2,
testWorkspace: testWorkspace2
})
/**
* Use 1.31.0 release for testing
*/
await runTests({
version: '1.31.0',
extensionPath,
testRunnerPath,
testWorkspace
})
/**
* Use Insiders release for testing
*/
await runTests({
version: 'insiders',
extensionPath,
testRunnerPath,
testWorkspace
})
/**
* Manually download VS Code 1.30.0 release for testing.
*/
const vscodeExecutablePath = await downloadAndUnzipVSCode('1.30.0')
await runTests({
vscodeExecutablePath,
extensionPath,
testRunnerPath,
testWorkspace
})
/**
* - Add additional launch flags for VS Code
* - Pass custom environment variables to test runner
*/
await runTests({
vscodeExecutablePath,
extensionPath,
testRunnerPath,
testWorkspace,
// This disables all extensions except the one being tested
additionalLaunchArgs: ['--disable-extensions'],
// Custom environment variables for test runner
testRunnerEnv: { foo: 'bar' }
})
/**
* Manually specify all launch flags for VS Code
*/
await runTests({
vscodeExecutablePath,
launchArgs: [
testWorkspace,
`--extensionDevelopmentPath=${extensionPath}`,
`--extensionTestsPath=${testRunnerPath}`
]
})
}
go()
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
0.4.3 | 2019-05-30
FAQs
![Test Status Badge](https://github.com/microsoft/vscode-test/workflows/Tests/badge.svg)
The npm package vscode-test receives a total of 8,425 weekly downloads. As such, vscode-test popularity was classified as popular.
We found that vscode-test demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
ESLint has added JSON and Markdown linting support with new officially-supported plugins, expanding its versatility beyond JavaScript.
Security News
Members Hub is conducting large-scale campaigns to artificially boost Discord server metrics, undermining community trust and platform integrity.
Security News
NIST has failed to meet its self-imposed deadline of clearing the NVD's backlog by the end of the fiscal year. Meanwhile, CVE's awaiting analysis have increased by 33% since June.