let’s say there is a Shape interface.
interface IShape { double Area(); }
A Rectangle class and a Triangle class implement it. Now should i write tests for:
From what I see I am testing implementations either ways. How do you even test an interface without testing the implementation? Can someone please help clarify my doubts? Thanks!
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Follow the wormhole through a path of communities !webdev@programming.dev
That advice does not literally refer to
interface
the programming language feature. It means to test the observable behavior of a component, not internal implementation details.In your example, write tests for both Rectangle and Triangle that call
area
, and assert the result is correct. But do not test, for example, the order of mathematical operations that were run to calculate the result. The details of the math are an internal detail, not part of the “interface”.Fuck! Now it makes sense to me. I thought it literally meant an interface. Thanks a lot for clarifying!
No problem! I thought there was a good chance you already know the concept, just not in the exact, unfortunately-overloaded words of your post title.