Android Development Culture. The Document. #qualitymatters
Runner at the Finish Line Bronze Statue. 2015-12-02 Android Development is in trouble (for about 7 years). Most of the projects do not have tests (unit, integration, functional); compilation and lint warnings ignored; code is kind of smelling spaghetti (hopefully, reactive-spaghetti) and so on. Bad news: Google participated in such development culture right from the beginning of Android. #perfmatt
Espresso 2.1: ActivityTestRule
When I wrote my android-test-demo app, I wanted to use Jake Wharton's ActivityRule, but couldn't because I wanted to customize the launch intent for each test method. Today I got my solution from Google: Test rules in Espresso 2.1. ActivityTestRule can be configured to take a different launch intent per test method like this: @Rule public ActivityTestRule activityRule = new ActivityTestRule<>( Mai
Dagger 2 + Espresso 2 + Mockito
I've been doing Android instrumentation testing with Dagger, Espresso and Mockito, and I love it. To commemorate the launch of Dagger 2 out of SNAPSHOT, I am sharing a demo repo with Dagger 2, Espresso 2 and Mockito: https://github.com/chiuki/android-test-demo Dagger Components Dependency injection allows our app and test obtain different modules. This is very useful for creating repeatable test c
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Unit Testing Delays, Errors & Retries with Kotlin Flows
Effective Espresso #roppongi_aar
about:blank
