> What if the internal code incorrectly stores the fruit in a temporary file? Genuinely curious - how would you write a lower-level unit test to account for th

> What if the internal code incorrectly stores the fruit in a temporary file? Genuinely curious - how would you write a lower-level unit test to account for this? If my "testAddFruit" method directly hits the temporally flimsy datastore, how is that any better than the API doing the same, albeit through multiple abstraction tiers?