backend-tests Skill
Use when writing unit tests under test/unit-tests/backend/.test.ts that run in Node with Mocha+Chai and no VS Code API. For pure logic: parsers, helpers, env merging. Triggers: "backend test", "unit test", "mocha test without vscode". Published by microsoft in vscode-cmake-tools.
Decision snapshot
Is this a fit?
Testing, Data analysis, Design and media, Writing
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is backend-tests Skill?
Use when writing unit tests under test/unit-tests/backend/.test.ts that run in Node with Mocha+Chai and no VS Code API. For pure logic: parsers, helpers, env merging. Triggers: "backend test", "unit test", "mocha test without vscode". Published by microsoft in vscode-cmake-tools. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Data analysis
- Design and media
- Writing
- Testing use cases
Declared skill metadata
- Source file: .github/skills/backend-tests/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use backend-tests Skill
- Use it for testing.
- Use it for data analysis.
- Use it for design and media.
- Use it for writing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode-cmake-tools
- Skill file: .github/skills/backend-tests/SKILL.md
What it does
Use when writing unit tests under test/unit-tests/backend/.test.ts that run in Node with Mocha+Chai and no VS Code API. For pure logic: parsers, helpers, env merging. Triggers: "backend test", "unit test", "mocha test without vscode".
Skill instructions
Writing Backend Tests Recipe for adding backend (unit) tests that run without VS Code. When to use backend tests Use backend tests for pure logic that has no VS Code UI interaction. They are the fastest feedback loop — no Extension Host, no display server, just Node + Mocha. Good candidates: string manipulation, path logic, parsers, encoding, variable expansion, data-structure helpers, environment merging. Not suitable for: anything that calls vscode.window., vscode.workspace. beyond getConfiguration(), or depends on an active editor. --- File location test/unit-tests/backend/<name.test.ts --- Import strategy — decision tree Module has NO transitive vscode dependency Import directly via the @cmt/ path alias. typescript // encoding.test.ts — encodingUtils has no vscode imports import { isValidUtf8 } from '@cmt/encodingUtils'; Module transitively imports vscode Mirror the pure function logic inline in the test file. Do not import the source module — it will fail because vscode cannot be
Verified compatibility and discovery
Frequently asked questions
What is backend-tests?
backend-tests is a open-source AI agent skill with Copy skill directory. Use when writing unit tests under test/unit-tests/backend/.test.ts that run in Node with Mocha+Chai and no VS Code API. For pure logic: parsers, helpers, env merging.
Who is backend-tests best for?
backend-tests is best for reusing agent instructions, scripts, and references, testing workflows, data analysis workflows, design and media workflows.
How do I install backend-tests?
Install or run backend-tests using Copy skill directory. Check backend-tests for the latest setup command.
Is backend-tests actively maintained?
backend-tests may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
