Comments by "Nick" (@NicodemusT) on "TDD or BDD When It Comes To Automated Testing?" video.

  1. I will write TDD if it is effective. A lot of the time, it is not – or not realistic in certain situations. BDD is way more effective, because it tracks with the actual user. If you want to downvote my comment, go for it – but there are plenty of people who are working with different project/work parameters where the idea of writing TDD is not "better" or "easier". In the intro to this video, it is said that there are no edge cases that exist where TDD couldn't be applied. Here's just a few examples where TDD is/was not applied, and the world did not fall apart: – Nearly every plugin within the WordPress Plugin repository – The first 3 versions of Twitter – The first ~5 versions of Spotify – The entire history of Adobe/Macromedia Flash – 90% of anything built in Unity/Unreal Engine (for proof of this, check out the latest code leaks for GTA5 and insomniac games) – Websites, small applications made at marketing-speed agencies I'm sure there are many more. My point is not that TDD is bad – just that the "always" mentality is steamrolled by the objective reality we live in.
    3
  2.  @DagarCoH  comment got deleted and i repasted it to see what I did try trigger the filter.
    2
  3. This is a reality that the people working at SaaS multinationals like to gloss over.
    2