prysm-pulse/tools/analyzers
Victor Farazdagi 386b69f473
Fix comments (#8802)
* fix incorrect exported name in comments

* add comments to exported methods
2021-04-23 12:06:05 +00:00
..
comparesame Fix comments (#8802) 2021-04-23 12:06:05 +00:00
cryptorand Fix comments (#8802) 2021-04-23 12:06:05 +00: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 comments (#8802) 2021-04-23 12:06:05 +00:00
maligned Fix comments (#8802) 2021-04-23 12:06:05 +00:00
nop Fix comments (#8802) 2021-04-23 12:06:05 +00:00
properpermissions Fix comments (#8802) 2021-04-23 12:06:05 +00:00
shadowpredecl Fix comments (#8802) 2021-04-23 12:06:05 +00:00
slicedirect Fix comments (#8802) 2021-04-23 12:06:05 +00:00
README.md Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00

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/...