I have a following class in my PHP code:
<?php declare(strict_types=1); use function Http\Response\send; use Psr\Http\Message\ResponseInterface; class ResponseSender implements ResponseSenderInterface { public function __invoke(ResponseInterface $response) : void { send($response); } } The interface allows other codes to switch how they should "send an HTTP response", and this class simply binds a 3rd-party implementation to that interface.
Is this class too simple to test?
Its too simple to unit test. But you should still have integration tests.
Presumably the third party class dosent inplement the interface, hence you need this wrapping interface to be able to replace it with a mock in your unit tests.
So if you try to unit test this, you need another interface and you get into a situation where its 'interfaves all the way down'
If you make an intergration test though, which you should do, it really calls into question what you unit tests of the consuming classes are testing. Why not just integration test them? Why not separate their logic out a different way?
I would forgo this interface and simply integration test an http client for a service against a test http server.
