Too Long; Didn't Read
Automated tests are king. Reading any modern programming book like <a href="https://www.amazon.com/Working-Effectively-Legacy-Michael-Feathers/dp/0131177052" target="_blank">Working Effectively with Legacy Code</a> and it is obvious to see why coders just can’t get enough. Usually, the main focus of our automated tests is on the correctness of our business logic. However, there is one form of automated testing that is maybe too oft neglected and that is the measuring of your app’s Jank. Jank is the term that is used when your app drops frames usually due to poor performance. Analogous to how unit test provide quick feedback about correctness, wouldn’t it be great if we had performance test that provides quick feedback about Jank (or hopefully, lack thereof)? Here is a post on how we can combine <a href="http://kotlinlang.org/" target="_blank">Kotlin</a>, <a href="https://developer.android.com/training/testing/ui-testing/uiautomator-testing.html" target="_blank">UI Automator</a> (or any UI automation tool) and <a href="https://developer.android.com/training/testing/performance.html" target="_blank">gfxinfo</a> to create such a test.