mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2025-01-05 09:14:28 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
c7d01fd73c
prysm-pulse/tools/analyzers
History
Victor Farazdagi ecfdb354a7
Add new static analyzer: ineffassign (#7413) 
* test defined

* first working impl

* register analyzer

* cleanup

* removes unused code

* secure rand in slasher/detection/testing

* Updates test

* fixes ineffassign type checks

* one more

Co-authored-by: Preston Van Loon <preston@prysmaticlabs.com>
2020-10-02 23:56:18 +03: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 Apply testutils assertions: final cleanup (#7003) 2020-08-25 15:23:06 +00:00
featureconfig Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
ineffassign Add new static analyzer: ineffassign (#7413) 2020-10-02 23:56:18 +03:00
maligned Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
nop Fix failing static analyzer tests (#7363) 2020-09-29 11:29:40 +00:00
shadowpredecl Package-level comments for static analyzers (#7332) 2020-09-24 10:25:55 +00:00
slicedirect Unnecessary Slice-to-Slice Conversion analyzer (#7321) 2020-09-23 16:14:34 +00: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/...