-
I'm investigating property-based testing for Oxen projects, I think libsession-util is a good start, and `session::bt::merge` is a good toy study case.
To use property-based testing, the first step…
-
| | |
|--------------------|----|
| Bugzilla Link | [PR30540](https://bugs.llvm.org/show_bug.cgi?id=30540) |
| Status | NEW |
| Importance | P normal |
|…
-
A gripe I've had for a while is that the default runs of 100 is way too low to get decent coverage for most scenarios, and in my experience is pretty low for most test suites.
I recommend usually …
-
Greetings Halide developers and contributors,
We’re reaching out because your project is an important part of the open source ecosystem, and we’d like to invite you to integrate with our [fuzzing](…
-
#586 removed hypothesis, but left the door open for re-integrating it if we can address a couple of issues:
- remove random generation from gating PR CI
- ideally, run any random stuff in a ti…
-
Capturing it here since Twitter is not the best place for research discussions.
From - Brandon Falk - @gamozolabs - Aug 8 (https://twitter.com/gamozolabs/status/1292324287324381184)
---------
L…
-
### Is your feature request related to a problem? Please describe.
Failure of fuzz tests requires additional attention overheads of developers (1 for check what's the problem, 1 for rerun CI) who may…
-
Currently go-fuzz mutates and supplies to a test a byte slice, however there are cases when a test needs more complex, structured input. For example, a regexp test could accept 3 strings (regexp, repl…
-
*Originally reported by* **Thomas Pansino (Bitbucket: [tpansino](https://bitbucket.org/tpansino), GitHub: [tpansino](https://github.com/tpansino))**
----------------------------------------
Coming f…
-
The current Fuzz function signature is
```go
func FuzzSomething(b []byte) int
```
I think we should migrate it to something more like:
```go
import fuzz "github.com/dvyukov/go-fuzz"
fun…