Are you kidding me! I swear this is the first decent unit testing video I’ve ever seen and I’m only like 15 min in! You got me hooked! You are going to make waves in the community!

First, fantastic coverage of this topic. I needed a refresher for my current assignment this exceeded my expectations. A couple things to add. 1) Our test classes are just that and it is very useful at times to write helper functions within the test class that are not prepended with test_. Maybe you have a scenario that you want to test your data array with all evens or all odds in many tests. Creating funcs to do setup the data outside the setup/teardown funcs can be super handy. 2) Creating automated tests for you code always saves time: A) you are going to test the code anyway one or another if you are a decent software engineer. By making it an automated test you get to use it 10s of thousands of times or more. Your “one time” test code now does not get thrown away. B) When you write the tests you are in a different mindset. You naturally think of checking all the edge cases and rarely say, “I thought I tested that”. C) TDD with paired programming is the most cost effective way to develop software and is also the hardest concept to sell to those with the money. Come up with a good way of selling the concept. D) Developers should write all the fundemental tests. The testing team, if you are fortunate enough to have them, should be writing far more advanced tests. For instance the developr should write download tests like there are here. The testing team should be creating partially corrupt data tests, slow and hyperfast download speed… Testers are not for finding developer fundemental mistakes 3) No need to apologize for the length of the video. KZfaq gave me this handy pause button, I take as many breaks as needed to get through the whole thing. 😉 On to UI Testing review next. Thanks again.

I worked with apple. I think you are the best SwiftUI KZfaqr. :)

Found your videos yesterday. You are really saving me a lot of time. Great material. Thanks!

This is the part that I've been looking forward to the most since this series started. always thanks

I've never seen a better explanation! Thank you so much for this superb video, which saved me a lot of time:)

Best unit testing video with Swift!

Awesome! Thank you for the video, Nick

Such an informative video. Super helpful. I feel very good about Xcode Unit Tests now. FINALLY!

Been waiting for this video. Really good man. One of my favorite Swift videos of all time.

It's awesome! I am gonna add new skill in my bucket. Thanks for this awesome explanation. I always find your explanation a lot easier to understand. Thanks again.

This is amazing video!! This is definitely my favorite swift learning channel~!!

Amazing as always. Thanks so much Nick :)

bro, I was waiting for this video for a long time. thank you and never feel bad just because of the video length. keep grinding

Excellent video. thank you!

Great video, well explained. Thank you.

Amazing! Thank you very much.

Great explanation! Thank you for your effort! Would be great to have one about TDD :)

Amazing tutorial!!! thanks nick

Great explanation! Thank you for your effort! Would love to have with TDD.

Your channel is just awesome, I started Swift 2 weeks ago, and Now I am great at It.

Nice video! Just a quick FYI XCTest will create a new instance of your XCTestCase subclass for every single test in the class. -State wont be shared amongst your tests unless they write to a database, or are static (or similar)

Amazing video. I've been coding for 7 years and manage a team of 10...looking to implement unit testing for my team. Going to have them all watch this as a start :)

Excellent explanations

A MUST LOOK VIDEO!

Excellent video. It’s very educational. Please keep going.

I didn’t even know how to do this until now. Thanks angel.❤

awesome, thanks

I'm so excited for having found this tutorial, it looks really promising and I can't wait to start coding & learning!

The real power of unit tests is that they can be used to actually design data and to also help structure a function. They are an extremely powerful tool to allow you to write templates.

It would be really nice if you could make a video about unit testing core data. For example the video you made for creating an app with core data with multiple entities.

Thank you man

Hi Nick, thanks for yet another amazing video. I was hoping you could elaborate on why you created a local array for certain tests (ex. the ...shouldSaveItem( ) test) instead of just using the view model's dataArray property?

Love you my teacher ❤

The best in swift

You're a terrific tutor Nick, thank you very much for your work! Just a quick question: why use a separate itemsArray collection in saveItem_shouldSaveItem() (line 218)? Isn't it enough to just use the dataArray property belonging to the vm?

Dear nick, please provide something related to T.D.D too, thank you

Even a lazy programmer would watch this. Means, it is easy to understand

The first half of the video made sense to me. The second half requires a few more viewings.

good shortcut for testing is cmd + u

Can you please share if yu have a tutorial that tests the Networking layer of an application

It was a very informative video. It helped me a lot while writing unit test. I want to ask something. I used firebase in my application where I want to write unit test and I need to create an instance for firestore.firestore. how can i write this?

Incredible explanation. 🎉🎉🎉 Assume we have a dataService class reading and writing data to back end. This dataService would be used in multiple view model. The app should initialize the dataService after launching and stores it into the environment. Then all the views can get access to it and inject it into the view model of their own. Am I right about this? Is there a better way to organize the code?

Great series. What do you think about MockingBird library for mocks? With java background writing your own mocks seems cumbersome...

Cool, thanks man! Please consider create a icloudkit video 🙏

How do write unit tests for vars or funcs in the original code that are marked private? I did not find a way other than remove the "private" while testing. Any ideas? Did I miss something in the video? Great video by the way, the whole series.

Kindly make a video on writing unit tests for API calls also. Or Can anyone suggest me a video link on this if you know

Hi Bro, Just Started watching...now partially finished

How would you include String extensions though? I am getting an error when trying to include them Value of type 'String' has no member 'myfunction'

is it right to specify the name of the test function on that much long as we can? can we summarise it only in a comment?

Where can I download the starter project? Thanks

Hi bro, can you make a series on VIPER architecture

Hi :) If I wrong, please correct me 🙏 52:58 - func test_UnitTestBootcampViewModel_selectedItem_shouldBeSelected_stress() You have created a new variable: var itemsArray: [String] = [ ] - But it seems pointless to me. Here is your code: // When let loopCount: Int = Int.random(in: 1..