Ah, good article really! Thanks!
Pointless tests, you have a point :P
The point is, like you say, TDD IF it doesn't get your way.
And I keep asking myself, especially when I'm experimenting, if TDD is the way to go in these cases.
There's definitely room for both practices: test first, test after.
I'm trying to understand from the community if this is broadly accepted, as opposed to: if you're writing unit tests later, then you're doing it wrong.
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.
It's a great habit to get into, provided it doesn't get in your way.
The tragedy of 100% code coverage
Dan Lebrero
Ah, good article really! Thanks!
Pointless tests, you have a point :P
The point is, like you say, TDD IF it doesn't get your way.
And I keep asking myself, especially when I'm experimenting, if TDD is the way to go in these cases.
There's definitely room for both practices: test first, test after.
I'm trying to understand from the community if this is broadly accepted, as opposed to: if you're writing unit tests later, then you're doing it wrong.