Accuracy testing: Difference between revisions
add CHIP-8 and revise text |
mNo edit summary |
||
| Line 10: | Line 10: | ||
* [https://github.com/c-sp/gameboy-test-roms GB] | * [https://github.com/c-sp/gameboy-test-roms GB] | ||
* [https://forums.mgba.io/showthread.php?tid=18 GBA] | * [https://forums.mgba.io/showthread.php?tid=18 GBA] | ||
* [https://github.com/Timendus/chip8-test-suite CHIP-8] | ;CHIP-8: | ||
* [https://github.com/Timendus/chip8-test-suite CHIP-8 test suite] (by Timendus) | |||
* [https://github.com/coornio/CubeChip-SDL/tree/master/test_roms Test roms] (by the CubeChip-SDL developer) | |||
==Demos== | ==Demos== | ||
Revision as of 21:17, 17 May 2024
Accuracy testing refers to any measure to determine accurate adherence to a given system's design. In emulation, accuracy tests are usually done in one of two ways.
Test ROMs
Some homebrew is designed to look for capabilities of the original system. For many, their express goal is to make sure emulators can replicate them. Some systems can have discrepancies across hardware versions that can also be detected in software. Test ROMs may also be able to catch those as well. Here are some test ROMs that can help measure the accuracy of an particular emulator:
- CHIP-8
- CHIP-8 test suite (by Timendus)
- Test roms (by the CubeChip-SDL developer)
Demos
Demos are media productions (homebrew) that make use of a computer or console to showcase a programmer's technical prestige or knowledge, and/or the system's capabilities. They are often used to test the accuracy of an emulator.