I ignore them because they’re meaningless. You should not pass env to a protocol implementation but define implementations based on the environment. Then your code uses the protocol itself and doesn’t care about the implementation or the environment.
Hardcoding names to processes is another code smell you apparently use. Always keep the option to start a non-named process.
If we’re talking about unit tests, why are you not keeping your functions pure? Why they start processes which involve database calls?
P.S. me and @mudasobwa talk about the same thing. Just two different ways to achieve it.
