very nice and concise ! speaking about comparing the error messages at 13:13 I think it would be better to throw errors or have an enum with a raw type String which defines these messages
Follow BDD (Behaviour Driven Development). With which we can cover all the interrelated dependencies for a particular flow also, the Views methods (not the actual UITests) are also covered under this. So ultimately we achieve close to more than 90% test coverage minimum. When I say BDD I actually mean business use cases for any SUT rather than individual methods. If we cover all the use cases all the methods (even private) will be covered. If any method is not covered, then we can safely remove this method as its not at all reachable and its unused.
Thank you! This is clearest description I have seen
Such an amazing explanation! Thank you so much!
very nice and concise ! speaking about comparing the error messages at 13:13 I think it would be better to throw errors or have an enum with a raw type String which defines these messages
Great video and better explanation. Subscribed.
Fantastic work!
very insightful sir thx
Amazing explanation👍👍
Very interesting video!
Very good on begging unit test, but nothing related to SwiftUI.
Thanks a million!
Follow BDD (Behaviour Driven Development). With which we can cover all the interrelated dependencies for a particular flow also, the Views methods (not the actual UITests) are also covered under this. So ultimately we achieve close to more than 90% test coverage minimum. When I say BDD I actually mean business use cases for any SUT rather than individual methods. If we cover all the use cases all the methods (even private) will be covered. If any method is not covered, then we can safely remove this method as its not at all reachable and its unused.
you are perfect
great