You will miss items if you don't visually inspect even in a ttd application. Tdd is a net to catch some expected bugs but should not be the only tests.
Clicking around in your browser is more akin to an integration test though. TDD is about unit tests, not integration tests.
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.
Re:TDD did not live up to expectations
by ericgunnerson on Thursday June 29, 2017 @04:07PM
(#14666460)
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. :(
In other words, people (for example web-devs) who don't write tests first tend to "test" their code by clicking around in the browser to see whether they get the desired effect.
Writing tests, running them and then iteratively updating/fixing the code is IMO so much more efficient than manually clicking around to test one's code.