Agile in Practice: Test Driven Development

[@ISprayTrolls]

12 years later and still relevant. Good Job!

[@majormotorslam301]

Should have watched this before my software engineer internship interview

[@jeffspaulding9834]

Nice video. It'd be nice if you put a link to your site in the description, though.

[@LevviTalk]

Awesome! ps.: love his accent

[@95rawan]

Great video thanks. I also love your accent.

[@SantiagoBlancoSoy]

Great work! Very useful

[@MrShadzu]

Great video keep up good work

[@ccdtech5394]

Thanks for this explaination

[@manarabdelbasetmohamed8590]

good explanation

[@deepthisingh3315]

Do you have this video's PDF document?

[@busbusvlog]

Thanks for the video! It's simple and very understandable

[@nivasdevarapalli2943]

Nice Video, Good

[@thearchibaldtuttle]

Where do you draw the line between what you have to specify and what the developer will cover with tdd by himself? Example: feature is calculating the sum of two entries. Does it need to be specified that the entries must be numeric and that there should be a meaningfull message to the user when he enters non numeric values? I have my personal opinion but what does tdd say about this?

[@davidhbrown0us]

+Archibald Tuttle I think that's a great question (and a great avatar). In my (limited) experience, yes, it ought to be specified in the design of the class/module being worked on that the values would be numeric and what to do if they're not. If it isn't specified, the developer wouldn't know how to write the test for non-numeric values. Should it look for an exception, a concatenated string, null...? Here, I think TDD can help uncover ambiguities or omissions in whatever design document you're working with. (If the language is strongly typed, it might prevent the possibility of non-numeric values, so the apparent omission might actually be covered by the class design.) I would think, also that "calculating the sum of two entries" and [displaying] "a meaningful message to the user" would be behaviors of two different objects, so a test that checked both would be more of an integration test, not a unit test. Not that you said unit test, but the video did, though most of what it discusses could apply to both.

[@thearchibaldtuttle]

+David Brown Thanks for your reply! Helped me a lot. BTW: Brazil is one of my favorite movies and I'm sometimes in the same situation as Harry Tuttle.

[@unorthobox7350]

very helpful

[@a.s8897]

I've been doing it for long without knowing that it has an actual name

[@SoranSuleiman]

Thanks, it is very informative.

[@Lilybun]

Doesn't this just make coders spend more time building tests than actual working code? Not to mention that making an elaborate test case that covers all the intended features can be more challenging than actually writing fully functional code. I mean, compiler should catch most basic errors and the rest can be caught by simply testing the code, a good comment with the intended features and possible problems is just as likely to help your co-developer test or improve your code and takes a fraction of the time.

[@LegoEddy]

I guess it's about being certain that your code works. Imagine working in a team of several devs. Once you commit your code into the joint project, you should be confident that it produces no bugs, or otherwise it will interrupt other devs from workinf on their stuff, too.

[@frankfrank380]

That is my opinion as well. I think it can work is the project is not time bound.

[@marlonsubuyu2012]

The thing is that you, the reviewer will spend the same time doing the test manually. It will take much more time to do a manual test because there are more things involved

[@MohamedOmrano]

Thanks a lot ;)

[@joaoguedesdasilvaneto94]

Done.

[@SimonaSquillante]

completed

[@juniorautran]

concluído

[@milindraut9881]

Video is very good but why are you running so fast? Need to watch it 3 times to understand what you are saying. Content is good.

[@fernandotoledo8093]

I disagree, making something fast does not ensure anything with high quality.

[@Puffadderr]

Term fast is so relative here that it doesn't even make sense. The target with TDD is to streamline coding progress of certain unit so that it can be done faster and with fewer errors. It doesn't mean you rush the code.

[@jimmy_jinglv]

test comment tdd

[@alexanderdemontfort3022]

Is there an English version of this video I can listen to?

[@wildone2163]

what a BS....