C# Unit Testing Tutorial

[@ivanvincent7534]

Would you recommend talking about unit tests on a first date?

[@RawCoding]

Yes, yes and yes. Works every time! Only thing more sexy than a programmer is a responsible one!

[@igornowicki29]

Depends if your date is also your technical interviewer.

[@laurenceqi7932]

Can I just say I have only just started watching your videos and I really wish I found your channel earlier, your articulation of these topics is just so well versed at every layer of abstraction. Where you're able to simply descibe what the tooling involves, the utility of it for engineers to the actual use for business strategy itself. I can't thank you enough for investing the time to make these wonderful videos.

[@RawCoding]

Thank you 🙏

[@com0oan]

10 minutes, already the best video on testing i've seen!

[@rafaelurrea2385]

Really nice advice all around, really quality content

[@RawCoding]

Thanks

[@ariafathi5683]

You are incredible, I really love your videos and they helped me a lot. Thanks

[@RawCoding]

Glad to hear

[@JordanBuildz]

Great stuff!! love the flow; thinking about unit tests from the standpoint of a client really paints the picture!

[@az1nn]

Clear and practical explanation, thanks for this video!!!

[@anatoliytkachenko7081]

Anton, Thanks a lot for great video!

[@RawCoding]

Thank you for watching

[@madd5]

Downloaded to watch later :)

[@RawCoding]

Why download?

[@madd5]

@@RawCoding I will forget to watch otherwise LOL

[@rouzbehzarandi7846]

Awsome..charming..fantastic...profesional....superb poster back there. by the way nice tut thanks ;)

[@funfactor2290]

since when you can just inherit from any class, doesn't have to be abstract does it ?

[@mohammedibrahim5464]

Thanks a lot for the great videos! , Your videos are awesome !!

[@RawCoding]

Glad you like them!

[@hozmannew896]

Simple but useful, thank you so much

[@RawCoding]

thank you for watching

[@reha2341]

what's the compiler u r using ??

[@crusaderACR]

What are you using to show markdown files in Rider?

[@RawCoding]

should be a bundled extension called Markdown

[@rade6063]

Great video dude.

[@RawCoding]

Cheers

[@mehdihadeli]

@ Raw Coding Thanks for your great video, Please record a separate video for integration testing and E2E testing also. Could you introduce me, some good resources for testing?

[@RawCoding]

Don’t worry it’s coming. And I’d say just practice, can’t read about push-ups

[@mehdihadeli]

@@RawCoding thanks

[@RawCoding]

If it helps, I’m currently making videos on testing

[@rade6063]

By the way what is this environment where you are coding?

[@RawCoding]

Rider

[@rade6063]

@@RawCoding Is it better than Visual Studio enterprise?

[@rade6063]

Im asking because you used to use Visual Studio in your previous courses

[@RawCoding]

Yea I like Rider better now

[@madd5]

@@RawCoding interesting. I'll try Rider.

[@HaiNguyen-vu9cj]

Thank you very much.

[@RawCoding]

Thank you for watching

[@naodagere8210]

Thanks, subscribed.

[@SoulGuitarMetal]

What if the tests have bugs?

[@RawCoding]

Then you’ve fucked up

[@scigama71]

very good tutorial..thank you

[@HAN_USA]

is thi VS code or intelliJ ?

[@RawCoding]

Rider

[@davudsafarli5356]

Nice! Thanks for the video and explanations. subscribes++; I would like to mention(discuss?) one thing you said about TDD while testing Hashing. If it was only about hashing a string then we could make use of TDD *very* easily, by checking a sha256 of string "AABB" online, and use that result in the test assertions. In this example too, in `arrange` section, we can build an `Item` in such a way that its #content + #url will be "AABB" eventually, and do the same thing I wrote before. But then our tests will be coupled to the implementation, because you may iterate over selectors in reverse order(just an example), and then hashed string would become "BBAA", and tests would fail. So, maybe it's design related problem? Hashing shouldn't go over the selectors at all? It should *only* accept a string(or array of bytes) and make a hash out of it? If we decoupled the the Hashing and Stringifier* logic, then we could make a better unit test for both. I think this way, because when something can't be done with TDD, it's mostly because of design decisions(problems)

[@RawCoding]

> If it was only about hashing a string then we could make use of TDD very easily, by checking a sha256 of string "AABB" online, and use that result in the test assertions. True, I think this is a valid approach, although I think this is more of a chicken and egg problem in our scenario, unless we are using TDD to develop the algorithm. Can't remember if I mentioned it in the video or not but - ideally we want to provide the algorithm from behind an interface, which we can mock. > So, maybe it's design related problem? Hashing shouldn't go over the selectors at all? It should only accept a string(or array of bytes) and make a hash out of it? If we decoupled the the Hashing and Stringifier* logic, then we could make a better unit test for both. Yes I completely agree, we discuss this in the 2nd episode (it will be out on Tuesday) where we talk about mocking and how decoupling helps testing when we can mock. We invert the dependency on algorithm creation and decouple from the parent hashing strategy the way you describe it. > I think this way, because when something can't be done with TDD, it's mostly because of design decisions(problems) Agree

[@kimsung2384]

Really difficult to see the code when watched on phone

[@deepak3358]

Hey! Your videos are awesome and can you please make tutorials for pheonix- live views ? If possible.... Thanks

[@RawCoding]

What’s that?

[@deepak3358]

@@RawCoding basically it is used to make single page applications in which we don't need to worry about heavy JS libraries...we can actually code front end and backend code together...this is the only thing I know as of now...

[@RawCoding]

Sounds like you know more about it than me, I won’t be making a tutorial on something I don’t know

[@clearlyunwell]

👍🏽

[@RawCoding]

)

[@xxyxungxxraimexx7242]

Cool

[@RawCoding]

indeed

[@sreenuksr]

First like 👍

[@RawCoding]

:clap: