To separate functionality for CLI and the tests, create two controllers for CLI and the tests.
Use cases:
CLI controller is very "heavyweight" in sense of logic. tests do not need all this stuff. to not make mistakes in the method it makes sense to separate logic dedicated to tests and to CLI (tests controller would be more lightweight)
Authselect. We don't need authselect in CLI commands in general. This model is used in the tests. So why overload this controller with auxiliary stuff?
This idea is overkill for our purposes. It would be enough to serialize required objects using e.g JSON format and then load them in the tests via fixtures.
Idea: two controllers
To separate functionality for CLI and the tests, create two controllers for CLI and the tests.
Use cases: