run-smoke-tests

To run smoke tests for a VS Code extension, execute automated scenarios within a live VS Code instance to validate activation, command registration, and API availability under real-world conditions.

Integration testing using a live VS Code instance catches activation and API issues early by simulating actual user interactions, whereas mocked tests often miss environment-specific extension failures.

Yes, automated smoke tests verify VS Code extension activation and command registration by executing scenarios that check if the extension loads and its commands work without errors.

Run smoke tests after updating extension activation logic or adding new commands to confirm core features remain operational in a real VS Code environment before committing or deploying.

Running smoke tests inside a live VS Code instance validates real-world integration but may execute slower than mocked unit tests due to the overhead of loading the full environment.

Yes, run-smoke-tests verifies that exported APIs work as expected by simulating real-world user interactions and testing API availability within the live VS Code environment.