> I couldn't disagree more. *sigh* I know where you're coming from. This is the classic argument for limiting unit tests to black-box testing of public APIs

> I couldn't disagree more. *sigh* I know where you're coming from. This is the classic argument for limiting unit tests to black-box testing of public APIs exclusively, avoiding clear-box testing altogether. I agree that it's possible to write absolutely wretched fragile clear-box tests. And I agree that if you have a black-box test and a clear-box test which provide equal validation of functionality, the black-box test is superior because it will survive a refactor. I generally dislike absolutist rules of any kind when it comes to unit testing and prefer to think of things in terms of ROI. Sometimes you can add a lot of value with a clear-box test because the functionality is impossible to write a black-box test for without a ton of extra work and time. But sometimes you may be in an environment where absolutist rules are the only way to go.