Changes to Android instrumentation code under androidTest are not picked up by Buck
See original GitHub issueRunning ./buckw test
will not pick up any changes to Android java test code under src/androidTest/java
.
In order for the changes to be reflected I have to rm -rf buck-out
and ./buckw test
again which of course takes forever.
I can reproduce this every time.
Is this a known issue and/or is there any workaround for this?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Advanced test setup - Android Developers
Create an instrumented test for a build variant; Configure instrumentation manifest settings; Change the test build type; Configure Gradle test options ...
Read more >Android Studio import existing unit tests "Unable to find ...
15 Answers 15 · Go to Run/Debug Configurations · Setup a Android-Test for your test class · Select your Android test configuration on...
Read more >android_instrumentation_apk() - Buck
An android_instrumentation_apk() rule is used to generate an Android Instrumentation APK. Android's Testing Fundamentals documentation includes a diagram that ...
Read more >Shared srcDirs between test and androidTest, unresolved ...
The idea is to share test data between unit tests and instrumented tests. Keep in mind, the tests can build and execute, but...
Read more >Developing Android unit and instrumentation tests - Tutorial
This tutorial describes how to write unit and instrumentation tests for your Android application. It describes how to execute these tests via Android...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
NO_BUCKD=1 fixed the issue for me.
Could one of you provide repro steps?