Anyone who has encountered non-trivial bugs on android probably knows that, sometimes, it takes a lot of time and effort to fix them. Other times, the situation is even worse - it takes a lot of time to reproduce the bug. There are cases when there is nothing to do but restart the application under different conditions: with a network, without a network, without cache, with a bad network, with erroneous responses from the server, etc. The situation can be aggravated by the fact that constant restarts require a lot of long single-type actions, e.g. filling fields with data. In this article, I want to describe one possible solution to this problem. Let’s get to it Observations and Assumptions It is assumed that you are familiar with adb This solution is suitable for filling fields of XML, compose, webView, and other visual types as well as other applications. Running a script from a scratch file sometimes causes an error. A quick way around the problem is to create another . kotlin There is currently no clean solution. scratch file Selecting an example Let's say we have an application that consists of two activities: and . To go to , you need to fill in the fields in and press : LoginActivity MainActivity MainActivity LoginActivity Enter Code: package com.leonidivankin.draftandroid.articles.autofill

import android.os.Bundle
import androidx.appcompat.app.AppCompatActivity

class MainActivity : AppCompatActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        title = "MainActivity"
    }
} <?xml version="1.0" encoding="utf-8"?>
<androidx.constraintlayout.widget.ConstraintLayout xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:padding="24dp"
    tools:context=".articles.autofill.LoginActivity">

    <EditText
        android:id="@+id/editTextEmail"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:hint="login@gmail.com"
        app:layout_constraintBottom_toTopOf="@+id/editTextPhone"
        app:layout_constraintTop_toTopOf="parent"
        app:layout_constraintVertical_chainStyle="packed" />

    <EditText
        android:id="@+id/editTextPhone"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:hint="+1 650 123 4567"
        app:layout_constraintBottom_toTopOf="@+id/editTextPassword"
        app:layout_constraintTop_toBottomOf="@+id/editTextEmail" />

    <EditText
        android:id="@+id/editTextPassword"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:hint="123456"
        app:layout_constraintBottom_toTopOf="@+id/buttonEnter"
        app:layout_constraintTop_toBottomOf="@+id/editTextPhone" />

    <Button
        android:id="@+id/buttonEnter"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:text="enter"
        app:layout_constraintBottom_toBottomOf="parent"
        app:layout_constraintTop_toBottomOf="@+id/editTextPassword" />

</androidx.constraintlayout.widget.ConstraintLayout> package com.leonidivankin.draftandroid.articles.autofill

import android.content.Intent
import android.os.Bundle
import androidx.appcompat.app.AppCompatActivity
import com.leonidivankin.draftandroid.databinding.ActivityLoginBinding

class LoginActivity : AppCompatActivity() {

    private lateinit var binding: ActivityLoginBinding

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        binding = ActivityLoginBinding.inflate(layoutInflater)
        setContentView(binding.root)
        title = "LoginActivity"

