If a utility is useful for testing it will eventually make its way into production.
I have seen this pattern many times.
You add a piece of code (possibly to help set up a test) that sets some state.
This then gets extracted from the test to a shared library.
It then gets added to the backoffice tool for development purposes.
This is then required for production.