Ivan Carvalho

Congratulations, after #1407 was merged we have our first fuzz target. Some action items: * add more fuzzers for popular methods * add a GithubActions workflows that installed a pinned...

You can focus on adding more targets. I think that is the harder part. I will figure out how to run it

@Krishn1412 I think the next best thing would be property based tests with `quickcheck`. I will try to find some examples later from other packages.

It looks like `petgraph` already implements some `quickcheck` utilities we could use: https://github.com/petgraph/petgraph/blob/8439ee24335b8ffd20fb6c44ec3fcd2cc108917c/src/quickcheck.rs#L29

> I had a doubt here. If we use petgraph's quickcheck utilities to create arbitrary graphs with random inputs and ensure our properties hold, isn't that similar to fuzzing? Excellent...

@Krishn1412 I think your work is complete! We have a good coverage now. For testing tickets, there’s #1316. For non-testing tickets, #1466 and #804 can be interesting things to work...

@Krishn1412 sounds good to me! Feel free to ping

So I tried following: https://pyodide.org/en/stable/usage/building-and-testing-packages.html I had to install `emsdk 4.0.8.`, `pyodide-build==0.30.1`, `rustc 1.88.0-nightly (00095b3da 2025-04-03)` I got this error: https://pastebin.com/TaT892sU. So yeah, I'd like to keep this build outside...

@sorin-bolos how did you setup the SDK to build the version from your PR? I might need some help here

Maybe I should try using the version pinned here: https://github.com/pyodide/pyodide-build/blob/7126c5f1bd56ed7f40ce29cbcbe588267a42434c/pyodide_build/config.py#L240C24-L240C42