These tests are redundant, since no other test will succeed when your constructor doesn't work.
And to be honest, I don't even bother to write those null checks in my constructors anymore. Reason is simple: DI containers don't allow you to auto-wire constructors with null references (or at least, not by default), so there is no possibility of types being constructed using null values (when auto-wired by a container). So it just adds useless code that makes me add useless tests when I want to have high code coverage.
I say skip these null checks completely and trust your DI container (or pick a DI container that you can trust).