I've studied Object Oriented Programming (OOP) in two universities so far over several courses and using several programming IDEs and languages. I wish I had watched this video when I first started out in 2016. Your 7 simply explained steps to Unit Testing for Test Driven Development has made my final university assignment so much easier. You truly are a rare species! Thanks for creating and sharing this video!
The video does a good job introducing the concepts of Test-Driven Development. While the video is a little slow, the content is good. The video even gives the history of TDD and how extreme programming resulted in the creation of TDD. The visuals do a good job showing how the process of TDD works. They talk about the different key benefits, such as how bugs get eliminated quicker and programmers being more confident in their work. Also they go over how TDD allows code bases to grow and expand.
Spot on. Calculated pace of the speech allows brain to absorb. Wonderful Explanation. Would be great if you can paste the link of the implementation of the TDD in C#.
i create some piece of code, split it into 5-10 methods, then rearrange code into other 5-10 methods , and then in a day i find that i'd better fuse 2 of those methods in 1. If on each stage i crete tests before, that going to be more then 2 times more tests then eventually necessary
Excellent explanation, this is a topic that can be difficult to put into practice. Can you check the link you have in one of your slides? www.xprogramming.com/software, I would like to go check out this information but doesn't work.
You could've just wrote the damned function and tested it with mock data (remember, functions must do one thing and one thing only). If you need TDD, then you might have approached the problem too broadly.
But how would you test that function? Would you need to start the application to run that function with the mock data? If the application you're working with takes a while to build and start up, testing this way isn't practical because of the long feedback loop. Also, unit tests are typically run during the build process. If there isn't a unit test, it doesn't get run during the build, and bugs are introduced into the application where they are more expensive to fix at that point. But if a unit test is in place, a failed test will fail the build and force you to fix the bug before they are introduced into the application.
I've studied Object Oriented Programming (OOP) in two universities so far over several courses and using several programming IDEs and languages. I wish I had watched this video when I first started out in 2016. Your 7 simply explained steps to Unit Testing for Test Driven Development has made my final university assignment so much easier. You truly are a rare species! Thanks for creating and sharing this video!
Very very good explanation. I love how you speak slowly so the brain can understand the information ;)
video begins at 0:28 you're welcome
The video does a good job introducing the concepts of Test-Driven Development. While the video is a little slow, the content is good. The video even gives the history of TDD and how extreme programming resulted in the creation of TDD. The visuals do a good job showing how the process of TDD works. They talk about the different key benefits, such as how bugs get eliminated quicker and programmers being more confident in their work. Also they go over how TDD allows code bases to grow and expand.
Spot on. Calculated pace of the speech allows brain to absorb. Wonderful Explanation.
Would be great if you can paste the link of the implementation of the TDD in C#.
Thanks for this video. It explains TDD very simply. I do recommend people watch at 1.25 speed though. :D
Haha thanks works perfect at 1.25
@@carlos52321 it's not TDD though...
I disagree, his pacing and inflection are ideal for me for maximum distillation
Boris Churzin why not, can you explain and link to a video of what is tdd?
@@mattmarkus4868 search for Robert Martin TDD (three laws of TDD)
Best video available in TDD in You tube
Good video. Very clear and concise explanation of TDD.
You have a good clarification here. Thanks a lot.
Thanks for this video, got clear idea about tdd.
So 1 month of work suddenly took 1 minute? It's surprising that not everyone have discovered this productivity increase.
Really good what + why of TDD.
awesome
i create some piece of code, split it into 5-10 methods, then rearrange code into other 5-10 methods , and then in a day i find that i'd better fuse 2 of those methods in 1. If on each stage i crete tests before, that going to be more then 2 times more tests then eventually necessary
Excellent explanation, this is a topic that can be difficult to put into practice. Can you check the link you have in one of your slides? www.xprogramming.com/software, I would like to go check out this information but doesn't work.
Anyone else here from SWEN 5432?
You could've just wrote the damned function and tested it with mock data (remember, functions must do one thing and one thing only). If you need TDD, then you might have approached the problem too broadly.
But how would you test that function? Would you need to start the application to run that function with the mock data? If the application you're working with takes a while to build and start up, testing this way isn't practical because of the long feedback loop.
Also, unit tests are typically run during the build process. If there isn't a unit test, it doesn't get run during the build, and bugs are introduced into the application where they are more expensive to fix at that point. But if a unit test is in place, a failed test will fail the build and force you to fix the bug before they are introduced into the application.