        binding.buttonEnter.setOnClickListener {
            if (binding.editTextEmail.text.toString() == "login@gmail.com"
                && binding.editTextPhone.text.toString() == "+1 650 123 4567"
                && binding.editTextPassword.text.toString() == "123456"
            )
                startActivity(Intent(this, MainActivity::class.java))
        }
    }
} To move to , the fields must be filled in, and their values must meet certain requirements.
For example, take the following values: MainActivity email: phone: +1 650 123 4567 login@gmail.com https://youtu.be/oX3NIZMYpyo As you can see, it takes about 1 minute from startup to . This is still on the assumption that there were almost no errors in filling the data. Sometimes, finding complex bugs requires multiple rebuilds of the application and restarts on the device. This means constant filling of fields to get further into the app. MainActivity It turns out that with each restart we would lose about 1 minute extra. The ideal would be to jump directly into , bypassing , but in large projects, this is most often impossible due to the need to get a token from the server. MainActivity LoginActivity Another possible solution to this problem would be to assign default values to these fields. However, this is not always possible, because the fields may be in an external or in a . In this case, you won't be able to set default values. SDK webView As we continue I’ll show you how you can optimize the filling of the fields with kotlin-script. Autofill fields Finding the necessary adb commands I will use the commands to fill the text fields. To fill one text field, we need: adb Click on the text area. Fill it with text. To click on a text area, you must use the command: adb adb shell input tap x y where x and y are coordinates relative to the upper left corner of the device in pixels (px). They can be found in different ways: There is an that knows how to determine the click coordinates: adb-command adb shell getevent -l But there are difficulties with the translation of coordinates. You can read more . here On the real device, you can enable the developer's settings to display click coordinates or grid. You can add a listener, which will give absolute coordinates at each click. You can also find out through . Layout Inspector In this example, I am more comfortable using paragraph 4. Launch the Layout Inspector. Connect to the current process. Select the necessary . view Check its coordinates. It will depend on the size and type of the device. Most likely, your coordinates will be different. Note that these coordinates are in . And the command needs coordinates in . In my case it is x: 243=72, y: 3643=1092 dp adb px The final command turns out to be: adb shell input tap 72 1092 Go to the terminal and enter this command: The text input field is now active. To find out the pixel density, you need to go to : Device Manager In my case it is . Here the ratio between and is 3. The ratios are described in more detail . xxhdi dp px here Next, you must enter the desired text in the field. To do this, use the command: adb shell input text 'login@gmail.com' Enter it into the terminal and check that the necessary is entered.
Similar actions are carried out with other text fields: . Next, we need to click on the button, for this, there is a command: email phone, password adb shell input tap 72 1497 I've already put the coordinates I need there. We found all the necessary to fill in all the text fields and click on the button. Here is the complete list: adb commands adb shell input tap 72 1092
adb shell input text 'login@gmail.com'
adb shell input tap 72 1227
adb shell input text '+1 650 123 4567'
adb shell input tap 72 1362
adb shell input text 123456
adb shell input tap 72 1497 Now we need to build a script from these commands that will execute them instead of us. Creating a kotlin script You can build a script in different ways and in different languages. Here are some of the options: Make a . bash script Make a plugin for . Android Studio Make , etc. Gradle task But each of these methods has disadvantages. The bash script is difficult to maintain, the plugin for needs to be maintained for new versions of the environment, gradle tasks take a long time to run due to dependencies with and . Android Studio gradle gradle wrapper So I use another way - . The kotlin language is more familiar to the android developer, the script is independent of the project, android studio, and gradle. kotlin-script (kts) Create a scratch file using (Windows). In the window that appears, select : Ctrl+Alt+Shift+Insert Kotlin This will create a file. Notice the green arrow. This means that the file is executable and can be run. Uncheck so that the script won't restart every time you change the file. scratch.kts Interactive mode There is a special method that allows you to execute an from a kotlin script: adb command Runtime.getRuntime().exec() Insert all of our commands. My complete scratch file is as follows: fun run(){
   run("adb shell am force-stop com.leonidivankin.draftandroid")
   run("adb shell am start -n \"com.leonidivankin.draftandroid/com.leonidivankin.draftandroid.articles.autofill.LoginActivity\" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER")
   Thread.sleep(2000)
   run("adb shell input tap 72 1092")
   run("adb shell input text 'login@gmail.com'")
   Thread.sleep(500)
   run("adb shell input tap 72 1227")
   run("adb shell input text '+1 650 123 4567'")
   Thread.sleep(500)
   run("adb shell input tap 72 1362")
   run("adb shell input text 123456")
   Thread.sleep(500)
   run("adb shell input tap 72 1497")
}

fun run(command: String){
   Runtime.getRuntime().exec(command)
} This file consists of the we defined above with some additions. adb commands Note that I inserted the lines first: fun run(){
   run("adb shell am force-stop com.leonidivankin.draftandroid")
   run("adb shell am start -n \"com.leonidivankin.draftandroid/com.leonidivankin.draftandroid.articles.autofill.LoginActivity\" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER") These lines are needed when the application is running and you need to restart it. I also put the command in a separate method to reduce the amount of code: exec() fun run(command: String){
   Runtime.getRuntime().exec(command)
} Note that some commands have between them. This is to wait for the application to start or the previous command to be entered. The point is that adb commands are executed asynchronously. And there is a probability that the focus will be shifted to the next text field without waiting for text input in the current one. Thread.sleep() Total transition time to from launching is not more than 5 seconds, which reduced the time by 20 times. MainActivity https://youtube.com/shorts/R484DB_RScc?feature=share Conclusion As Steve McConnell wrote in Perfect Code, programming is a complicated thing. It gets even more complicated because you have to look for complex and nontrivial bugs. So, from my point of view, the role of any optimizations is rather high. Despite the fact that within the framework of the whole project, they seem microscopic. Try to optimize the launch of your application by autocomplete fields.
If you find bugs or know how else to improve the script, post in the comments.

Super

YouTube

The Effect of Multiple Switching to and From Compose on Application Performance

Practical Tips for Refactoring on Compose

Nominated for 2022 - Android Advocate of the Year

Too Long; Didn't Read

Make resilience your competitive advantage

Autofill Fields with a Kotlin Script

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

6 Ways to Run Kotlin Code in Android Studio

Java bits: 0xFF and 0xFFL

10 Things You Didn't Know You Could Do With Google Keep

10 Things to check on Android code reviews

10 Mistakes In Mobile App Development That Make You Look Dumb

6 Ways to Run Kotlin Code in Android Studio

Java bits: 0xFF and 0xFFL

10 Things You Didn't Know You Could Do With Google Keep

10 Things to check on Android code reviews

10 Mistakes In Mobile App Development That Make You Look Dumb

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps