Test Driven Development (TDD) | Crash Course | 2020

Testing driven development is a skill that you must develop as a software engineer. In this crash course I will teach test driven development in simple steps.

==========================================
==========================================

🙊 Here are the goods for all my videos video:

► Recommended Books

Clean Code

HTTP: The Definitive Guide

Clean Architecture

► Computer and Monitor

New Apple MacBook Pro

Dell 27 INCH Ultrasharp U2719D Monitor

Double Arm Stand Desk Mount

USB C Hub Multiport Adapter

► Camera Gear

Sony ILCE7M3B Full Frame Mirrorless Camera

Sigma 16 mm F1.4 DC DN

Sigma 33B965 30 mm F1.4 DC DC

Awesome Screen Saver

IDE I use for coding
- Iterm
- VsCode
- GoLand
- IntelliJ
- Sublime

💯 You can also follow me here:

❤️ Thanks for watching

[natalya]

This is the moment when you watch a TDD video almost like an action movie. Thank you very much for your video, you dotted all the i's and crossed all the t's.

[ollysalanson]

Amigoscode you are one of the best teachers that I've ever learned from, not only that, you cover an absurd amount of topics. Thanks for always having my back!

[joaopedrodeamorim]

As usual, fantastic. Cheers from Brazil!

[ArMaAa]

Amazing tutorial :D ! Keep up the good work man!

[AnnieBox]

I'm soooo happy that I found another treasure vlogger!!!

[gerardoplus]

Wow! I like this post. Very good, I learned a lot of things. I'll watch the other videos! You are a good teacher

[renejacques]

Excellent for something I'm not even paying for.

[cheke]

Great video as most you publish. Just one comment, what is the scenario for the case where you have a new public function, but inside it you have various private functions defined or private variables that call functions from other classes? How do you implement the unit test of each one? Regards.

[peterwurst]

Good explanations and also a good video. Didn't you skip some parts or continue too quickly?
In my opppinion the cycle of testdriven development is allways to create failing test, fix with the minimal amount of code possible and create the next failing test. So when you created the function returning just false and checking for true the minimal approach would be to change the returned value and than add a test checking for false...

[SonOfMiguel]

Great video as always Nelson! Been looking to do more TDD during my internship. Thank you!

[nayalashmohammad]

This is just what I needed! Could you also make a Golang OAuth API Tutorial (making a go API from scratch) Thanks.

[andres]

Hey! First of all, congratz on an amazing video! I'd like to ask one question: Don't you think that parameterized test ruin the clean code idea of having one test for each assertion?

[mohammadjaouni]

جزاكم الله خيرا" . Jazaka ALLA khayran Bro

[Abhishek-troi]

First one here... I was waiting very eagerly.Thanks🙂

[jainchetan]

You are really doing good job, thank you so

[albinsjolin]

Dude, you are doing such good content! Gods work!

[carlosantovito]

Hey Nelson nice work, well explained simple and straight. I want only to discuss the PhoneNumberValidator class, it's a utility class so for me it's not needed to declare it like a bean and put it in the constructor of various Service class. I think that it's better to make a utility class with static methods in it and use it like every other utility class, so no need to mock it in the test or pass it in the constructor, it's more flexible. Tell me what you think about this modification. Good work keep it up!

[zakariahossain]

Another great course. Your crash course is like a pro level course. Thanks to Amigos.

[closetothee]

36:34 This test code would fail if later the message was changed to something else (which is likely to happen). But it was not the original code needs to be fixed, but the test need to be fixed in this case. Maybe this is a problem with TDD, i.e., you may need to spend extra time refactoring your test code rather than the code to be tested.

Also it seems to me that if you can take all possible conditions into account in your test code, you can actually ALREADY avoid bug in THESE scenarios. E.g. in the phone number validation example, you think of 2 conditions: phone number should start with +44 and it should have 12 digits and you put that in your test code. But if you're aware of these 2 conditions, you should already be able to put the check in your code to be tested. So in this sense the test code is redundant. On the other hand, if you don't take these 2 conditions into account, your code would still have bug although it can pass unit testing.

It seems to me the test code would be more useful when later the original code to be tested is modified. So running the unit test can make sure the original functionality is not broken. But in reality it's not common to remove existing logic but more likely to add some new code over that. Take the phone number again for example, maybe later [phone]Ext123 appears as a valid phone number. In this case the original code would be modified to add this possibility. But in this case the test code would fail because it also needs to be modified.

[pecewu]

Awesome work. Great Java tutorials! Keep it up.