Swift TDD - Test Driven Development for Swift no more bugs (Udemy.com)

The course uses an API that no longer exists. Should be updated, so people taking the course can reproduce the tests and actually make the calls. Calcatraz currently returns 404. The subject of the course so far seems very basic - being the course advertised as advanced, I'm not very happy with it.

In the description it says it's a advanced course, in my opinion it was very basic. It gave me however a quick introduction to TDD in Swift and enough knowledge to continue on my own. I would have preferred some more advanced content though. Injection and mocking, maybe? I would say that some of the code written in this course is pretty far from best practice but maybe it does not matter that much, because testing was the main purpose of the course.

The course is a little bit slow and before create a course it's a good thing to prepare them. I mean normally you don't have to hesitate because you already know what you have to show us. I could nevertheless learn a few things interesting. Thanks you.

Throughout of this course finally got a clear picture of TDD. Which is required for an iOS developer to boost professional skills for a better scope and extremely helpful for bug-free development. Thank you Udemy and especially thank you Icaro Lavrador. Just a request if you can use more practical real-time project it would be great. Thank you

This is my 2nd Course from Icaro and so I am writing the generalized review of what I think about this course and Icaro as an instructor. If you are looking for a real instructor for iOS then I would definitely recommend Icaro he really teaches good. I am stating some real reasons that why should you take this courses- - Number 1 reason to buy this course is the support you get. He replies to the problems students are facing personally and he just don't helps you out with the problem he helps you out with the best possible manner he can. I am telling you that I hadn't received better support then this course on Udemy. - He is an experienced guy so what he is sharing with you is his experience and learning from his experience is worth the price you are paying. - Best Coding parctices, He is teaching things with best coding practices. - And last but not the least is he had made very nice course structure, he knows what should be taught and how it should be taught. I am very happy after taking this course from him and I would recomment you to take this and his other courses. And one more thing this is the 1st or 2nd time I am giving someone 5 star rating on Udemy.

I this course requires more polishing. There is no "first right your test, then come back and write your class and doing this over and over approach" I learned that elsewhere. The English isn't really good. The problem sets aren't real world, nor they are even good pedagogical examples. Neither the course is thorough enough. It's just a waste of your time, regardless of the refund. I hope the instructor sees the faults and addresses them. I recommend you instead buy a TDD swift book on this subject...

It got me started on testing in Swift, so I'm happy with that. I do have to agree with a few other comments though: a) a downloadable project with the code would have been good - I did not need to recreate the project, b) some edits where mistakes had been made (not the deliberate ones) would have sped things up. However I WOULD recommend this to someone, like myself, who wants to get up and running with XCode testing without any prior experience in it. Thanks

1. The instructor adds the files he want's to tests also to the test targets. You should not do that. Never ever should you do that. This can lead to hard to debug problems. 2. In TDD you have to run the test *before* you write the production code. Otherwise you cannot prove that the test actually tests something. 3. The instructor uses NSError. In Swift we have now a very powerful error handling. One should use it, when possible. 4. The instructor starts the course with the UI. In TDD the UI is completely irrelevant. 5. In TDD you should only write production code when you have a failing test. The instructor sometimes writes production code first and sometimes test code. This is not TDD. 6. The three steps of TDD are red, green, refactor. The instructor does not refactor (at least up to lecture 13 where I am right now). 7. Performance tests are kind or irrelevant for TDD. You normally use them to improve algorithm code. 8. The instructor writes really poor Swift code. For example we still uses the pyramid of doom.

Really informative course, I try to learn TDD using courses for Java and PHP as before this course a TDD course for Swift did not exist, I am glad it was finally done and Icaro is an amazing instructor he is very careful to explain every single step.

Thanks for finally make a TDD course for us, I always had problems with questions related to "tests" in my past interviews. I am half way in the course and I think I am already prepared to answer any question they can possibly ask me now. Thank you!