[FIX/Discussion] Slow unittests #424
Description
We need to address the growing number of tests and their increasing run times. As most our tests are visual, we should explore other methods for testing the fidelity of the codebase. I see a few potential options.
Hashing (preferred)
pytest-mpl allows for testing hashes rather than images directly. This has two direct benefits. For one, it is fast, and second, we don't have to store the images -- just the hashes.
Reduce number of visual tests (not-preferred)
We should perhaps curate the number of tests to specifically test some but not all properties. I don't really now which ones would be best, but I can imagine a few essential ones and tooling the rest to be logical checks only.