20+ mins is kind of a crazy amount of time for unit tests to run

[richardpringle]

We should look into what's causing the tests to take so long, see if there's any way to speed them up or split them up.

We should only be running tests on a sub-crate that actually had changes applied, that would probably get us a nice speed up right off the bat.

Expected outcomes to close this issue:

• Identify slow tests and create individual issues specifying that they need to be sped up (probably one issue per slow test)
• Split up sub-crate tests based on diff.

[Angel-Petrov]

Is this primarily a issue with the tests for CI or the local crate tests? Running cargo test on my machine yields satisfactory speeds.

[richardpringle]

@Angel-Petrov, cargo test doesn't actually run all of the tests. CI is a bit of a mess right now, it wasn't properly setup. It looks like the e2e tests can take a while as well as the unit tests (with all features).

This could also be a caching issue where a lot of the time is spent compiling the code.

I think someone internal has to work on this though as it'll be difficult without perms to make CI adjustments.