I am a new lead developer that has recently started at a new company, I have been assigned to a project that is trying to consolidate functionality from lots of different applications already in widespread use in the business.
The problem is that their software development/project management are in the dark ages. I have committed myself to trying to improve things, starting off with automated builds, which is almost setup.
The next thing I Would like to add is automated testing. The issue I am facing with this is while the project is technically 'new' for the business the code that has already been written has a lot of dependencies and is considered(not by me) to be un-testable.
I have some experience in using the fakes framework to write unit tests for code with a lot of dependencies and i think we could use it to overcome the problems we face however are the project is being built around a large piece of middle-ware that contains the vast majority of the business logic and controls the data access. We are mostly just producing input for this system in a lot of cases.
So I am confused on what should actually be tested in this scenario or even how it could be done. It is a very large dependency which IMO is too big to mock or fake, so i cannot see a way to even validate the created input to what would be valid output.