IntersectMBO/plutus

Add golden tests for the validation benchmarks

Open

#6,828 创建于 2025年2月10日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)Haskell (1,637 star) (511 fork)batch import
BenchmarksGood first issueInternalTeststatus: triagedtech debt

描述

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?

贡献者指南

技术栈
无
领域
testingperformance
议题类型
test
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
HaskellPlutus basicsgolden testing
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
First, examine how golden tests are implemented for the 'nofib' and 'bitwise' benchmarks in the same repository (e.g., look at the test files for those benchmarks). Understand the pattern: likely there is a script that outputs expected values and a test framework that compares against them. Then, apply the same pattern to the 'validation' benchmarks directory. The issue also mentions 'marlowe' so decide if it should be included. After writing the golden tests, run them to ensure they pass. If there are any failing tests, investigate whether the benchmarks produce deterministic output.