Podcast on Testing: Test & Code

[YvesMuyaBenda]

Though the language is python, listening to the podcasts would be an excellent way to immerse oneself in various thoughts related to testing, a superb way to learn the language of testing:
http://testandcode.com/

Most useful for a complete beginner and non python-specific are the following podcasts:

1. Why Test?
2. The Waterfall Model
3. Test Case Design Using Given When Then from BDD

[kfern]

IMO Podcast are very difficult to follow for those who do not have English listening skills. Using videos with subtitles would be more useful

[nelsonic]

@kfern agree that for people who's first language is not english, subtitles are more friendly.
we will be adding them soon to our videos: dwyl/video#35 😉

[newswim]

Thanks for that link Yves!

Have you given any attention to James Shore's course? It seems like one of the better paid courses on TDD. Reminds me a bit of DestroyAllSoftware but for JS. I haven't worked through any of it yet because I'm currently drowning in free resources.

Another thing for the link wall: https://www.letscodejavascript.com

[Fl4m3Ph03n1x]

My two cents here:

@YvesMuyaBenda:

• The Waterfall Model doesn't work and hasn't been used successfully for years ( http://www.infoq.com/resource/articles/scaling-software-agility/en/resources/ch02.pdf ). Also TDD defines that tests should be made before coding, not after and the Waterfall model has tests after. I enjoyed the podcast, but I don't see how anything related to Waterfall can be beneficial to this tutorial TDD tutorial.

@newswim:

• Should we add resources that are payed? I am usually against such things, as it looks we are promoting payed content. What are your opinions ?

Anyway, great suggestions overall!

[YvesMuyaBenda]

@Fl4m3Ph03n1x I simply do not have the experience to debate the pros and cons of the Waterfall model in specific scenarios. I included the link for general context and background. The Waterfall model is a common reference point in discussions of software development methodologies, and the podcast was the very best discussion I have seen, in part because it went back to the source.

[Fl4m3Ph03n1x]

@YvesMuyaBenda and the source, for those who have read it, actually predicted all the issues that Waterfall is plagued with, and laid the base for what is SCRUM today (an Agile methodology) :P

• Short sprints with prototypes
• More customer involving
• Tests earlier

Eventually this became the foundation of how we see TDD today. I agree it was an interesting talk, but I still defend that adding it would add no valuable meaning to this specific TDD tutorial, because without proper context you won't realize the link between Agile, SCRUM and TDD, and how people not reading the actual paper contributed for one of the worst methodologies ever created for software development.

[YvesMuyaBenda]

@Fl4m3Ph03n1x Sure, I am just offering suggestions that I have personally found useful and interesting; I am not that much invested in the various arguments for and against specific definitions of specific software methodologies. Folk are free to make their own choices about my suggestions.

[YvesMuyaBenda]

@Fl4m3Ph03n1x On the topic of Agile, this talk Agile is Dead by Dave Thomas, one of the originators of The Manifesto for Agile Software Development, was fascinating, fascinating! It is always useful to see different points of view. I am not making any hard choice yes or no on this or that methodology, merely holding the different points of view in mind as additional context.

[Fl4m3Ph03n1x]

@YvesMuyaBenda Interesting talk, I will be sure to listen to it :D