Thank god for your existence man.

This is exactly the content KZfaq is lacking ! Thank you for making this !

You are doing a great job philipp... I am watching your videos again and again. Just in love with your way of explaining things...😘😘

Your tutorial are clean as your architecture ! Insane content, it save me a lot of times !

28:44 that was the perfect description of the feeling! :D:D Thanks for your work Phillip!

That's a priceless content there, clear & to the point. Well done.

Thank you. Love to see more video on Compose UI testing

Phillipp, you decided to destroy me. I don't do almost anything but watch your videos. I absolutely fell in love💘💘 . You are the best teacher in the world! Thank you very much!

Incredible testing content, thank you so much! I can't even. This is awesome!

if you want really gain knowledge about android it is right channel , I have learnt lot of from it thank you philipp

I've just finished it . The more time passes , the more people realize the value of this video

Man, thank you for uploading this video. This is really helpful to me

Keep doing this. For sure you are helping many people out here.

Thanks again Philip! Amazing video again !

Am late but not out. This is amazing. This was long overdue.

Amazing job, as always. Thanks

Thanks Phillip for this amazing content.

Thanks, Philipp for this Awesome video

It's so great that you cover such important topic, in our company a skill in Unit testing is even mandatory for Junior/Intern position, because it's so crucial to write tests (nobody will write them for you if you create a pull request), and so many candidates are rejected because of the lack of this skill Also it is amazing that you do so with one of your current poroject, many courses cover it as "I HaVe A hAmBuRgEr ClAsS, lEtS WrItE UnItTest", and the skill of testing on a living project is really crucial Huge +1 form me

hey man , thank you very much , you really conquered our hearts, god bless you

thanks, learned a lot !!

Was looking something like that you seem to know your audience very well !!

Hope you make a TDD video covering outside-in and classicist approach using uncommon convention where test classes are suffixed with the word "should".

this was a very helpful video, learnt a lot about test structure,very useful for a developer new to testing

Very important and usefull video!

Thank you very much!

finally thank you for your good explanation. easy to understand

Amazing! Tanks a lot! Change : Unit Tests, UI Tests, End-to-End Tests => Unit Tests, Instrumented Tests, End-to-End Tests If you would prefer as well.

Wow thank you so much♥️♥️

Awesome tutorial thank you rly.

thanks for sharing!

Thank you very much 🥰

I love you phillipp, you are the best of the world, tks

Great job!!

Thanks Philip very mush

Was nice to see how you do testing, thanks for sharing! Let me comment on what I noticed while watching: 1) When testing the GetNodes UseCase, you're faking the repository instead of the dao. This has the setback that the behavior of the fake might not mimic the actual repositories implementation, especially over time when your code and structure changes. When you refactor you repository code, you might change e.g. the semantics of getNodesById -- say for exception handling. When you have tests for your repository separately, you'll adjust them since they broke. But you'll certainly forget to adjust this UseCase test. This will result in this UseCase test becoming useless. Things will improve when you fake the dao, since changes to the semantics of the dao will happen less often -- and of course you'll find issues due to changed repository semantics. If you have concepts on your mind how to avoid that your UseCase test becomes useless following your presented test pattern because it's not updated on changes of dependencies, I'd be glad to hear about that. 2) Keep your tests as tidy as you keep your production code, the same principles apply -- especially DRY, so don't just copy&paste, it will give you headaches later. 3) Why are you using the @Throws annotation in your AddNote UseCase? Are you planning for Java interop?

Thank you very much

You are the best. I have learned a lot by your tutorials. Can you please upload a video for all Functional Tests, Unit Test, instrumentation test and UI test in Java. ? Even if it's a paid version, it is ok.

you are the best 🥰🥰thank you so much

Holy ****! Thank you!!!! Philipp breaking the android community!!!

1. So I already understand how to put the UI in the layout .. 2. Making the UI to be clickable 3. Making the UI to scroll And yes you're right that I need my build time to be faster.. And I am interested how to integrate unit test with a mocking object of the android components.. Hopefully I can finish this

Awesome love you

Hey Philipp, sorry if you mentioned this before but are you gonna make either Flutter, React Native, or KMP tutorials? I love you're well-paced and properly architectured teaching style. I've had enough of other tutorials that teach you how to make a todo list app in 5 minutes all in one class. I want a professional, longer, well-pace, and architectured multiplatform tutorial.

Please can you make this same video but for projects making network calls? Projects that use coroutines and flow as well like this one

great video, can you make testing for viewmodel using stateflow

Aw yeeessss an update! 😎

How do you test the delete notes usecase? It seems I would need to add an extra method inside the DeleteNotes usecase to return the repository and check whether the note is there or not

Thanks 😘

Great work! ,Could you please include webview UI test case in jetpack compose

Hey philip I have enjoyed this video and please make one video with adding AI in application

Man you're an Android beast)))

Please please make a detailed video on Bound Services.

thanks for the video

Wow Perfect

Basically iam a single web application tester in my company. As part of the new project they assigned me as Android tester so just guide me What's the exact thing to do in this . They just telling to test Android devices. As part of KT They just delivered some kind of stuff but unfortunately idint get it . CTS VTS GTS. Iam fully confused that what they actually talking about .... Finally make a video from Scratch who is starting their carrier as Android testing Thank you 😊

Plzz make video on binding adapter Philipp 🙌🏻

In Android Studio are there any limitations in using AndroidX&Junit5 for instrumented tests?

I'm getting Dagger duplicate binding error even after using UninstallModule on my AppModule in the test class. Do we need to do something more to fix this? How can it have duplicated binding when AppModule is already uninstalled fromt the test class

28:43 made me laugh out loud! It is true though.

I feel like i won lottery ,thanks phillip 💚💚

Hi, Phillip, I have a question, I have a production-level project but it does not contain any tests so if I were to implement unit tests in that same project can I add the tests to the production level directly or I should create a separate project for tests that will be separate from production also what is the industry standard? and thank you for reading it.

hey, in Spotify play list in video 13 there are more than 10 person have the same problem in comment of "@Quang Đạt" please if anyone can help tell us if u can't set Like to make philipp see it please..

Hi Man, do you have premuim testing course?

Love you Sir....

how would you just test the view model here? I tried mocking the SavedStateHandle but I get an error about duplicate bindings (I just bind the SavedStateHandle in the TestAppModule object class)

The unexpected uss of the word "orgasm" got me 😂

The instrumented test fails, it can't find a view with given tag. useUnmergedTree = true does not help. Adding a delay does not help. Using tags the same way on other views works fine. assertExists also fails. Any ideas? e/ Also the EndToEnd test fails because it's missing focus on the first action. [e: No input session started. Missing a focus?] Think update to composable introduced focusModifier?

🔥

It's the orga*m part for me. Hahahahaha love your tutorials

one question. when to use fake objects and when to use mockk to mock objects?

if you refactor this great app to multi module it will be our document to architect our apps ... thx

It's 2023 and I can't run this project with latest versions of... all the stuff that it's using. I spend half a day and still no success. This is crazy.

I am late to this video, Code is very hard to build now. Can you update code base.

Reason: Expected exactly '1' node but could not find any node that satisfies: I am following the same steps as you for my composable but still getting this error. In my composable, however, I call other composables and the node with the tag is located in one of them

How to properly run your source code? I like all your tutorials, but I actually never successfully run any of them...

Sir please make a video on how to Use FIREBASE with Jetpack Compose

I got the required knowledge for different types of android application tests, the video is just amazing and you really doing a very great job doing your huge efforts in making this free up to dated content for the android developers, I am really happy following or subscribe your channel, keep it up boy, Salute 🫡

28:41 🤣🤣🤣🤣

Y O U A R E T H E B E S T

As always... what a crack

I love that in your testing videos, when your tests fail, you think there is something wrong with the test function. 😂😂😂 Pretty ironic.

it would be super cool if you could a video like this one kzfaq.info/get/bejne/f9x2hq2Hua2okmg.html, basically refactoring the app to use modules instead.

Please don't teach to add randomisation in unit tests. Other than that, there is a lot of useful info here. Thanks for the video!

How to test with real rest api? Let say my screen needs to perform api request? How to make unit test wait for api to finish?

Your explanation is wrong. Unit tests don't test a component class or function but a feature. This is the big misunderstanding which is also mentioned by Uncle Bob. Implementation details like inner classes should never been tested separately but tested as a black box. Tests should trigger your ViewModel and expect an effect on your ViewState, Database or Http-Request. You never should test something in between!

down voting way too many ads

The setup boilerlate is huge for the instrumented tests.

Thanks for your video Philipp! This was very educational and I learnt a lot from it. For some reason, during my Integration section following the tutorial, I kept on getting the error "java.lang.AssertionError: Failed to perform isDisplayed check. Reason: Expected exactly '1' node but found '4' nodes that satisfy: (TestTag = 'ORDER_SECTION')" for the function clickToggleOrderSection_isVisible. Not sure what I am doing wrong

getting this error. please help. -> android.content.ActivityNotFoundException: Unable to find explicit activity class {com.samm.brewerysearch.test/androidx.test.core.app.InstrumentationActivityInvoker$BootstrapActivity}; have you declared this activity in your AndroidManifest.xml, or does your intent not match its declared ?

Anyone gave this a try? I get an error when I run the Integration test, the trace says: Caused by: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':app:debugAndroidTestRuntimeClasspath'

instead. of composerule.setcontent do composerule.activity.setcontent

composeRule.activity.getString(resId = R.string.my_string)