Link Details

Link 1136477 thumbnail
User 929435 avatar

By vendettamit
Submitted: Apr 06 2014 / 12:04

We Write testable code to make the external dependencies injectable via dependcy injection and faking/mocking them while unit testing. But what if: 1. you have too many dependencies and you can't take put like 6-7 things to inject via constructor. Ofcourse it will look ugly in the code. 2. you have some dependecies that you can't fake. So you wrap the dependency in one of your own interface with implementing the real deal. But this is too much of writing code for getting rid of that thing. 3. You have to test the Legacy code that is Either "Restricted" for refactoring or "Refactoring" Cost you a lot as stakeholders don't want you put that much efforts in it.
  • 1
  • 0
  • 103
  • 15

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (1)

Voters Against This Link (0)

    Java Performance Optimization
    Written by: Pierre-Hugues Charbonneau
    Featured Refcardz: Top Refcardz:
    1. Design Patterns
    2. OO JS
    3. Cont. Delivery
    4. Java EE7
    5. HTML5 Mobile
    1. Node.js
    2. Debugging JavaScript
    3. OO JS
    4. JSON
    5. Ajax