this 'testing' chapter of this playlist is very tough, but i'm learning sooooooo much because of you. Haven't seen any better, free videos about testing. Thank you so much.
Haha thanks, it is defo more advanced than the other vids. So take your time and rewatch it as many times as needed till you fully grasp the concepts 👌🏾
Hello, can you explain how i can i read the iOS simulator or the real device console logs while the UI test execution is in progress just to validate few scenarios based on console logs?
Awesome video as usual 🙌🏾 I always thought the purpose of integration test or UITest in this case was also to validate the API. So basically write the happy case without mocks and if it fails then something isn’t working as expected therefore helping you catch actual bugs. With this setup if there is breaking change from the API the test would still pass right?
Integration tests are meant to validate a real service. UI tests on the other hand validate the UI is correct. In both cases yh, if the API data structure was to change then the test should fail since the decoder wouldn’t be able to decode it 👌🏾
Great use of enums for type-safety. Really paying off in building these tests! Question: I know that we wrote tests for EVERY data element returned from our network call. How should I cover enough when dealing with over 500 read-only data elements that are merely processed into strings that represent some derived data? I would think all derived data should be covered by tests and maybe display-only data not tested - but curious as to how you would approach this situation? Thanks again for this great content!
Thanks & if you have a large data set you’d probs want to have some local json or a string in your test resources & use equatable to compare both objects to check that they’re the same 👌🏾
@@tundsdev Cool. I can use the same JSON that I used to develop my views in the early going. Makes total sense to check object vs. object rather than every branch in the JSON tree. Thanks for the quick reply sir.
Yh this was a very simple example where the dataset wasn’t too large, in big objects you 1000% want to compare objects since its easier, maintainable & scalable too 👌🏾
My question is, if I have 10 items on that grid where 6 are visible then gridItems.count will return 6. But how to get the count of all 10 cells?? @@tundsdev
this 'testing' chapter of this playlist is very tough, but i'm learning sooooooo much because of you. Haven't seen any better, free videos about testing. Thank you so much.
Haha thanks, it is defo more advanced than the other vids. So take your time and rewatch it as many times as needed till you fully grasp the concepts 👌🏾
Hey man, thank you for your work! It's awesome! I see you doing new videos almost every day. My respect! 👍
Glad you enjoy the content 👌🏾
Hello, can you explain how i can i read the iOS simulator or the real device console logs while the UI test execution is in progress just to validate few scenarios based on console logs?
Awesome video as usual 🙌🏾
I always thought the purpose of integration test or UITest in this case was also to validate the API. So basically write the happy case without mocks and if it fails then something isn’t working as expected therefore helping you catch actual bugs.
With this setup if there is breaking change from the API the test would still pass right?
Integration tests are meant to validate a real service. UI tests on the other hand validate the UI is correct. In both cases yh, if the API data structure was to change then the test should fail since the decoder wouldn’t be able to decode it 👌🏾
Great use of enums for type-safety. Really paying off in building these tests! Question: I know that we wrote tests for EVERY data element returned from our network call.
How should I cover enough when dealing with over 500 read-only data elements that are merely processed into strings that represent some derived data? I would think all derived data should be covered by tests and maybe display-only data not tested - but curious as to how you would approach this situation?
Thanks again for this great content!
Thanks & if you have a large data set you’d probs want to have some local json or a string in your test resources & use equatable to compare both objects to check that they’re the same 👌🏾
@@tundsdev Cool. I can use the same JSON that I used to develop my views in the early going. Makes total sense to check object vs. object rather than every branch in the JSON tree. Thanks for the quick reply sir.
Yh this was a very simple example where the dataset wasn’t too large, in big objects you 1000% want to compare objects since its easier, maintainable & scalable too 👌🏾
Your grid has exact 6 items or at a time 6 items are visible in screen?
I’m testing there are 6 items visible on the screen at that time
My question is, if I have 10 items on that grid where 6 are visible then gridItems.count will return 6. But how to get the count of all 10 cells?? @@tundsdev