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 the option to disable prompt to confirm exit, akin to the "confirm on close" setting in Dolphin.

Smaller Details:

• I have a need to close the emulator without a mouse on my arcade cabinet. The current pop-up prompt that requests the user to confirm they want to close the emulator causes a break in the u

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