Hmm, I guess I don't really consider throwaway assertions in pursuit of debugging "tests" in the typical sense.

I certainly wouldn't advocate for code reorganization for that case, but if there is a property that is important to maintain over time that isn't easily expressed by exercising the public API, it does suggest that reorganization is probably in order.