mooneye-test-suite VS GameboyCPUTests

The thing about the Game Boy (or most consoles, really, but especially the Game Boy since it uses a custom CPU) is that we don't know all the details. People have had to reverse engineer it to figure stuff out. /u/gekkio is one of the people doing that work, and his technical reference and test suite are the (ongoing) results of that.

I tested it with the classic dmg-acid2 test rom and another rom called sprite_priority.gb which is part of the Mooneye Test Suite.

I am working on my Game Boy emulator and I'm trying to get the timer to work with mooneyes acceptance tests. Take this one as an example.

The mooneye-gb test suite has very specific tests for the timer (maybe too precise, they require emulating every little detail — but if you want that kind of accuracy, way to go)

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