GameboyCPUTests VS ProcessorTests

Also check out adtennant’s tests; they should allow you to figure out which instructions are already complete and which still need with in isolation of one another.

You should check out adtennant’s tests, which can be used to test one instruction at a time, at cycle-by-cycle precision. Even if you’re not interested in the cycle breakdowns, you can test each instruction’s length independently of all others.

Here you go: https://github.com/adtennant/gameboy-test-data

If you want to test processor only, use https://github.com/TomHarte/ProcessorTests/tree/main/6502

Unit tests! Here are mine.

As part of development of JSMoo, my multi-system emulator, I implemented a series of 1,000+ tests per possible valid opcode (including undocumented opcodes). These tests are inspired by the amazing work of Tomas Harte at https://github.com/TomHarte/ProcessorTests , and after some people exercise them a bit I'd like it to be integrated there if he agrees.

I have added slightly more than a million 68000 test cases to my processor test collection.

Verify your 65816 and spc700 cores with this: https://github.com/TomHarte/ProcessorTests I contributed the spc700 tests and worked to improve and validate the 65816 tests. Neither core has had a single issue in any game so far.

I've yet really to go to town on producing public 68000 resources, but my limited contribution is: a complete list of [mostly-]decoded official 68000 instructions.