Posted by Jose Alcérreca, Android Developer Relations Engineer

 

As apps improve in performance and complexity, manually testing them to confirm conduct turns into tedious, costly, or unimaginable. Trendy apps, even easy ones, require you to confirm an ever-growing listing of take a look at factors corresponding to UI flows, localization, or database migrations. Having a QA group whose job is to manually confirm that the app works is an possibility, however fixing bugs at that stage is pricey. The earlier you repair an issue within the growth course of the higher.

Automating assessments is the perfect method to catching bugs early. Automated testing (to any extent further, testing) is a broad area and Android provides many instruments and libraries that may overlap. Because of this, newbies typically discover testing difficult.

In response to this suggestions, and to accommodate for Compose and new structure tips, we revamped two testing sections on d.android.com:

Coaching

Firstly, there’s the brand new Testing coaching, which incorporates the basics of testing in Android with two new articles: What to check, an opinionated information for newbies, and an in depth information on Take a look at doubles.

Faking dependencies in unit assessments

After offering an summary of the speculation, the information focuses on sensible examples of the 2 most important kinds of assessments.

• Native assessments that run on a workstation and are sometimes unit assessments.
• Instrumented assessments that run on a tool. This part contains an introduction to UI assessments and the AndroidX Take a look at libraries.
  

  Faking dependencies in UI assessments

  Instruments Documentation

  Secondly, we up to date the Testing part of the Instruments documentation that focuses on all of the instruments that enable you to create and run assessments, from Android Studio to testing from the command line.

  

  The Unified Gradle take a look at runner.

  We included an article that describes Superior take a look at setup options corresponding to working with completely different variants, the instrumentation manifest choices, or the Android Gradle Plugin settings.

  These two new sections ought to provide you with a basic notion of how and the place to check your Android app. To study extra about testing particular options and libraries, you must take a look at their respective documentation pages. For instance: Testing Kotlin flows, Take a look at Navigation, or the Hilt testing information.

  Sadly, machines cannot robotically confirm the correctness of our documentation, so when you discover errors or have strategies, please file a bug on our documentation challenge tracker.