"The Clean Code Talks -- Unit Testing"

Google Tech Talks
October, 30 2008

ABSTRACT

Clean Code Talks - Unit Testing

Speaker: Misko Hevery

• Category

  People & Blogs

[succelus]

Keep the good Talks !

[neohubris]

great talk!

[bhavik shah]

"How do we write hard to test code? We mix object creation code with business logic. This will assure that a test (test case) can never construct a graph of objects (object graph - mocks, fakes, stubs, proxies) different from production. Hence nothing can be tested in isolation."

[deepak balasubramanian]

check for conversation display.... unit testing

[deepak balasubramanian]

Post from shared Message.... !@# diff

[Jesper Heilmann]

Constructor paradigm:

Ask for needed objects (by parameters)

Do not instantiate dependencies.

(Separating Object graph construction from business logic)

[senihokur]

back when I watched this first time, I thought testing a car was just an analogy

[Vijay S]

Here is the good explanation of unit testing: softwaretestinghelp[dot]com/un­it-testing/

[Ilya Ivanov]

agree, a lot of literature covers topic, like "why procedural code is much easier to test". If you have a static method with big, unmockable side effects, than this code is bad by procedural standards. Pure procedural functions don't have side effects which is golden grail for testing.

[mLovelady30]

thegoodteacher(dot)com