depends if its a critical component. For stuff that needs to be atomic and handles critical data then yeah. Otherwise less so. TDD is really good for stuff tha

depends if its a critical component. For stuff that needs to be atomic and handles critical data then yeah. Otherwise less so. TDD is really good for stuff that doesn't have a native test workflow (headless invisible stuff) as it can double up as a test harness, so for stuff like message queues its great. For user interfaces its pretty crap though because you already have a test harness and your eyes are much better at testing.