Run slow tests for coverage only

[caleb-johnson]

#307 includes a slow test that also provides important code coverage. I suggest we run slow tests on coverage only. This will allow us to continue to test a higher proportion of our code without bogging down every workflow with slow tests.

[github-actions]

Pull Request Test Coverage Report for Build 5525586771

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 90.703%

---

Totals
Change from base Build 5523955804:	0.0%
Covered Lines:	2556
Relevant Lines:	2818

---

💛 - Coveralls

[garrison]

I suggest we run slow tests on coverage only.

To clarify: this change makes it so coverage run the slow tests by default when invoked by tox; the other tox test environments don't run them. But within CI, the workflows explicitly opt for the other environments to run slow tests as well (see --run-slow in the test_*_versions.yml files). I think this is fine, just noting it.

[garrison]

Coverage takes a long time to run now, as there is a single test (test_asymmetric_bitstrings_CN) that takes 39 seconds on my machine. I think it might be better to annotate the specific slow functions we actually want to count coverage for, and run only those slow tests during coverage. It might be annoying to figure out the details of this, but I'll probably do it one day when I am feeling especially annoyed by the status quo 🙂

[caleb-johnson]

Coverage takes a long time to run now, as there is a single test (test_asymmetric_bitstrings_CN) that takes 39 seconds on my machine. I think it might be better to annotate the specific slow functions we actually want to count coverage for, and run only those slow tests during coverage. It might be annoying to figure out the details of this, but I'll probably do it one day when I am feeling especially annoyed by the status quo 🙂

OK this had crossed my mind, but now that I see how bad the CN test is again, I'll look into it. Thanks