IntersectMBO / IntersectMBO/plutus
Add golden tests for the validation benchmarks
Open
Benchmarks
Good first issue
Internal
status: triaged
tech debt
Test
- Dominant language
- Haskell
- Stars
- 1.6k
- Forks
- 508
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 22
Description
Currently the `validation` benchmarks don't seem to have any golden tests ensuring that what scripts evaluate to doesn't change. Unlike e.g. `nofib` or `bitwise` benchmarks (and `lists` ones have some property tests). We should fix that, otherwise an apparent optimization might as well turn out to be a bug.
Same about `marlowe`?
Contributor guide
Assessment
This issue has not been assessed yet.