# Lessons Learned from Removing Android UI Tests from the CI Pipeline

DevFeed: [Lessons Learned from Removing Android UI Tests from the CI Pipeline](<https://devfeed.tech/articles/do-androids-dream-of-ui-testing-29356.md>)

Original publisher: [Read original article](<https://arturdryomov.dev/posts/do-androids-dream-of-ui-testing/>)

Author: Artur Dryomov

Published: 2018-05-26T00:00:00Z

Content type: article

Language: en

Sources: [Artur Dryomov](<https://devfeed.tech/sources/artur-dryomov.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [ui-testing](<https://devfeed.tech/topics/ui-testing.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Android](<https://devfeed.tech/topics/android.md>), [ci](<https://devfeed.tech/topics/ci.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [automation](<https://devfeed.tech/tags/automation.md>), [ci](<https://devfeed.tech/tags/ci.md>), [testing](<https://devfeed.tech/tags/testing.md>), [ui-testing](<https://devfeed.tech/tags/ui-testing.md>)

## AI overview

This article shares lessons learned from removing Android UI tests from a continuous integration pipeline. It discusses the testing pyramid, the maintenance cost and flakiness of UI tests, and the role of unit tests and abstractions in creating maintainable tests.

## Source excerpt

Automation is a foundation stone of the software development. People didn't like counting numbers themselves, so they invented calculators. Calculators went to be computers and here we go, waiting for AI to take over, watching movies about transhumanism on our way here. Automation related to UI testing seems to be a Holy Grail from that standpoint. Sure thing, it can replace manual QA procedures with automated ones! Like, completely! You just need to have a local backend... And maybe disable animations. And... you know, somehow wait for backend responses. And don't forget about the infrastructure.