Profile cover photo
Profile photo
Valera Zakharov
A human being with geeky tendencies (which seem to be getting worse with time).
A human being with geeky tendencies (which seem to be getting worse with time).


Fellow Android devs! If you haven't already, could you take this short (and completely anonymous!) survey about testing?
Thank you!
Add a comment...

Post has shared content
Android Testing (Android Dev Summit 2015)

Writing automated software tests should be a fundamental part of your app development strategy. Writing tests helps you to quickly catch and fix software regressions introduced by code changes to your app. In this talk, we'll give you an overview of the testing tools and frameworks provided by Google and show you how they can help you to iterate more quickly and maintain a more healthy codebase.

+ Android testing blueprint:
+ Android testing samples:
+ Android testing codelab:
+ Automated performance testing codelab:

#androidtesting #androiddev #androiddevsummit2015 #perfmatters
Add a comment...

Post has shared content

Post has shared content

Post has shared content
Nice work!
We’ve just released a new version of the Android Testing Support Library

This is mainly a bug fix release which includes fixes for Android Marshmallow, JaCoCo Code Coverage, Test Sharding and a more reliable way to close and synchronize with the Android software keyboard. For a comprehensive overview of the new features and fixes please refer to our release notes[1]. To get started with the latest version of ATSL, follow these instructions[2].

With this release we’re also announcing the deprecation of Android-Test-Kit [3]. We created a brand new website[4] dedicated only to ATSL. This website contains documentation, samples, downloads and more. Our support forum has also moved to a new home and can be found here[5].

The samples on github[6/7] have been updated to reflect the latest version of ATSL. New bugs should be filed against our new component on the AOSP bug tracker[8/9] and last but not least, we have a new logo, yay :-)

Happy testing from the ATSL team +Stephan Linzner, +Nick Korostelev & +Jose Alcérreca

[1] Release notes -
[2] Getting started -
[3] Android-test-kit -
[4] ATSL github page -
[5] Support forum -
[6] Testing samples -
[7] Testing blueprint -
[8] ATSL bug -
[9] ATSL feature -

#androidTesting #buildBetterApps
Add a comment...

Post has shared content
Add a comment...

Post has shared content
Nice one.
Do you understand how Espresso IdlingResource works? Take this quiz to find out! Fork the repo and make the test pass. Post your answer as a comment here. The solution will be published in two weeks.

#GDE   #Android   #Article  
Add a comment...

Post has shared content
More samples.
Last week we published a small but important sample for Espresso Intents on GitHub. It shows you how to fake an ActivityResult to keep your test hermetic, stubbing an Intent and simulating that a picture is fetched from the camera without leaving the main app.

We prefer short, focused UI tests to long end-to-end or flow tests. Espresso Intents lets you stay in your Activity and focus on your code. 

Take a look:

#espresso  #espresso-intents #androiddev  
Add a comment...

Post has shared content
At Google I/O 15 we announced the release of the latest version of the Android Testing Support Library[0].

This release includes three major updates:
Espresso-Web[1]: an Espresso-like API for automated UI testing of hybrid Android applications. Use Espresso-Web to test and interact with any WebView and seamlessly integrate it with your native Espresso UI tests.
Accessibility-Checks[2]: is a set of Accessibility checks that once enabled will automatically perform accessibility checks on your views. The good news is, that once these checks are enabled, they are performed automatically and you get the accessibility testing more or less for free.
Junit/Dagger/Hamcrest: In this release we did a lot of internal clean up. We bumped up the JUnit version to 4.12, we now use the new and shiny Dagger 2 and we upgraded Hamcrest to 1.3, which was one of the most flagged bugs on the bug tracker.

All samples[3] have been updated to use Runner/Rules 0.3, Espresso 2.2 and the new @VisibleForTesting annotation from support-annotations[4].

Of course, we have also squashed some reported bugs and addressed minor feature requests from android-test-kit[5]. See release notes[6] and javadoc[7] for details.

This is also the first release that includes some AOSP contributions. Shout out to +Jake Wharton for DisableOnAndroidDebug* Rule and +Eric Denman who contributed gravity support for DrawerActions. Thank you both for your contributions and feedback! 
If you are interested in contributing to ATSL, please refer to our external contributions guide[8]. 

Happy testing from the ATSL team +Valera Zakharov+Nick Korostelev+Jose Alcérreca and +Stephan Linzner 

#AndroidDev   #AndroidTesting   #happytesting   #io15  

[1] Documentation coming soon!
[2] Accessibility Checks -
[3] Samples on Github -
[4] VisibleForTesting Annotation -
[5] Android-Test-Kit Issues -
[6] Release Notes -
[7] Javadoc -
[8] Guide to external contributions -
Add a comment...

Post has shared content
We just pushed a new sample for ServiceTestRule to Github[0].

ServiceTestRule is one of our new Android JUnit4 Rules for testing integration with an Android Service. This class replaces the ServiceTestCase class in the platform, however ServiceTestRule is a real integration test that actually starts your service under test. For more details please refer to the README[1] file in the project.

[0] ServiceTestRule sample on Github -
[1] README ServiceTestRule -
Add a comment...
Wait while more posts are being loaded