Who should initialize dependencies in a TDD application?

I’m trying to learn implementing TDD with mocking/fake objects. One of the questions I have is how to initialize a dependency in an application which implements TDD? An example from this article
Beginning Mocking With Moq 3 shows:

How to unit test a function that is refactored to strategy pattern?

If I have a function in my code that goes like:

How do I make code bound to an ORM testable?

In Test Driven Development, how do I make code bound to an ORM testable?

Test-Driven Development with plain C: manage multiple modules

I am new to test-driven development, but I’m loving it. There is, however, a main problem that prevents me from using it effectively.

TDD, BDD or both? [duplicate]

This question already has answers here: Relation between BDD and TDD (4 answers) Closed 11 years ago. I’m a little bit confused about BDD. I’m doing TDD currently. My question is whether BDD is complementary to TDD or it’s a whole new thing and my team should do both TDD and BDD? Or is it […]

Unit testing and Test Driven Development questions

I’m working on an ASP.NET MVC website which performs relatively complex calculations as one of its functions.

TDD – Outside In vs Inside Out

What is the difference between building an application Outside In vs building it Inside Out using TDD?

Introduce unit testing when codebase is already available [duplicate]

Possible Duplicate:
Best practices for retrofitting legacy code with automated tests

“TDD is about design, not verification”; concretely, what does that mean?

I’ve been wondering about this. What do we exactly mean by design and verification.

How to implement isValid correctly?

I’m trying to provide a mechanism for validating my object like this: