assumption: you already use a testing framwork and an assertion library that enable you to know about when a test is executed and which is its outcome
I'm not that kind of gut who blindly believes in best practices. To me, everything is feasible and everything is good unless someone shows me a concrete downside. what are downsides of logging test code? performance? readability? if not, go with it
There is somethig, though, that we have to consider: in general, the logging purpose is to observe interal state of the system at work. Logging helps to investigate about misbehaviours beacuse lets to recognize problems with inputs, outputs, exceptions and with components integration
Unit tests are supposed to do the exact inverse: they are black box, they are "all of nothing", executed in isolation and without tolerating exceptions, if not part of side effects checking.
So, adding logs to tests seems a real code smell. Why you need them? Are your tests long and complicated? you are not able to investigate on failing tests? production code logging entries are not enough to explain the flow? This is something to discuss about