Effective code tends to put a lot of functionality behind a relatively small interface, and tends to work for a long time without needing attention.
A "change detector" is exactly what you want in this situation. Does the code still fulfill the spec (tests)?
Tests that feel like they need to be changed every time the code changes are generally white box instead of black box, or the interface to the code being tested is too large.
> Effective code tends to put a lot of functionality behind a relatively small interface
Do you have actual strategies for reducing high surface-area:volume requirements into more easily managed low surface-area:volume code or is this just wishful thinking?
Nobody likes shim layers but they (and other horizontal strata) happen for a reason.
A "change detector" is exactly what you want in this situation. Does the code still fulfill the spec (tests)?
Tests that feel like they need to be changed every time the code changes are generally white box instead of black box, or the interface to the code being tested is too large.