Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

I never said that TDD is a design, but it is about design.

Mik378
– Mik378

2016-05-29 23:34:37 +00:00
Commented May 29, 2016 at 23:34
1

Uncle Bob was telling you to design. He wasn't telling you "hey if you're tests work who cares about the rest".

candied_orange
– candied_orange

2016-05-29 23:41:57 +00:00
Commented May 29, 2016 at 23:41
1

As I already said, just follow the rules of who you're allowed to talk to. The clean architecture isn't something to have a BDUF debate over. Just identify what part you're in and think about who and how you should communicate. It's more agile than you might think. After that ask if it's testable by TDD. If it's not you did something wrong. If it is I hope you were paying attention because good design is more than just testable.

candied_orange
– candied_orange

2016-05-29 23:52:04 +00:00
Commented May 29, 2016 at 23:52
8

Ugh... I really can't stand the "Test Driven Design" misnomer. You still have to design a bit before you start blissfully pounding away at your keyboard, whether or not you write tests.

RubberDuck
– RubberDuck

2016-05-30 00:16:21 +00:00
Commented May 30, 2016 at 0:16
1

To quote Uncle Bob on this exact point, "You have to DESIGN period". Click there and if you're too impatient to read the whole thing search for those words. You'll find Mr Martin is quite adamant that TDD is no magic bullet and that you must design not only your code but your tests as well if you don't want to live in a very brittle code base.

candied_orange
– candied_orange

2016-05-30 10:04:32 +00:00
Commented May 30, 2016 at 10:04

| Show 12 more comments

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »