Some TDD tests aren’t small. Some TDD tests look more like integration or acceptance tests. There really aren’t any rules in that regard. So perhaps the best name of all is simply:TDD tests. Why? Because TDD tests are unique.
We use the term “unit” test to describe the tests we write while using TDD. But that name is unfortunate because it has no good definition. We don’t know what a unit really is.
The tests we write in TDD are written by programmers and for programmers.
There is no rule that says that unit tests can’t touch the database. Of course they can. One should be very careful, however, to avoid touching the database when the database is not relevant to the test.
Cheers.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
And before you come with the 3 rules by uncle bob with the word "unit tests" in it, take a look at this:
twitter.com/unclebobmartin/status/...
twitter.com/unclebobmartin/status/...
twitter.com/unclebobmartin/status/...
twitter.com/unclebobmartin/status/...
Cheers.