mirror/prysm-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/prysm-pulse.git synced 2025-01-03 08:37:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
b5a913d862
prysm-pulse/tools/analyzers
History
Preston Van Loon d4e6ce6998
Fix deepsource findings (#7457) 
* remove unused code

* Incomplete condition fix

* club append to single call

* anti-pattern fix 'should use for range instead of for { select {} }'

* use strings.ReplaceAll

* replace `len(parts[0]) == 0` with `parts[0] == ""`

Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com>
2020-10-08 08:36:47 +00: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 Fix deepsource findings (#7457) 2020-10-08 08:36:47 +00: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/...