Advanced testing for `rustworkx-core`

[IvanIsCoding]

What is the expected enhancement?

Currently, we test rustworkx with unit tests in Python and we test rustworkx-core with unit tests and doctests in Rust.

Because rustworkx-core is written completely in Rust and has a simpler testing setup (no need for tools that understand two languages), we could run some more advanced tests for it:

• Miri: find undefined behaviour in Rust
• Mutation Testing: use cargo-mutants to find lines of code that are covered by tests but do not cause test failures
• Fuzzing: use cargo-fuzz, most likely to find panics
• Property-based testing: use quickcheck to generate randomized tests that are stronger

[IvanIsCoding]

Also, Miri is known to cause issues to some dependencies we have in Cargo.lock so check https://github.com/Qiskit/qiskit/blob/e4048320db76dcd738a36f5376628855d20e97b3/.github/workflows/miri.yml#L28 to see some patches Qiskit uses.

[Krishn1412]

Hey @IvanIsCoding , can I pick this one up and add the tests?

[IvanIsCoding]

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 rust nightly version, C++ toolchain and builds the fuzzer
• Join https://github.com/google/oss-fuzz maybe?

[Krishn1412]

should I add more fuzz targets (and work on the other action items you mentioned) or go ahead with building a basic structure for the other types of tests?

[IvanIsCoding]

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

[Krishn1412]

Got it!

[Krishn1412]

Hey @IvanIsCoding, now that basic fuzzing is done, should now focus on adding other kinds of tests?