♻️ parameterize tests

[jvdd]

Closes #30, should in general "remove" a lot of duplicate unit test code :)

• parameterize unit tests
  • limit duplicate code using generic functions from test_utils.rs
  • place unit tests at the bottom of each file (instead of between the code - at the end of the sub-mods)
• parameterize integration tests

Decided to keep the tests in each file as this seems the best practice in Rust - see quote from the book

You’ll put unit tests in the src directory in each file with the code that they’re testing. The convention is to create a module named tests in each file to contain the test functions and to annotate the module with cfg(test).

However, I placed the tests at the bottom of each file (which should significantly enhance the code readability) + limited duplication of tests through using parameterization & centralized generic code (in test_utils.rs).

Long story short, this PR should improve the maintainability & flexibility of the tests!

[codspeed-hq]

CodSpeed Performance Report

Merging #31 improve_tests (6975eaf) will not alter performances.

Summary

🔥 0 improvements
❌ 0 regressions
✅ 52 untouched benchmarks

🆕 0 new benchmarks
⁉️ 0 dropped benchmarks