I disagree. I and others (such as Thoughtbot) often start by writing integration tests first. It’s known as outside-in testing.

TDD by started by with low level tests is just backwards. Outside-in helps you clarify the design from the perspective of the user.

https://robots.thoughtbot.com/testing-from-the-outsidein

ATDD or design-driven development starts with integration tests first, and can be a great thing if written by the PO, as you can pretty much skip acceptance testing.

It addresses a different concern than unit testing, however.

(Your account was rate-limited—sorry, fixed now. It's an anti-abuse restriction on new accounts and we hate it when article authors get dinged by it!)

This is the only comment to mention ATDD, and none mention BDD. :(