Manually edit run configuration as workaround for lacking run check in Android Studio Bumblebee
This text was initially revealed at vtsen.hashnode.dev on March 28, 2022.
I observed in Android Studio Bumblebee, we won’t Run Take a look at anymore from the Android Studio UI. It looks like is a recognized concern right here and supposes it must be mounted on this model already, however in some way I nonetheless have the problem?
Anticipated Conduct
- From the supply code editor
- From proper click on folder / file
Android Studio Bumblebee
- From the supply code editor, it reveals Nothing right here
- From proper click on folder / file, Run Checks… menu shouldn’t be there
Workarounds
I am not a unit testing man. Perhaps I am lacking one thing right here as a result of it looks like nobody complains about this? Anyway, these are the workarounds primarily based on my restricted data in testing.
1. Use Totally different Android Studio Model
I suppose you possibly can roll again to earlier secure launch model Arctic Fox or improve to the most recent preview model. I personally strive Android Studio Dolphin (Canary construct preview model) and haven’t any points.
2. Manually Edit Run Configuration
- Go to app->Edit Configuration…
- Add Gradle job
- Give the gradle job title (any title) and specify the gradle venture (primarily based in your venture folder title)
- Add this Activity
:app:testDebugUnitTest
--tests "com.instance.myapplication.ExampleUnitTest"
This run all check capabilities in
ExampleUnitTest. If you wish to run all lessons throughout the bundle, you should use the*
--tests "com.instance.myapplication.*"
-
So it seems like this
-
Run the unit check
To run unit check in command line, you possibly can run the next command within the terminal
gradlew :app:testDebugUnitTest --tests "com.instance.myapplication.ExampleUnitTest"
To run particular unit check operate (e.g.
ExampleUnitTest.addition_isCorrect), you simply must replace the duty to
:app:testDebugUnitTest --tests "com.instance.myapplication.ExampleUnitTest.addition_isCorrect"
For instrument check, you additionally must manually add it, just like the unit check run configuration above.
- Go to app->Edit Configuration…
- Add Android Instrumented Checks
- Choose ** All in Bundle**
- Choose Module and Bundle
- So it seems like this
- Run the instrumented check (just like the unit check above)
The above steps run all instrumented checks below the specify bundle. If you wish to run check in specify class, simply select Class as a substitute of All in Bundle and specify the category title you need to run.
To run instrumented check in command line, you possibly can run the next command within the terminal
gradlew :app:connectedDebugAndroidTest
Conclusion
I really feel troublesome to manually add the run configuration, particularly I need to run a single check that’s newly added. Perhaps I ought to simply transfer up my Android Studio model to the most recent preview construct to do away with this downside.
