@monkey92t Would we consider merging #2483 before continuing on this
As it can be useful to test this command
Or alternatively do you have a suggestion on how we can test this?

CLIENT-SETINFO is similar to #2492, it represents the state of the connection, not just the command.

What do you think we should do?

According to the docs
We should be able to test these by checking whether those version/fields are there in the client info right?

It is tied to the network connection...

client -> call cmd -> conn-1 -> client setinfo lib-name test-name
client -> call cmd -> conn-2 -> client info -> lib-name ->""

Because we only set lib-name for conn-1, when we execute client-info, unless we are lucky and conn-1 is selected in the connection pool, we cannot get the value of lib-name