Hi, Mitch, I'm thinking about purchase this course on your site, I generally watch your videos and they are all quite good. But I have one thing in my mind, does this course meet all expectations for the business industry, I mean the testing part. Thanks in advance,
A better course for testing is the clean architecture course. It showcases a real practical way to build out your backend layers and write tests for then
@@codingwithmitch I am all okay to your suggestions, I just wanna learn this stuff very well and there is barely source at least i couldnt find much but your videos
I was watching Room persistence library and in which you used Asyctask, I didn't find any proper way to ask a question because on youtube this lecture was not available. So I am posting here kindly I need help regarding abstraction My question is how we abstraction hides the real implementation of the abstract method. if we look asynctask you will see an abstract method name {doinbackground} this as annotation of workerthread, now the question is where is the real implementation of this method, how this method become asynchronous. If you did not get my question then here is an example on upload StackOverflow.
I don't know what you're asking. But it sounds like you are overthinking it. Also, you shouldn't really use AsyncTask anymore. There's a lot of much better options. Things like: 1) RxJava 2) Kotlin Coroutines 3) and even Executors The Room Persistence library course is for beginners. Now that you're done it, you should check out another course and move to the next level. I recommend this one: codingwithmitch.com/courses/rest-api-mvvm-retrofit2/
A small remark in 8:37, your presentation of Test driven development is absolutly wrong, and it's exactly the inverse of what you are saying. In a test-driven development environment, you code the test first, considering your class or your logic unit as a black box. It's what is so difficult to learn for beginners who are used to code the feature and then develop test for that feature (which is an absurd thing to do). If you have coded something, and you test it by having a knowledge of how it works inside, you will subconsciously code the test in accordance with this logic. That is why you need to code the test first, to put a certain standard, and then code something that meets that standard ; and iterate over the standard/exigence that you put on that feature to develop more robust tests.
You're the man. Happy wedding day Mitch!
Hi, mitch. Could you please do a tutorial on how to do unit testing on retrofit calls in mvvm architecture?
You are the best person I have ever come across.
Very good, Mitch. I like your videos.
Glad you like them pal
best teacher I have ever come across
thank you so much🤩🤩🤩
Mitch is the 🐐
Great explanation but TDD is not exactly what you said, first you write the test that not pass then you implement the feature to make the test pass
that's what I said
@@codingwithmitch really at 8:28 you said the opposite
Thanks
Sir, please make a video how to use restful api in android and what are the things that we have to know before jumping into restful api
You have always been a awesome gentle teacher.
Could you make a tutorial on using socket in Android?
I want to do someting with Socket.io hopefully this year
@@codingwithmitch excited!
Your definition of TDD is wrong
The longest ad I ever seen
Hi, Mitch,
I'm thinking about purchase this course on your site, I generally watch your videos and they are all quite good. But I have one thing in my mind, does this course meet all expectations for the business industry, I mean the testing part. Thanks in advance,
A better course for testing is the clean architecture course. It showcases a real practical way to build out your backend layers and write tests for then
@@codingwithmitch I am all okay to your suggestions, I just wanna learn this stuff very well and there is barely source at least i couldnt find much but your videos
@@bluebird5600 I got good stuff my friend. Clean architecture is what I recommend.
@@codingwithmitch 👍🏻thanks man, and pls keep making these i appreciate your work
Hello Mitch
I became a member today. Lets see how it goes !
You will definitely love it
I was watching Room persistence library and in which you used Asyctask, I didn't find any proper way to ask a question because on youtube this lecture was not available. So I am posting here kindly I need help regarding abstraction My question is how we abstraction hides the real implementation of the abstract method. if we look asynctask you will see an abstract method name {doinbackground} this as annotation of workerthread, now the question is where is the real implementation of this method, how this method become asynchronous. If you did not get my question then here is an example on upload StackOverflow.
I don't know what you're asking. But it sounds like you are overthinking it.
Also, you shouldn't really use AsyncTask anymore. There's a lot of much better options. Things like:
1) RxJava
2) Kotlin Coroutines
3) and even Executors
The Room Persistence library course is for beginners. Now that you're done it, you should check out another course and move to the next level.
I recommend this one: codingwithmitch.com/courses/rest-api-mvvm-retrofit2/
How old are you?
btw Good shirt man!
It is an amazing explanation till the 11:00 but from 11:23 to 11:46 I fall in love with you ...It's loving, I have no wording...Thank you
Can we use Espresso for Unit testing in Android?
espresso is for ui testing
A small remark in 8:37, your presentation of Test driven development is absolutly wrong, and it's exactly the inverse of what you are saying.
In a test-driven development environment, you code the test first, considering your class or your logic unit as a black box. It's what is so difficult to learn for beginners who are used to code the feature and then develop test for that feature (which is an absurd thing to do).
If you have coded something, and you test it by having a knowledge of how it works inside, you will subconsciously code the test in accordance with this logic. That is why you need to code the test first, to put a certain standard, and then code something that meets that standard ; and iterate over the standard/exigence that you put on that feature to develop more robust tests.
hi, is there a way where I can pay only for a unit test course instead of subscription?
Nope only monthly or yearly subscription for unlimited access to all courses.
41 k views and 41k subscribers at the time 😂