Ooops, no...
Because it only occurs when calling "convert", not the underlying routine (obviously).

I guess it's a legacy of having no pre-existing tests for the existing behaviour of convert (at least, not this behaviour).
It would be easy to check that convert is calling the new routines, but I don't see how to easily check that 'exactly and only these coordinates' are made, as we can in testing the individual grouping functions.

What do you suggest ?