---
title: "Comment by Maxi Contieri on \"Code Structure vs Behavior in TDD\" | Hashnode"
description: "Nice post! Few people understand this Adding a new class is not the trigger for writing tests. The trigger is implementing a requirement. Michael Feathers gives"
url: "https://hashnode.com/posts/code-structure-vs-behavior-in-tdd/6115482be249483e1210f4de/comment/6117cae7e9f08a51fd85fc9d"
---

[Discussion](https://hashnode.com/posts/code-structure-vs-behavior-in-tdd/6115482be249483e1210f4de)

Comment [Code Structure vs Behavior in TDD](https://hashnode.com/posts/code-structure-vs-behavior-in-tdd/6115482be249483e1210f4de)

[Maxi Contieri](https://hashnode.com/@mcsee)

[Aug 14, 2021](https://hashnode.com/posts/code-structure-vs-behavior-in-tdd/6115482be249483e1210f4de/comment/6117cae7e9f08a51fd85fc9d)

Nice post!

Few people understand this

_Adding a new class is not the trigger for writing tests. The trigger is implementing a requirement._

Michael Feathers gives a great definition of a unit

_a Unit test is a fast test_

It is completely unrelated to classes, structure and file naming conventions.

I would mix the two concepts

[Mario Cervera](https://hashnode.com/@macerub)

[Aug 14, 2021](https://hashnode.com/posts/code-structure-vs-behavior-in-tdd/6115482be249483e1210f4de/comment/6117cae7e9f08a51fd85fc9d#reply-61182da0ac5c985f36434123)

Thanks Maxi!

Ian Cooper's statement was an eye-opener to me. The behavior-centric nature of TDD is far from obvious, specially for people that's learning the practice. And the ambiguity of the notion of unit does not help much.

I hope my article contributes to clarify the issue a bit 🙂