Visual Studio Code
CI/CD & Code
Open source
<What you get/>
Committed workspace configuration so the project works from a clean clone
Launch configurations for running and debugging tests from the editor
A handover environment identical to the one your developers already use
Extension and telemetry settings configured to your policy, not defaults
What it is
Visual Studio Code is where automation code is actually written. Its value to a QA practice is in the extensions — language servers, debuggers, test explorers and Git integration — which let an engineer author a test, step through a failure and review a colleague's pull request without leaving the editor.
How PerfectQA uses Visual Studio Code
VS Code is the editor most of our engineers and most client teams already share, which matters more than it sounds: when we hand a suite over, it opens in the environment your developers already use, with the same extensions and the same debugging experience. We standardise the workspace configuration and commit it — recommended extensions, formatter settings, launch configurations for running and debugging tests — so a developer joining the project gets a working setup from a clone rather than a setup document. Test runner integrations for Playwright, Cypress and the Java frameworks mean tests can be run and debugged from the file being edited, which is the single biggest factor in whether developers actually run tests before pushing. Where clients have restrictions on extensions or telemetry, we configure to their policy rather than assuming defaults.
Category
CI/CD & Code
In our stack
8 years
Projects
41 delivered
Where we’ve put it to work
Frequent questions
Does it matter what editor you use?
Will our developers need new extensions?
Can they debug tests from the editor?
We use a different IDE. Is that a problem?
Every stack is different
Tell us yours, and we’ll show you where this fits
