mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2024-12-25 21:07:18 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
5f3299e598
prysm-pulse/tools/analyzers
History
terence tsao 068f758f49
Code inspect - clean ups (#8445)
2021-02-12 17:04:45 -06:00
..
comparesame Code inspect - clean ups (#8445) 2021-02-12 17:04:45 -06:00
cryptorand Code inspect - clean ups (#8445) 2021-02-12 17:04:45 -06:00
errcheck Code inspect - clean ups (#8445) 2021-02-12 17:04:45 -06:00
featureconfig Code inspect - clean ups (#8445) 2021-02-12 17:04:45 -06:00
ineffassign Fix deepsource findings (#7457) 2020-10-08 08:36:47 +00:00
maligned Code inspect - clean ups (#8445) 2021-02-12 17:04:45 -06:00
nop Code inspect - clean ups (#8445) 2021-02-12 17:04:45 -06:00
properpermissions Code inspect - clean ups (#8445) 2021-02-12 17:04:45 -06:00
shadowpredecl Code inspect - clean ups (#8445) 2021-02-12 17:04:45 -06:00
slicedirect Code inspect - clean ups (#8445) 2021-02-12 17:04:45 -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/...