Yes, I read the documentation the original problem was that I wanted to ensure that we are overriding dependencies during unit tests.
Using contexts first can make it easy to forget that you need to override a dependency during tests, as you have to explicitly call the test context. Additionally, even when I use the test context, I’m no longer able to override dependencies during my tests. That's why I added "Is there another way to ensure we always override dependencies during unit tests, perhaps by triggering an error or warning when we forgot to override?"

Hi @hmlongco, just following up on this. Do you have any advice on how to avoid relying on developers to manually override dependencies for unit tests and prevent potential issues if they forget and use the live dependency by mistake?