Running test cases from the "File" Running test cases from the "Edit Configuration" window The alternative option is to run a specific test case or all tests from the opened class. Running test cases from the "Project Tree" Running test cases from the "File" We need to select a folder with the test cases which we want to execute, open the context menu, and select the “Run 'Tests in 'FOLDER''” menu item. Running test cases from the "Project Tree" If you are familiar with different ways of running local tests, I recommend moving to the "Local tests: Use Cases" section. Running test cases using the "Gradle command".Running test cases from the "Edit Configuration" window.Running test cases from the "Project Tree".
We have multiple ways of running local tests in the Andoid project. Storing local tests in the project Running local tests Storing local tests in the projectĮvery Android project already has a predefined place for local tests in the /module/src/test/ folder. When our code has no Android dependencies, we can test it without the Robolectric framework, and in this case, it will be much faster. The non-UI local testing can be done with Robolectric when we have Android dependencies in our code, like Context, Activity, etc. Still, the current version of the Robolectric framework has many limitations, and we cannot verify all screens of the application (Robolectric has issues with testing the NavigationDrawer component). So, we can test the UI of the application with the Robolectric framework. We can split all local test cases into UI and non-UI tests. The local tests are usually executed on one version of JVM with Android dependencies this means that we cannot check how our code works on a different Android OS version. Still, we can run test cases on many devices simultaneously. The instrumentation tests are much slower than local test cases because we spend additional time installing two applications to the device and collecting data from the device to understand each test case's state. Instrumentation test cases require an emulator or device, and we can test Android-specific code with the instrumentation test cases. The main difference between these tests is that the "local" test can be executed on JVM (Java Virtual Machine) and a specific version of JVM with Android dependencies, delivered as part of the Robolectric library, which allows us to test Android-specific code. There are Local and Instrumentation test cases. In the Android world, we have different types of test cases, which allow us to test both Android-specific code and Android independent code. Today I want to talk about different types of Android test cases, examples, and how to run them from Android Studio, Gradle, and ADB commands.
Local and Instrumentation tests in Android.This article is a part of the "Efficient Android testing" series:
0 kommentar(er)
