Do you see any opportunities to speed up running tests via t kotlinlang #kotest

Channels

fluid-libraries

jhipster-kotlin

effectivekotlin

effective-kotlin

android-architecture

algolialibraries

stayhungrystayfoolish

pattern-matching

kotlin-data-storage

skia-wasm-interop-temp

squarelibraries

beepiz-libraries

cscenter-course-2016

kotlin-foundation

compose-android

lambdaworld_cadiz

kotlin-pakistan

java-to-kotlin-refactoring

event21-community-content

fb-internal-demo

kotlinprogrammers

kotlinx-datetime

framework-elide

github-workflows-kt

library-development

arrow-contributors

spring-security

pocketgitclient

domain-driven-design

swiss-user-group

refactoring-to-kotlin

ohio-kotlin-users

introduce-yourself

kotlin-by-example

kotlin-multiplatform-contest

graviton-browser

tricity-kotlin-user-group

kotlin-in-action

android-databinding

kotlintest-devs

cincinnati-user-group

codemash-precompiler

kotlingforbeginners

prozis-android-backup

realworldkotlin

connect-audit-events

russian-kotlinasfirst

androidgithubprojects

intellij-tricks

machinelearningbawas

swagger-gradle-codegen

100daysofkotlin

competitive-programming

compose-ui-showcase

androidx-xprocessing

navigation-architecture-component

strife-discord-lib

embedded-kotlin

image-processing

myndocs-oauth2-server

leedskotlinusergroup

kotest-contributors

practical-functional-programming

kotlinultimatechallenge

k2-early-adopters

kotlinforbeginners

compose-desktop

competitivecoding

100daysofkotlin-2021

refreshversions

language-evolution

jvm-ir-backend-feedback

python-contributors

codingconventions

sofl-user-group

getting-started

language-proposals

intellij-plugins

Title

# kotest

r

Rob Elliot

11/29/2021, 10:25 AM

Do you see any opportunities to speed up running tests via the plugin? I just profiled running a single test in a spec via the green arrow, and it’s taking 5.5 seconds before actually starting the test, mostly in classgraph scanning, which seems unnecessary as the class and test name are being sent to it as

--spec

and

--testpath

args to

io.kotest.engine.launcher.MainKt

in the first place.

This is with 4.6.3, so may be completely irrelevant as it looked like you did quite a rewrite for 5.0.0.

I see what causes it -

io.kotest.engine.config.detectConfig

does a classgraph scan unless you explicitly disable it with two system properties.

🆒 1

w

wasyl

11/29/2021, 11:26 AM

I had a wip to discover configs via service loaders

I had to shelve it because stuff, but I hope to pick it up soon now that 5.0 is released

That'd only work on JVM, but I think class graph also works on JVM only so