am getting

Component not initialized

when running tests

I created

AndroidManifest

inside

androidTest

added

tools:node="remove"

to disable automatic initialization but still failed to create the hilt component for testing. In my case it's not merging at all with the

main

app manifest. So I ended up refactoring the startup, removing manifest initialization for the

main

app altogether and manually triggering the startup inside the Application class. Not ideal, but I didn't had any espresso UI testing issues before migrating Dagger to Hilt.

@Marko Novakovic @Jay Barria Thank you for your replies. Sorry, I noticed your replies only now, so I will work on it now, trying your recommendations, too.

Got same issues… so in short you avoid the manifest init