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!
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
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.
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..
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!
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
I think you should do a followup video about Mocking (Mockito or Mockk) and verifying mocks, because I think that actually nobody uses "fake components"
hi Philipp. you used `TestInstallIn` annotation and `replaces` in your recent test cources and, you didn't use `UninstallModule` there. What is the difference between these methods?
I also realized that redefining Compose and its navigation stuffs in the setUp function is no longer necessary. createAndroidComposeRule starts the activity already, and Compose components are ready to test there.
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 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
It seems that you've assigned the tag to the OrderSection's Modifier and forgot to use that passed modifier inside OrderSection. As a result, the node not be present in the tree and causing the test to fail.
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.
Hi man, not Philip but the tests should be on the same project, on the com.test directory for unit tests and com.androidTest for the Instrumentation tests and UI tests, hope this helps.
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 😊
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?
I am also not liking how the composable are copied into the test class.We're basically maintaining the same code for the main code and the test code. How can you make It tidy and not copy the code?
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?
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'
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 ?
it would be super cool if you could a video like this one ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-IvFSJVTGDb4.html, basically refactoring the app to use modules instead.
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
Hope you make a TDD video covering outside-in and classicist approach using uncommon convention where test classes are suffixed with the word "should".
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)
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
It seems that you've assigned the tag to the OrderSection's Modifier and forgot to use that passed modifier inside OrderSection. As a result, the node not be present in the tree and causing the test to fail.
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.
mock objects make sense when you have something with tons of functions. Implementing a fake for that would require you to write an implementation for all these functions. With a mock you only implement the ones needed. Most of the times, mocks actually make more sense
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.
Well - the guy has to make his money from this somehow - you know how much time it takes to make such good quality content? Cmon - your comment is disrespectful!
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 🫡
