It’s been a while since I last wrote about why testing is important, but in this post I thought I would expand on that and talk about why not only ...
For further actions, you may consider blocking this person and/or reporting abuse
First are the requirements. Then comes a test that fails and then the implementation of the requirement. That may cycle until the code fulfills the requirement. Finally move to the next requirement and repeat. That is TDD. Writing unit tests to check that getters and setters work has little to do with TDD.
I guess the point of this article was to encourage people who associate testing with TDD that there's more to testing than the order in which you do it. Thanks for your comments.
Some more musing on this can be found here webrocketx.com/automatedTesting.html