mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2025-01-10 19:51:20 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
5727d4eb8a
prysm-pulse/tools/analyzers
History
terence tsao 616081fbdd
Ran code inspect (#8387)
2021-02-03 10:59:17 -06:00
..
comparesame Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
cryptorand Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00
errcheck Rename getter functions to be idiomatic (#8320) 2021-01-25 21:27:30 +00:00
featureconfig Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
ineffassign Fix deepsource findings (#7457) 2020-10-08 08:36:47 +00:00
maligned Various code inspection resolutions (#7438) 2020-10-12 08:11:05 +00:00
nop Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00
properpermissions Prevent Usage of Stdlib File/Dir Writing With Static Analysis (#7685) 2020-11-09 14:27:03 -06:00
shadowpredecl Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
slicedirect Ran code inspect (#8387) 2021-02-03 10:59:17 -06:00
README.md Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00

README.md

Running analyzer unit tests

Analyzers' unit tests are ignored in bazel's build files, and therefore are not being triggered as part of the CI pipeline. Because of this they should be invoked manually when writing a new analyzer or making changes to an existing one. Otherwise, any issues will go unnoticed during the CI build.

The easiest way to run all unit tests for all analyzers is go test ./tools/analyzers/...