Proposed Changes

Refactored test cases for DaggerTrack due to the following reasons:

• Over mocking of the classes leading to over specifications in test cases.
• Some of the tests were highly coupled with Gradle API for example ClassPoolFactoryTest
• No functional tests for dagger track plugin
• Due to lack of functional test reliability on test suite was highly reduced
• Adding more tests was becoming a pain when we rely more on mocking.
• Added GradleTestRunner class which helps you to set up a minimal project which can help to set up the environment of tests easily.

Testing

Have refactored all the test cases mostly.

• [x] ClassPoolFactoryTest
• [x] CtClassTransformationsTest
• [x] ClassPoolTransformationsTest
• [x] Added new DaggerTrackPluginTest

Issues Fixed

I add all that you write in the manual:

maven { url 'https://s01.oss.sonatype.org/content/repositories/snapshots/' }

dependencies { classpath "me.amanjeet.daggertrack:dagger-track:1.0.5-SNAPSHOT" }

apply plugin: 'com.android.application'

apply plugin: 'me.amanjeet.daggertrack'

daggerTrack { applyFor = ["debug"] }

implementation 'me.amanjeet.daggertrack:dagger-track-clocks:1.0.5-SNAPSHOT'

All in the right places.

I expect that I automatically see the output in logcat if I filter DaggerTrack. I force stop app and run but there is no DaggerTrack in logcat.

I have to do something else?

Thanks for answer

D/DaggerTrack: Total On CPU time of me.amanjeet.daggertrack.ui.HomeFragment: 2940ms
D/DaggerTrack: Total Off CPU time of me.amanjeet.daggertrack.ui.HomeFragment: 4547ms
D/DaggerTrack: Total time of java.lang.Object: 7487ms
D/DaggerTrack: Total On CPU time of java.lang.Object: 2940ms
D/DaggerTrack: Total Off CPU time of java.lang.Object: 4547ms

For some subcomponents and components, I have noticed that there exists a corresponding java.lang.Object injection which is even not visible in my bytecode. Not sure how it comes.

D8: java.lang.NullPointerException org.gradle.workers.WorkerExecutionException: There were multiple failures while executing work items at org.gradle.workers.internal.DefaultWorkerExecutor.workerExecutionException(DefaultWorkerExecutor.java:266) at org.gradle.workers.internal.DefaultWorkerExecutor.await(DefaultWorkerExecutor.java:246) at com.android.build.gradle.internal.tasks.DexArchiveBuilderTaskDelegate.doProcess(DexArchiveBuilderTaskDelegate.kt:274) at com.android.build.gradle.internal.tasks.DexArchiveBuilderTask.doTaskAction(DexArchiveBuilderTask.kt:275) at com.android.build.gradle.internal.tasks.NewIncrementalTask$taskAction$$inlined$recordTaskAction$1.invoke(BaseTask.kt:66) at com.android.build.gradle.internal.tasks.Blocks.recordSpan(Blocks.java:51) at com.android.build.gradle.internal.tasks.NewIncrementalTask.taskAction(NewIncrementalTask.kt:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Build fails sometimes fails with the above exception when gradle builds continuously runs reusing daemons. For solving this, I have to keep stopping gradle to reuse its daemon through:

./gradlew --stop or --no-daemon switch