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”.

Testing interface is not about exactly interface as language’s feature. It’s about testing outer public interface (public API) of you things, looking at it as a black-box and doesn’t matter what happens inside. That’s all it means.

From my understanding the interface being referred to in the original guideline doesn’t necessarily refer to an interface as in the language concept but the more general concept of the interfaces to a given part of the system. In your example, I would interpret it as suggesting that you should test the public interface of the shape ie, when I call the Area method with some known cases, does it return the expected value.

Testing the implementation details in this case could be something like testing that the Area method for a circle called the Math.Pi function which would be an implementation detail. I don’t know if it’s the best or most helpful example but that’s my interpretation at least.

It’s a form of Black-Box Testing, essentially you want to validate expected behavior. Implementation can change, but your outcome should remain the same.

This is a big target for Test Driven Development, since your first step is to write the test with the expected outcome, then you write the most basic implementation, and when you can verify the behavior, then you are free to re-factor to improve implementation knowing your test will tell you if the behavior changes with each internal change.

Is that a real example, or a contrived one?

I don’t think it’s normal to write a test for IShape.Area() in your example. You’d only write tests for Rectangle.Area() and Triangle.Area().

Wether or not all of that is in the same file should, in my opinion, depend how many tests there are. If there are “too many” lines of code, split it into multiple files.

Testing the interface is more like validating the architecture of your module.

Say, you have your interface IShape, which represents a geometric shape.

Now you decide to add some shape editing capabilities to your qpplication.

Can you rotate your IShape? Can you flip it? So your IShape interface needs methods rotate(double angle) and flip(enum direction). So you add a test that checks that your module exports methods rotate(double angle) and flip(enum direction).

Does your application requires rotating shapes by a fractional angle? Maybe rotating by 90⁰ is enough? So you replace rotate(double angle) with rotate90degrees(bool clockwise) in your test and you can simplify your implementation.

There is no functionality in the interface so there is nothing to test. You test the logic of the implemented methods.

With that said, with reflection you can at least test that an interface has the right method names and annotations present, but I’ve extremely rarely found it useful to do so.

Not an “expert” in testing per se, but I’m not sure I would ever attempt to “test” an interface. As you said, there is no implementation. You can only test implementation, so #2 in your list.