I'm a software developer based in Birmingham, UK. currently working at asos as a senior software engineer. I graduated from Staffordshire University in 2010 with a degree in Computer Games Programming. I've been blogging since 2010 - though this was my second attempt after a failure back around 2008. My background is agile development and pragmatic software development. When I'm not coding I'm a keen gamer and gardener.
Common complaints and problems that I've both encountered and hear other developers raise when it comes to the practice of Test Driven Development are: Impossible to refactor without all the tests breakingMinor changes require hours of changes to test codeTest setup is huge, slow to write and difficult to understandThe use of test doubles (mocks, stubs and fakes is confusing)Over the next three posts I will demonstrate three easy steps that can resolve the problems above. In turn this will allow developers to gain one of the benefits that TDD promises - the ability to refactor your code mercifully in order to improve code quality.StepsStop Making Everything PublicLimit the Amount of Dependencies you Use A Unit is Not Always a Method or ClassCode quality is a tricky subject and highly subjective, however if you follow the three guidelines above you should have the ability to radically change implementation details and therefore improve code quality when needed.