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.

The operator * of utf8::iterator reads the code point at the location the iterator points to by calling utf8::next, which parses the UTF-8 encoding by iterating the underlying octet iterator from the leading to the last byte in the encoding.

However, when utf8::iterator is using a reverse_iterator as an octet iterator (like in the utf8_criter case in Xenia), the next function will

Feature Request

What feature are you suggesting?

Overview:

Currently, the range list implementation performs linear search on the FindOverlaps method. The purpose of this method is finding all ranges that overlaps with the range that is passed as argument. This can be improved with the use of interval trees, a data structure designed for fast insertion, removal and lookup of int

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

Related pr: Vita3K/Vita3K#749. Commit message or description from pr can be interesting to be in release description.