Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
Fixing Broken Robots - Android Mutation Testing
Search
Panini
July 18, 2019
Programming
230
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Fixing Broken Robots - Android Mutation Testing
Panini
July 18, 2019
More Decks by Panini
See All by Panini
Kotlin 1.5 preview
panini
1
490
Java谷園から逃げ出した話
panini
0
410
Kotlin 1.4-rc
panini
0
250
Kotlin Multiplatform
panini
2
720
build.gradle.kts
panini
2
2.5k
Kotlin Multi-platform(?)
panini
1
790
Convert Java file to Kotlin file ⌥⇧⌘K
panini
0
1.2k
Introducing Android P
panini
2
890
Display Cutout
panini
1
710
Other Decks in Programming
See All in Programming
Agents on Rails - Rails at Scale 2026
irinanazarova
0
530
半永久的に提供し続けられるプライベートクラウドを目指して ― 利用者の認知負荷を抑えるAPI抽象化とハードウェア世代交代の基盤設計
tomokon
0
470
外から家のPCの電源入れたい!をPHPで解決する
kawashimo0
1
130
Vue Fes Japan 2026 タイムテーブル徹底解説
448jp
1
650
AI主導のプログラミング学習アプリを作ってみた
econanringo
0
150
wkhtmltopdfの次どうするか問題2026
willnet
2
1.9k
sbt 2.0: takeoff
eed3si9n
0
120
APNsからLive Activityを開始する話
yumnumm
0
160
Jetpack Compose Mechanisms
skydoves
2
690
なぜCTOを降りてFDEを選んだのか?〜なぜプロダクト企業がFDEで顧客の現場に踏み込むのか〜
gonta
1
190
Findy - エンジニア向け会社紹介/Findy Company Deck
findyinc
6
400k
SalesForceを内製化!? ~ HR事業を支える顧客管理基盤のインフラを大公開 ~
oku053
0
160
Featured
See All Featured
DBのスキルで生き残る技術 - AI時代におけるテーブル設計の勘所
soudai
PRO
68
58k
Tell your own story through comics
letsgokoyo
1
1.1k
Visual Storytelling: How to be a Superhuman Communicator
reverentgeek
2
710
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
56
3.5k
Unlocking the hidden potential of vector embeddings in international SEO
frankvandijk
0
980
What's in a price? How to price your products and services
michaelherold
247
13k
Practical Tips for Bootstrapping Information Extraction Pipelines
honnibal
25
2.1k
[Rails World 2026] Durable orchestration on Rails: from continuation to workflow
palkan
1
700
A Guide to Academic Writing Using Generative AI - A Workshop
ks91
PRO
1
510
4 Signs Your Business is Dying
shpigford
187
23k
Speed Design
sergeychernyshev
33
2.2k
Stewardship and Sustainability of Urban and Community Forests
pwiseman
0
540
Transcript
Fixing broken robots - Android Mutation Testing DroidConSG 2019 1/45
About me Matthew Vern Twitter Github Mercari, Inc Software Engineer
(Android) @panini_ja panpanini 2/45
Client Engineer Solving problems for our customers Shipping features Improve
existing functionality My job 3/45
A non-shipped feature doesn't provide benefit Ship features as quick
as possible My job 4/45
A shipped, broken feature doesn't provide benefit Ship quality features
as quick as possible My job 5/45
Maintaining quality 6/45
QA Maintaining quality 6/45
QA Code Review Maintaining quality 6/45
QA Code Review Tests Maintaining quality 6/45
How do we know our tests are providing quality Maintaining
quality 7/45
How do we know our tests are providing quality Use
coverage to make sure that our tests are calling production code Maintaining quality 7/45
How do we know our tests are providing quality Use
coverage to make sure that our tests are calling production code changes introduced will not break existing code Maintaining quality 7/45
How do we know our tests are providing quality Use
coverage to make sure that our tests are calling production code changes introduced will not break existing code new code does what it says on the tin Maintaining quality 7/45
Who watches the watchmen? 8/45
How do we know that our tests are quality? Maintaining
quality 9/45
What are tests 10/45
asserting that our assumptions about a piece of code are
correct binary assertions of code correctness What are tests 11/45
Lets fail some tests 12/45
Unit tests assert code behaviour change code behaviour tests fail
???? profit Lets fail some tests 13/45
Mutation testing 14/45
proposed by Richard Lipton in 1971 computationally expensive, not a
viable testing solution until recently Mutation testing 15/45
1. Create a mutant 2. Run test suite 3. Confirm
if mutant was detected or not 4. Repeat Mutation testing steps 16/45
A mutant is a biological entity which has undergone a
change in its genetic structure. What is a mutant? 17/45
A mutant is a code block which has undergone a
change in its structure. What is a mutant? 18/45
class SessionController( private val sessions: MutableList<Session> ) : EpoxyController() {
fun setSessions(sessions: List<Session>) {} override fun buildModels() {} fun generateModels(sessions: List<Session>): List<SessionModel> {} } Creating mutations 19/45
Creating mutations fun setSessions(sessions: List<Session>) { this.sessions.clear() this.sessions.addAll(sessions) requestModelBuild() }
20/45
Creating mutations override fun buildModels() { generateModels(sessions) .forEach { it.addTo(this)
} } 21/45
Creating mutations fun generateModels(sessions: List<Session>): List<SessionModel> { return sessions .map
{ session SessionModel_() .title(session.title) .imageUrl( if (session.speaker.profileImage "") { session.speaker.profileImage } else { null } ) } } 22/45
Creating mutations 23/45
Competent Programmer Hypothesis Creating mutations 23/45
Competent Programmer Hypothesis Coupling Effect Creating mutations 23/45
Replaces relational operators with boundary counterpart Original Original Mutated Mutated
< <= <= < > >= >= > Conditionals boundary 24/45
Conditionals boundary original if (currentTime < startTime) { do something
} mutated if (currentTime startTime) { do something } 25/45
Negates conditional checks Original Original Mutated Mutated == != !=
== <= > > <= Negate Conditionals 26/45
Negate Conditionals original fun buildModels() { SessionModel_() .title(session.title) .imageUrl( if
(session.speaker.profileImage "") { session.speaker.profileImage } else { null } ) } mutated fun buildModels() { SessionModel_() .title(session.title) .imageUrl( if (session.speaker.profileImage "") { session.speaker.profileImage } else { null } ) } 27/45
removes void method calls Remove void calls 28/45
Remove void calls original fun setSessions(sessions: List<Session>) { this.sessions.clear() this.sessions.addAll(sessions)
requestModelBuild() } mutated fun setSessions(sessions: List<Session>) { this.sessions.clear() this.sessions.addAll(sessions) } 29/45
So what? 30/45
Code coverage, but better Why mutation testing 31/45
1. Introduce a fault into production code 2. Use code
coverage to determine which tests to run 3. Run tests 4. Confirm if fault was detected or not 5. Repeat Mutation testing The better way 32/45
That's a lot of work you expect us to do
there bud 33/45
Pitest 34/45
mutation testing system mutants stored in memory outputs pretty reports
Gradle plugin Pitest pitest.org 35/45
apply plugin: pitest generates pitest<Variant> tasks Gradle plugin szpak/gradle-pitest-plugin 36/45
37/45
written by Karol Wrótniak, forked from szpak/gradle-pitest-plugin works with Android
projects has some Android specific helpers (eg: generating mockable Android jar) Android Gradle plugin koral--/gradle-pitest-plugin 38/45
plugins { id("pl.droidsonroids.pitest") } pitest { excludeMockableAndroidJar = false targetClasses
= setOf("jp.co.panpanini.mypackage.*") outputFormats = setOf("XML", "HTML") } Android Gradle plugin 39/45
id("pl.droidsonroids.pitest") plugins { } pitest { excludeMockableAndroidJar = false targetClasses
= setOf("jp.co.panpanini.mypackage.*") outputFormats = setOf("XML", "HTML") } Android Gradle plugin 39/45
pitest { excludeMockableAndroidJar = false targetClasses = setOf("jp.co.panpanini.mypackage.*") outputFormats =
setOf("XML", "HTML") } plugins { id("pl.droidsonroids.pitest") } Android Gradle plugin 39/45
excludeMockableAndroidJar = false plugins { id("pl.droidsonroids.pitest") } pitest { targetClasses
= setOf("jp.co.panpanini.mypackage.*") outputFormats = setOf("XML", "HTML") } Android Gradle plugin 39/45
targetClasses = setOf("jp.co.panpanini.mypackage.*") plugins { id("pl.droidsonroids.pitest") } pitest { excludeMockableAndroidJar
= false outputFormats = setOf("XML", "HTML") } Android Gradle plugin 39/45
outputFormats = setOf("XML", "HTML") plugins { id("pl.droidsonroids.pitest") } pitest {
excludeMockableAndroidJar = false targetClasses = setOf("jp.co.panpanini.mypackage.*") } Android Gradle plugin 39/45
Demo 40/45
Pitest tips & tricks 41/45
MutationInterceptor Removes mutants for Kotlin generated code Pitest kotlin pitest/pitest-kotlin
42/45
Run PITest on Unit tests only 43/45
Run PITest on CI 44/45
Mutation Testing panpanini/mutation_testing Github: panpanini Twitter: panini_ja 45/45