We've had this discussion before. typ does not currently run all of the tests in a class in a row, and so it is actually correct for it to be calling setupClass()/teardownClass() between each test. If your tests or timeouts are actually flaking or failing as part of this, you need to fix your tests.

Apart from that, if you want to make sure that you're calling setup/teardown as infrequently as possible, you'll just need to be smarter about how you're doing things in these methods, and use setupProcess and teardownProcess instead to ensure things are cleaned up at the end.

One possible alternative to this is to introduce fancier sharding into typ, which is something that I've been meaning to get around to for a long time (I think there's even another bug open on this somewhere), and that would give you more control over what was run where and when.

Feel free to dedupe this bug to the bug that implements actual sharding for typ.

de-duping into bug 696128 (I don't think there was a bug on file before, but there is now).