smoke-tests Skill
Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI. Published by microsoft in vscode.
Decision snapshot
Is this a fit?
Browser automation, Testing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
1 month ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is smoke-tests Skill?
Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI. Published by microsoft in vscode. 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
- Browser automation
- Testing
- Browser automation use cases
- Testing use cases
Declared skill metadata
- Source file: .github/skills/smoke-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 smoke-tests Skill
- Use it for browser automation.
- Use it for testing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vscode
- Skill file: .github/skills/smoke-tests/SKILL.md
What it does
Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky smoke tests in CI.
Skill instructions
Running Smoke Tests Smoke tests live in test/smoke/ and drive a full VS Code instance (Electron, web, or remote) through end-to-end user flows. Scripts - npm run smoketest — compiles the smoke tests first (test/smoke), then runs them. - npm run smoketest-no-compile — runs the already-compiled smoke tests. CI uses this after an explicit compile step. Both forward extra arguments after -- to the runner (test/smoke/test/index.js). Common options | Option | Description | |--------|-------------| | -g <pattern (alias -f) | Grep filter on test/suite titles (mocha grep). | | --build <path | Run against a packaged build instead of the compiled-from-source dev build. | | --tracing | Capture Playwright traces (and screenshots on failure). | | --web | Run the browser smoke tests instead of Electron. | | --headless | Headless browser (used with --web). | | --remote | Run the remote smoke tests. | bash Run everything (Electron, from source) npm run smoketest Run only a subset of suites by name, wit
Verified compatibility and discovery
Frequently asked questions
What is smoke-tests?
smoke-tests is a open-source AI agent skill with Copy skill directory. Use when running VS Code smoke tests or working on smoke-test CI steps. Covers npm run smoketest / smoketest-no-compile, grep filtering tests, and a temporary repeat-loop technique for tracking down flaky.
Who is smoke-tests best for?
smoke-tests is best for reusing agent instructions, scripts, and references, browser automation workflows, testing workflows.
How do I install smoke-tests?
Install or run smoke-tests using Copy skill directory. Check smoke-tests for the latest setup command.
Is smoke-tests actively maintained?
smoke-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.
