It is important to know what counts as a test in terms of licensing: depending on your plan, your account may limit the number of tests you can run each month.
Snyk keeps separate test counts and sets limits for each product (Snyk Open Source, Snyk Code, Snyk Container and Snyk IaC).
See the Plans page for more details of test limits per plan and product.
See Running tests for details on how to run a test in Snyk.
Counting SCM integration tests
For tests from source code management, we count by default the following:
- Daily recurring tests (see below).
- An automatic test whenever your dependencies change on your default branch.
- Whenever you create a pull request which changes those dependencies.
If you have a Dockerfile in your source code repos, the default settings will detect and scan it, but Dockerfiles count as a Snyk Container test, not a Snyk Open Source test.
Terraform and Kubernetes configuration files that are scanned from source code repositories are counted as Snyk Infrastructure as Code (Snyk IaC) tests.
For container scans from a registry or your Kubernetes cluster, we count the initial test and subsequent recurring tests, which occur once per day by default
Counting recurring tests
Snyk also periodically checks if your repo is affected by newly disclosed vulnerabilities.
Counting CLI tests
A test is counted for the relevant product each time you run one of the following commands:
- snyk test or snyk monitor (counted for Snyk Open Source)
- snyk container test or snyk container monitor (counted for Snyk Container)
- snyk iac test or snyk iac monitor (counted for Snyk IaC)
Counting app-based tests
A test is run when you add a new project or click the re-test button.
Counting API tests
Tests are counted when calls are made to the https://snyk.io/api/v1/test endpoint.