Should umbrella apps be tested in isolation?

I have an umbrella app that has one child application that does some heavy process manipulation in its test suite. This has the unfortunate side effect of clobbering the test suites of other applications. I understand this is an issue with async testing but I’m finding it especially hard to reason about this in the context of umbrella applications.

I’ve been able to get around this by testing the applications recursively (mix alias cmd mix test) but it’s super slow. I figure umbrella tests are the way they are on purpose and I have a knowledge gap.

Curious what other people’s experiences are if anybody has any advice.

1 Like