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.

Currently, Texture class is bloated with methods used to check if two textures are "compatible" with each other.

1. TextureCompatibility class also houses some of these methods.
2. Some of these checks affect other components in Ryujinx.Graphics.Gpu indirectly (as evident by #1474)

So, this code should instead be moved to the TextureCompatibility static class to centralize all compati

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