I am working on a project where
SqlConnection is created via a static method, lets say it's
DatabaseAccess.GetSqlConnection(). This method reads the .config file to get the connection string and creates a connection.
Is it ok to refactor the code to use an
ISqlConnectionFactory) responsible for creating the actual connections just for the sake of testing (as it seems more "by the book" for me) or go easy and just create a .config file in the test project containing test connection strings?
The second solution seems more error-prone and creates an indirect relation between tests and the tested classes.
I want to make sure there is a justification for the extra work of refactoring code to use the injected connection creator.