check | go-fuzz | |
---|---|---|
3 | 10 | |
1,039 | 4,707 | |
1.8% | - | |
0.0 | 5.2 | |
over 1 year ago | 3 months ago | |
C | Go | |
GNU Lesser General Public License v3.0 only | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
check
Posts with mentions or reviews of check.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-21.
-
How do you ensure your logic is correct for various inputs? Unit tests? Assert?
check
-
Unit testing for stdout/printf
I am using libcheck to write my unit tests in C. Unfortunately the library doesn't provide an easy way to verify what go written to stdout. I have a function that writes specific character sequences to the terminal using printf. The function doesn't return anything.
-
A rofi base shortcut helper (use remontoire configuration)
Running ./configure, make and make install inside the rofi-1.6.1 directory should go quite smoothly. If the configure complains that it requires the latest version of "check" (a utility that tests the source code for scripting errors) it can be downloaded from https://github.com/libcheck/check Note that check also has a few dependencies that have to be resolved.
go-fuzz
Posts with mentions or reviews of go-fuzz.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-06-10.
-
Fuzzing in Go
I used this method successfully for my qjson package . It accepts as input a human readable json. It detected a condition I forgot to check in a few minutes. I used the go fuzzer go-fuzz from Dmitry Vyukov. Check the impressive list of trophies at the end of the README. These are bugs found by the fuzzer.
-
Go Fuzz Testing – The Basics
It does instrumented fuzzing. The older https://github.com/dvyukov/go-fuzz would rewrite your sources to inject the instrumentation and pass the rewritten sources to the compiler, but it didn't really work with Go modules. This is something that probably makes sense to integrate with the compiler toolchain, same as `go test`'s coverage testing.
-
naive question regarding Fuzz testing de/serialisation
And another Go-Fuzz
-
Go Fuzzing
Anyone seen good articles on converting go-fuzz tests to native fuzzing? Specifics on the new corpus format and a converter from go-fuzz would be really useful.
It’s great to hear that the fuzzer is built on go-fuzz so hopefully the conversion process won’t be too bad: https://github.com/dvyukov/go-fuzz/issues/329
-
Go: Fuzzing Is Beta Ready
> it shows the limitations of the language that you can't just build this inside the language.
Not sure why you'd make that assumption. https://github.com/dvyukov/go-fuzz
-
goccy/go-json: A super fast JSON library fully compatible with encoding/json
Rather than explore the specific issues my tests found, I started playing with running https://github.com/dvyukov/go-fuzz against go-json which seems to have fairly quickly found some issues. I've opened https://github.com/goccy/go-json/issues/174 to start the conversation about how you want to proceed here.
-
Fuzz Test Proposal just accepted
You can check the go-fuzz's trophies here.
-
SQLFuzz made easy to load huge amount of test data into SQL databases
Maybe you can add support for using a fuzzer like https://github.com/dvyukov/go-fuzz or https://github.com/google/gofuzz
-
proposal: testing: add fuzz test support
I recently stumbled upon go-fuzz (that is also linked in the proposal). I'm amazed how fuzzing has made the go toolchain stronger and integrated this technique into some of our CI/CD pipelines for continuous testing. Having native fuzzy testing support (not just in go) would be great.
-
Add experimental fuzz test support for Go 1.17
Go tests and benchmarks are so easy to write and run: just add TestFoo and BenchmarkFoo functions to a bar_test.go file, and "go test" does the rest. It's currently doable, but it requires a 3rd party library (go-fuzz) and a bit of fluffing around. This will make fuzz testing an equally first-class citizen with standard Go tooling (just add FuzzFoo), and as such we'll probably see a lot more people testing with fuzzing.
I used go-fuzz in GoAWK and it found several bugs (see https://benhoyt.com/writings/goawk/#fuzz-testing), and almost everyone who's done fuzz testing has similar reports. Certainly go-fuzz has found many, many bugs in Go itself: https://github.com/dvyukov/go-fuzz#trophies
For what it's worth, I wrote an article for LWN about the upcoming support for built-in fuzzing in Go: https://lwn.net/Articles/829242/ (of course, if you want full details, read the full proposal).