kunwardeep / paralleltestLinks
Linter to check if your tests have been marked as parallel correctly
☆58Updated 4 months ago
Alternatives and similar repositories for paralleltest
Users that are interested in paralleltest are comparing it to the libraries listed below
Sorting:
- A linter that handles struct tags.☆54Updated 4 months ago
- tparallel finds inappropriate usage of `t.Parallel()` method in your Go test codes☆26Updated last year
- intrange is a program for checking for loops that could use the Go 1.22 integer range feature.☆34Updated this week
- A simple terminal UI for Go linters☆81Updated 4 years ago
- An analyzer that checks for pointers to enclosing loop variables.☆38Updated last year
- Golang linter that encourages you to use a separate _test package☆51Updated last week
- Go linter to detect erroneous multiplication of duration values☆48Updated last year
- The Golang linter that checks that there is no simultaneous return of `nil` error and an invalid value.☆73Updated 2 weeks ago
- 🚔 Enforce field tags in (un)marshaled structs☆38Updated this week
- nakedret is a Go static analysis tool to find naked returns in functions greater than a specified function length.☆131Updated 2 weeks ago
- ☆54Updated 10 months ago
- golang linter to detect named returns☆28Updated this week
- Golang linter to use strconv☆40Updated 5 months ago
- Minimal environment variable parser for Go☆52Updated this week
- Simple oauth prompting☆28Updated last year
- copyloopvar is a linter detects places where loop variables are copied.☆22Updated 7 months ago
- misspelled word linter for Go comments, string literals and embedded files☆42Updated 4 months ago
- Accept Interfaces, Return Concrete Types☆74Updated this week
- Analyzer: fourcetypeassert finds type assertions which did forcely☆43Updated 6 months ago
- Go linter for forbidding identifiers☆148Updated 6 months ago
- Extension handlers for the slog library☆43Updated last year
- Linter that confirms DB rows and statements are closed properly.☆89Updated 3 months ago
- Simple linter to check that your code does not contain non-ASCII identifiers☆27Updated last week
- ☆98Updated 7 months ago
- ☆121Updated last year
- Golang linter to check the errors handling expressions☆55Updated 4 years ago
- Go analyzer checking that the length of a variable's name matches its usage scope☆22Updated 2 years ago
- Syntax-aware Go code search, based on the mvdan/gogrep☆41Updated 2 years ago
- A linter to ensure that slices are not initialized with non-zero length☆76Updated 6 months ago
- ☆110Updated this week