Could you explain your rationale? Is it because of extra computation costs if logging is disabled? I find f-strings more readable than other interpolation format so I favored legibility over minor gains in CPU cycles in this case.

It's about the logging level you set yes. But also about uniformisation in the base
code. If we were to set the log level to warn in production, that'd be still computed
indeed.

If you look at any of our other modules, you'll see we do use f-string for some string
computations but not for the log ones. We let logging do its job.

Also it happens also that some objects (SWHID comes to mind but i may be wrong) used in
f-string could trigger some heavy computations too.

Although now that i've said that and given that I re-realized it's test code, it may be fine to keep it that way.

To be clear, it's non-blocking otherwise i would have requested changes btw.