During all these years I've been working on my emulator I've tried quite a few test-ROMs that some skilled people have written.
What they all seem to have in common is lack of human understandable-documentation. Tests may fail but I usually haven't got a clue what the problem is all about.
Yesterday I tried a bit with "NESStress". It actually comes with a textfile describing the tests (in a line or two), but it really doesn't tell me what's wrong with my emulator. So, I noticed I failed a few tests, but I simply don't understand what's wrong so I don't know what to fix.
What I really want is a detailed (but still readable) description of the tests, what they do, and the expected end result.
For example, documentation concerning a frame/vbl/timing-test should clearly state what it expects to pass the test. Which scanline is expected? Which state should all flags have etc.
I am not sure about the purpose of this post, but perhaps an idea for possible future test-ROM coders.
What do you think? Am I the only one that thinks the tests are usually somewhat hard to understand?
What they all seem to have in common is lack of human understandable-documentation. Tests may fail but I usually haven't got a clue what the problem is all about.
Yesterday I tried a bit with "NESStress". It actually comes with a textfile describing the tests (in a line or two), but it really doesn't tell me what's wrong with my emulator. So, I noticed I failed a few tests, but I simply don't understand what's wrong so I don't know what to fix.
What I really want is a detailed (but still readable) description of the tests, what they do, and the expected end result.
For example, documentation concerning a frame/vbl/timing-test should clearly state what it expects to pass the test. Which scanline is expected? Which state should all flags have etc.
I am not sure about the purpose of this post, but perhaps an idea for possible future test-ROM coders.
What do you think? Am I the only one that thinks the tests are usually somewhat hard to understand?