https://wiki.nesdev.com/w/index.php/Emulator_tests

It could run these ROMs and actually check the output somehow - perhaps either by checking memory values, or a copy of the screen buffer.

People seem to use Vulkan despite the d3d12 backend being superior, so add a message so people stop asking which backend is better.

Feature Request

What feature are you suggesting?

Overview:

Add more items to be logged in standard logs (not debug).

Smaller Details:

Add the following items to be logged. Tick the boxes below when it is implemented. Leave this issue open until all items are added.

• Audio backend (Dummy, SoundIO, OpenAL)
• Docked or Handheld status at boot time
• Vsync st

It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the

@Johnnynator says that it will boost build speed