https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hiring-french
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
h

Husam

05/02/2021, 11:00 PM
Anybody else face issues with #jacoco branch coverage when upgrading kotlin? Blocked from upgrading from 1.3.72 to 1.4+ because a lot of new 'ghost' branches pop up as uncovered. Some might be addressed in the next jacoco release based on the release notes, but it's been one of the few impactful pain points I've had with kotlin. Unfortunately been blocked from upgrading for months on this, curious if there's a plan to address this better going fwd?
b

Byron Katz

05/03/2021, 12:43 AM
Are you saying you're prevented from using the latest kotlin because of the code coverage report from jacoco?
h

Husam

05/03/2021, 12:59 AM
@Byron Katz Because of build failures from test coverage reqs suddenly not being met across the codebase, to be specific
b

Byron Katz

05/03/2021, 1:02 AM
Then I'd suggest to temporarily relax the gates to let that change through and have them back up again after
☝️ 1
h

Husam

05/03/2021, 1:10 AM
Tried but unfortunately the compromise would be quite drastic, e.g. from 85% to 50% in many cases, and across lots of packages, for an unknown amount of time. Branch coverage has been very helpful in ensuring diff code paths get covered that developers forget or don't notice. This is kind of an ongoing battle between jacoco and kotlin bytecode, where jacoco is constantly needing to catch up with kotlin compilation changes
b

Byron Katz

05/03/2021, 1:23 AM
Hmm. For what it's worth I use jacoco a lot in my project looking for places I missed and while it's a bit annoyingly pedantic about not having checked every branch in some functional mishmash, I generally am able to work through that and derive good value.
h

Husam

05/03/2021, 1:36 AM
Yeah Jacoco v0.8.6 works quite well with kotlin 1.3.x. They resolved lots of issues we faced when first adopting kotlin in 2019, and it's been pretty smooth since that release (easy to handle any potential discrepancies). And valuable indeed as you said, well worth it. However upgrading kotlin has proved challenging for us. Hoping the next Jacoco release is just as helpful in this regard, and that it comes soon :) But discrepancies are more so in the hands of the kotlin team with compilation modifications, hence asked here. Would be good to have the jacoco lib more in sync with kotlin bytecode changes
b

Byron Katz

05/03/2021, 1:50 AM
Or maybe it's time for Kococo 😉
☝️ 1
😂 1
n

nfrankel

05/03/2021, 6:35 AM
probably not what you want to hear but regular code coverage is meaningless 😬
c

christophsturm

05/03/2021, 11:07 AM
http://pitest.org works pretty well with kotin, and gives you mutation coverage which is what really matters.
💯 1
☝️ 1
1
n

nfrankel

05/03/2021, 1:50 PM
exactly @christophsturm i’m a big fan of PIT 🙂
b

Byron Katz

05/03/2021, 2:32 PM
I like PIT, it's good. But Jacoco is also very good for certain purposes. I can certainly understand why people would think plain code coverage isn't useful - the way it's instituted most of the time, the fact that developers don't typically apply good testing practices. It's all endemic.
h

Husam

05/05/2021, 3:59 AM
good news is jacoco 0.8.7 just came out, and the build now passes for the kotlin upgrade to 1.4.32 🙂
Better late than never!
@nfrankel I wouldn't say useless, but they have to be written well (perhaps that's what you were alluding to by 'regular'?). This line from pitest is totally true tho, in terms of what code coverage "guarantees": "It is therefore only able to identify code that is definitely not tested." And that's also useful to know - how much code is def not tested; at total risk
Good to know ppl have had good experiences with pitest and kotlin, will def look into setting it up! Looking forward to it
c

christophsturm

05/05/2021, 4:03 PM
for pitest to work well you need a pretty well designed test suite, the tests should be fast and be able to run in parallel. But i guess thats how a test suite should be anyway 🙂
👍 1
n

nfrankel

05/05/2021, 4:05 PM
But i guess thats how a test suite should be anyway
But i guess thats how a unit test suite should be anyway 😉
b

Byron Katz

05/05/2021, 4:07 PM
I've generally found PIT craps out if I throw it at a ton of tests - have you figured out a configuration where that doesn't happen?
c

christophsturm

05/05/2021, 4:08 PM
But i guess thats how a unit test suite should be anyway
right. and you should only use the unit test suite with pit, because integration test coverage is cheating 🙂
actually the run in parallel part is true for any test suite 🙂
@Byron Katz for me the number of tests did not really matter as long as they are well written, and don’t depend on global state
n

nfrankel

05/05/2021, 4:14 PM
actually the run in parallel part is true for any test suite 🙂
“it depends” if i want to test a full-fledged scenario like from browsing the catalog to final checkout i’ll probably have small tests that depend on each other
c

christophsturm

05/05/2021, 4:16 PM
hmm if it needs an order i treat it as one test. and i can not run the later parts separate anyway. but i can still run these long running tests in parall with multiple browsers, web servers etc.
n

nfrankel

05/05/2021, 4:21 PM
the problem when you treat is as one test is that if it breaks, you’ve no clue where it did that’s one of the issues of integration tests if you define steps and chain them, it becomes much clearer
c

christophsturm

05/05/2021, 4:23 PM
well i know what assertion failed
you can still define steps by seperating the test into functions. but from the test runners perspective i think it should be just one test
n

nfrankel

05/05/2021, 4:43 PM
but the function split doesn’t tell you at first glance where it failed
c

christophsturm

05/05/2021, 6:56 PM
what test runner would you use for that? I have not found one that i liked yet.
n

nfrankel

05/06/2021, 6:58 AM
testng junit 4 frowned upon test ordering and i don’t have experience enough in junit 5 to pinpoint you to a possible existing feature