Runs tests for Leiningen projects.
Patterns to include in reports.
Note: The input patterns are not applied when running lein test since lein test performs a regular build to run tests and the files excluded by the patterns may be required for the build. Therefore, the files excluded by the patterns are always processed and you may even see logs related to the excluded files in the job console. However, Inspecode eventually ignores any issues detected on the excluded files when generating job reports.
Patterns to exclude from reports.
Note: Just like
input:, the ignore patterns are not applied when running lein test.
Amount of CPU. The default machine has
0.75 CPU with
2880 MiB RAM.
Inspecode configures the maximum heap size (
-Xmx) of the Java virtual machine (JVM) by applying a custom profile with
:jvm-opts according to this value.
240 MiB RAM for system, and makes the rest of RAM available to JVM for heap allocation.
-Xmx2640m is specified by default (for
-Xmx5520m is specified for
No tool specific severity levels are available.
Note: The incremental analysis cannot be supported for lein test. This is because lein test performs a regular build with requiring all build dependencies and the results on unchanged files can be affected by changed files.
With default options:
inspecode: lein-test: default
With custom machine:
inspecode: lein-test: machine: cpu: 1.5 # 1.5 CPU, 5760 MiB RAM
If there are multiple Leiningen projects (
project.clj files) in single repository, Inspecode detects them and then runs
lein test for each project.
Before running the tool, Inspecode automatically searches your repository for
project.clj files and runs
lein deps at each directory where
project.clj is placed.