The first 5 minutes of this video cleared up so much for me: I am not a software developer. I don't work for a software company. I don't plan on being a software developer. I don't plan on working at a software company. I just write apps & libraries for myself, and sometimes I share them with the open-source community. But for some reason I still want to learn about unit testing and see if it can help my specific situation (learning to code better).
thanks for this. Nice simple unit test tutorial. I'm also an audio guy and I just want to point out, you have a pop filter on your mic, but all your "p"s and strong breaths are "popping". Try backing the filter off of the mic and bring down the input gain. 🙂
starting to follow along with this unit test course, just had a brown out and had to restart. however, can't help but be bugged by seeing the "solution explorer" on the left 😂, It's probably gonna be a good journey either way, even though I get bugged by small things like that. btw, doing the course because I'm on my 2nd year of my 2nd dev job, used to be a desktop technician, but got pulled into dev allegedly for my work ethic in the same company as my last desktop technician job (I had intention of staying there, until covid came and took jobs away, and now I work 50km from my house instead of just 5km, hoping learning the various things I check online can get me something fully remote).
Biggest thing with the code just breaking, years ago some dolt re-wrote a formula, had no unit tests, pushed it. They were missing a part of it in the "cleaned up" version so of course ti wasn't mathing properly. We spent who know's how long searching for the error in the entire freaking project, step, by, step, and then had to go get a fish and slap the person with it for changing a + to a - in the formula... Unit tests, they exist, require them, if people don't, throw their commits anywhere else but the main repo until they have them. Thousands of lines of game and networking code, for a freaking - sign being the wrong in some random function we all thought was fine because this same idiot likes to make 40+ file huge commits of tiny things and it got burried in one of those. Just use the freaking unit tests please and thank you. xD
Looking back on it, I think I came in at a bad time. Everything was falling apart and I think people were secretly panicking but I was too new to understand what was really going on.
Please reconsider saying, "we're going to", "go ahead", "actually", or any combination of them. 🤢 It will make your videos shorter and your content more digestible.
I was looking for unit testing content and i find this. Thanks, i liked your laid-back way of explaining!
Dang! You're on fire, Teddy :)
Thanks for more one video with an excellent explanation
33 seconds in, and I feel very positive about this! Good job!
Thank you for this @Teddy Smith!
Just wanted I needed. Super excited to enhance my testing skills!
The first 5 minutes of this video cleared up so much for me:
I am not a software developer.
I don't work for a software company.
I don't plan on being a software developer.
I don't plan on working at a software company.
I just write apps & libraries for myself, and sometimes I share them with the open-source community.
But for some reason I still want to learn about unit testing and see if it can help my specific situation (learning to code better).
It's great to have Luke Skywalker teaching me about unit testing! great content!
I was going for baby yoda but Luke is cool too I guess
Cheers man great video. Im working my way through the whole series
Best explanation about tests i've ever found. Good job, Teddy!
I am starting this lesson as a newbie.
Thanks for your video tutorial!
You just got a new subscriber :D very good and entertaining lesson. Thank you
Excellent initiative, loved the way you explained
Really liked your
input: water
function: human
returns pee
example. 😁
Thanks. Just in time, trying to figure out the tests
Sweet. Thanks for commenting and watching.
Thanks you, I start understand on what is unit test.
Amazing explanation. Thank you!
23:20🤣
Happy 1400 likes ;)
Made me laugh so I'll keep watching :)
Wow Really nice explanation. Thank you!
Thanks Teddy, I understood clearly
👍
so if i have a project with no classes and function implementation in separate source file i also do the tests in a class ?
thanks for this. Nice simple unit test tutorial. I'm also an audio guy and I just want to point out, you have a pop filter on your mic, but all your "p"s and strong breaths are "popping". Try backing the filter off of the mic and bring down the input gain. 🙂
thank you for input. i did end up fixing and getting a better mic setup after this
This really needs chapters, so I can find where I am in my progression and match that up with your segments.
I am not a C# dev but do you really need to wrap every test in try catch inside the unit test?? Is that a common practice??
No, later on the unit tests don’t have try catch. They just break and show up in the console.
thank you. Youre the best
loving it
starting to follow along with this unit test course, just had a brown out and had to restart.
however, can't help but be bugged by seeing the "solution explorer" on the left 😂, It's probably gonna be a good journey either way, even though I get bugged by small things like that.
btw, doing the course because I'm on my 2nd year of my 2nd dev job, used to be a desktop technician, but got pulled into dev allegedly for my work ethic in the same company as my last desktop technician job (I had intention of staying there, until covid came and took jobs away, and now I work 50km from my house instead of just 5km, hoping learning the various things I check online can get me something fully remote).
This was so helpful thank you!
Biggest thing with the code just breaking, years ago some dolt re-wrote a formula, had no unit tests, pushed it. They were missing a part of it in the "cleaned up" version so of course ti wasn't mathing properly. We spent who know's how long searching for the error in the entire freaking project, step, by, step, and then had to go get a fish and slap the person with it for changing a + to a - in the formula...
Unit tests, they exist, require them, if people don't, throw their commits anywhere else but the main repo until they have them. Thousands of lines of game and networking code, for a freaking - sign being the wrong in some random function we all thought was fine because this same idiot likes to make 40+ file huge commits of tiny things and it got burried in one of those. Just use the freaking unit tests please and thank you. xD
I legit laughed at your story 🤣
you remind me of Luke Skywalker hehe. Great video bro
haha just commented the same
Thank you so much!
Nice video bro!
2 things:
- why static ?
- why try/catch construct ?
a unit test should not be structured like production code.
should not need a try/catch.
most people have no idea what a unit test is, so this is just a concept to teach underlying idea without jumping into frameworks
Would you be also doing Integration testing? Thank you!
Just unit tests for this one 👍
Why do we need that try-catch block?
I guess you don’t but all exceptions are “unchecked” in C# so if you want to see an error try-catch is going to be the best bet (edit: spelling)
oh, ok.Thanks!
@@TeddySmithDev
Ninggalin jejak dulu om
I clicked the thumbs up, you better have done some web api stuff.... or else.
thanks
Do Web API too please 😎
Teddy... were you the one that they berated lol
Lol good question. Wasn’t me that time but they did in general. They went out of business I think tho so write your unit tests lollllll
Why does he look like one of the guys from Lonely Island? 😆
It’s my bowl cut. It actually has a second brain inside that helps me code 🤣
omg.. this takes a long time with a lot of content which you could edit out.
Check out this video starting from 16 minutes in
th-cam.com/video/HYrXogLj7vg/w-d-xo.html
Umm that toxici workplace story.... sounds like it was on the workplace, not the individual.
Looking back on it, I think I came in at a bad time. Everything was falling apart and I think people were secretly panicking but I was too new to understand what was really going on.
Русские есть?
just waist my time to you ((
waaaay too slow!!!!
Please reconsider saying, "we're going to", "go ahead", "actually", or any combination of them. 🤢
It will make your videos shorter and your content more digestible.