Testifly for VS Code
Find the blast radius of your local changes while in your IDE, before you ship
them to production.
Testifly shows which tests your changes affect, and
you run them on your machine without leaving the editor. You do not need to
download any test code or build it. The extension does all of it for you,
automatically.
What it does
- Analyze your changes. Run Testifly: Analyze Changes. The extension
reads your uncommitted changes and asks Testifly which of your tests are
affected. You watch the analysis work in the Testify sidebar, and then you
see its answer.
- Run tests on your machine. Press Run on a suggested test, or run
several at once. The results appear in the sidebar. Cancel a run at any time
with Testifly: Cancel Test Run.
Running tests locally
Tests run in a browser on your machine, using a Node.js you already have.
- The first run asks before it downloads the Testifly test runner (about 300 MB).
This happens once per runner version.
- The first run also asks which environment to use and which test user to log in
as. You can change them anytime in the Settings panel in the Testify sidebar.
- Logins of your test users are saved for 15 minutes, so a second run does not
sign in again. They are stored encrypted. Delete them with
Testifly: Forget Saved Logins. Testifly: Change Test User makes the
next run ask for a user again.
- A test run can use environments that exist only on your machine, for example
http://localhost:3000. Add them in the Settings panel.
Signing in, in a bit more detail
Sign-in uses the standard OAuth authorization-code flow with PKCE. The extension
never sees your password. Your session is stored in VS Code's own encrypted
secret storage - the OS keychain - and never in your settings or your project.
Test-user passwords are stored there too.
Sign out any time from the Accounts menu, or with Testifly: Sign Out.
Working over Remote SSH, WSL, a dev container or Codespaces is supported for
sign-in: the redirect comes back through a vscode:// link rather than a local
port. If your machine blocks custom URI schemes, set
testifly.useLoopbackRedirect to true in your settings.
Settings
Most of these are easier to change in the Settings panel in the Testifly
side bar.
| Setting |
What it is for |
testifly.environment |
The environment your test runs use. Empty means the first run asks. |
testifly.localEnvironments |
Environments that exist only on your machine: a name and the address of the app. |
testifly.parallelRuns |
How many tests run at the same time (1 to 8). Each one opens its own browser. |
testifly.runHeadless |
Run the browser without a window. Turn it off to watch the test. |
testifly.nodePath |
The Node.js that runs your tests. node uses the one on your PATH. |
testifly.serverUrl |
Point the extension at a staging or self-hosted Testifly. |
Requirements
- VS Code 1.86 or newer.
- A Testifly account.
- Node.js on your machine for local test runs. The extension tells you when the
version is too old.