Correction - 1 - Compile-time annotations run at compile-time, before you RUN not before you COMPILE Correction - 2 - the I in SOLID stands for Interface Segregation Principle, it's the D that stands for Dependency Inversion (of control)
integration tests can assert that a certain action (such as button press) will result in a specific call chain (viewmodel->repository->api service) for example.
Integration tests usually focus on the next service in the pipeline. There is also the component test layer that tests a group of units, essentially the next level in the pyramid above unit tests. So, Unit, component, integration, end to end/UI, then manual at the top. A lot of companies skip integration and component tests. The shift left approach adopts more of the component and integration so errors are found sooner, hence the shift left approach.
Sir your are amazing 🤩.i am also android app developer and i have 2 years experience just started my journey. Now i am going to start compose as well is it ok?
It really depends on the company. Most larger companies I have interviewed with include both, but the smaller firms are more Android specific. Just my experience, ymmv.
Correction - 1 - Compile-time annotations run at compile-time, before you RUN not before you COMPILE
Correction - 2 - the I in SOLID stands for Interface Segregation Principle, it's the D that stands for Dependency Inversion (of control)
integration tests can assert that a certain action (such as button press) will result in a specific call chain (viewmodel->repository->api service) for example.
Inversion of control (IoC) is a design pattern in which custom-written portions of a computer program receive the flow of control
Love the sense humour as much as your content! Keep up the good work 🍻
Integration tests usually focus on the next service in the pipeline. There is also the component test layer that tests a group of units, essentially the next level in the pyramid above unit tests.
So, Unit, component, integration, end to end/UI, then manual at the top.
A lot of companies skip integration and component tests.
The shift left approach adopts more of the component and integration so errors are found sooner, hence the shift left approach.
Amazing. Please bring us more stuff like this. Keep it up, mate. Even with years of experience I learned many.
Very helpful, thank you. Looking forward to more videos like this!
andrew tate on android interview
without all the money, sedge
Very good, Very clear ... and wonderful effort ... please do more 😊😉
Amazing. Bring to us some more. This gives me inspiration to include some of this into my own interviews. Thanks
Sir your are amazing 🤩.i am also android app developer and i have 2 years experience just started my journey. Now i am going to start compose as well is it ok?
Amazing!
do you know if we have to focus more on android stuff or leetcode problems? both maybe? Thanks! you are cool
I am currently traveling abroad, but when I come back I plan to make a complete video about this
@@odayprogrammer General summary maybe? Please? Since i am in the process now and i could potentially waste time.
It really depends on the company. Most larger companies I have interviewed with include both, but the smaller firms are more Android specific. Just my experience, ymmv.
@@Another0neTime thank you!
make more please
you are amazing
Thanks man