<d1b2>
<Flux> Or the start of Skynet. The bots would have a plausible excuse while they consolidated their power! 🤖
mindw0rk has quit [Read error: Connection reset by peer]
mindw0rk has joined #amaranth-lang
miek has joined #amaranth-lang
jevinskie[m] has joined #amaranth-lang
mindw0rk has quit [Read error: Connection reset by peer]
mindw0rk has joined #amaranth-lang
jess has quit [Quit: Lost terminal]
jess has joined #amaranth-lang
mindw0rk has quit [Read error: Connection reset by peer]
mindw0rk has joined #amaranth-lang
<d1b2>
<jer_emy> i am writing a test bench in which I would like to basically do the following things: 1. Input some data, 2. clock a bunch of times 3. check result 4. Reset, change input data and GOTO 1. What is the correct way to do this? Should I be re-creating the Simulator object for each run?
<adamgreig[m]>
it's pretty cheap to, so yea, i'd usually have a pytest test function parametrized by the different data, and each test run creates the simulator, feeds the data, checks the output