Running tests

You can use Snyk to test your code in different ways:
​Run tests manually: using the Snyk CLI, the Snyk Web UI, and the Snyk API.
​Run tests automatically: on a recurring basis, or when a relevant repo change is made.
Tests may be limited on your account; see What counts as a test? for more information.
Run tests manually
Run tests with the CLI
With the Snyk CLI you can use the following commands:
Scan open-source code with snyk test.
Scan application code with snyk code test.
Scan container images with snyk container test.
Scan Infrastructure as Code (IaC) files with snyk iac test.
See Getting started with the CLI for details.
Run tests with the Snyk Web UI
A test is run when you import a Snyk Project (see Import a Project), or click the Retest now button on a Project in the Overview tab.
See Exploring the Snyk Web UI for details.
Run tests with the API
Tests are counted when calls are made to the https://snyk.io/api/v1/test endpoint.
See API documentation for details.
Run tests automatically
Snyk provides automatic scanning functions with recurring tests, allowing you to catch new vulnerabilities automatically. After you import a project, Snyk automatically runs periodic checks to see if your code is affected by newly disclosed vulnerabilities.
Test frequency is set to daily by default. To change frequency, go to either the Usage page (see Usage page details) or the project Settings page (see View project settings).
Snyk monitor
Use the snyk monitor CLI command to create a snapshot of a project on the Snyk website that will be continuously monitored for new vulnerabilities.
See Monitor your projects at regular intervals for details.
PR Checks
Snyk can be enabled to scan every Pull Request (PR) submitted on your monitored repositories for vulnerabilities, to help prevent new vulnerabilities being added to your codebase.

Exploring the Snyk Web UI

Implementing Snyk: Free and Team plan users

Last modified 20h ago