Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

testing: link to fuzzing guide and more details on runtime #51032

Open
ronaldpetty opened this issue Feb 6, 2022 · 4 comments
Open

testing: link to fuzzing guide and more details on runtime #51032

ronaldpetty opened this issue Feb 6, 2022 · 4 comments
Labels
Documentation fuzz NeedsFix
Milestone

Comments

@ronaldpetty
Copy link

@ronaldpetty ronaldpetty commented Feb 6, 2022

$ go version
go version go1.18beta2 darwin/amd64

The go doc testing and this page https://pkg.go.dev/testing@master#hdr-Fuzzing still are pointing to #48255. They mention:

TODO(#48255): write and link to documentation that will be helpful to users who are unfamiliar with fuzzing.

Some details such as:

  • why does it run long (∞) and how to stop
  • maybe example quickly shows it 'finding' evil params (the current one ran for 30+ minutes and nothing found)
    • just to show what happens when it does, else you just see endless processing

I was asked to create new ticket (versus comment in #48255).

Looking forward to using it, and thanks for the hard work.

@ianlancetaylor
Copy link
Contributor

@ianlancetaylor ianlancetaylor commented Feb 6, 2022

@seankhliao seankhliao changed the title Guide for Fuzzing testing: link to fuzzing guide and more details on runtime Feb 6, 2022
@katiehockman
Copy link
Contributor

@katiehockman katiehockman commented Feb 7, 2022

https://go-review.googlesource.com/c/go/+/383415 fixes the TODO in the testing package 👍

@katiehockman katiehockman added the fuzz label Feb 7, 2022
@katiehockman katiehockman added this to the Backlog milestone Feb 7, 2022
@gopherbot
Copy link

@gopherbot gopherbot commented Feb 7, 2022

Change https://golang.org/cl/383454 mentions this issue: _content/doc/fuzz: describe the nature of a failure

@ronaldpetty
Copy link
Author

@ronaldpetty ronaldpetty commented Feb 7, 2022

Thank you @katiehockman . I have solved all my questions after seeing that link (and related ones). Cool feature.

@cherrymui cherrymui added the NeedsFix label Feb 8, 2022
gopherbot pushed a commit to golang/website that referenced this issue Feb 8, 2022
Updates golang/go#51032

Change-Id: Iec7965f8d2823e7918967e0fae8425e0b1cc615e
Reviewed-on: https://go-review.googlesource.com/c/website/+/383454
Run-TryBot: Katie Hockman <katie@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Roland Shoemaker <bracewell@google.com>
Trust: DO NOT USE <katiehockman@google.com>
Run-TryBot: DO NOT USE <katiehockman@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation fuzz NeedsFix
Projects
None yet
Development

No branches or pull requests

5 participants