@bobomb in case we don't get to meet this week, we should try and get some of our ideas down on this issue.
Today at lunch you mentioned you want to generalize the test setup for instructions with zero-page addressing.
I've recently been thinking about something related. I noticed a lot of our unit tests re-use state from prior tests of the same instruction. Maybe we should be calling cpu.powerOn() or cpu.reset() in between tests, or perhaps writing a custom function for each unit test that "resets" the cpu, RAM and console.
Topics to Discuss
@bobomb in case we don't get to meet this week, we should try and get some of our ideas down on this issue.
Today at lunch you mentioned you want to generalize the test setup for instructions with zero-page addressing.
I've recently been thinking about something related. I noticed a lot of our unit tests re-use state from prior tests of the same instruction. Maybe we should be calling
cpu.powerOn()orcpu.reset()in between tests, or perhaps writing a custom function for each unit test that "resets" the cpu, RAM and console.Topics to Discuss