У нас вы можете посмотреть бесплатно What IntelliJ isn't telling you - the Truth about Test Speed или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
Regular viewers won’t be surprised that I’m obsessed with the details of how long our tests are actually taking to run. I won’t speak for all developers, but I at least can be a little, erm compulsive when I get the bit between my teeth. So when I suspected that IntelliJ was just plain lying to me about how fast tests are running, I had to see if my suspicions were true. Last week ( • Why are my tests so slow? JUnit vs Gradle ... ) we saw that there is a lot of time between invoking the action and the tests actually running. This week we’ll see that the reported duration of individual tests, and the suites that they sit in, appear to be wrong too. In this episode 00:00:38 The story so far 00:01:18 Crank up the AI 00:01:40 AI Assistant bug 00:04:07 Oooh test times 00:05:45 No convert to property in k2 mode? 00:07:33 It looks like we need a different JUnit extension 00:08:53 Record times against tests 00:11:31 AI Autocomplete can be really very good 00:12:00 A smoking gun 00:13:03 Building a tree of tests 00:15:15 AI Over, back on your heads 00:20:55 We have tree! 00:21:52 Compare our tree times with those from IntelliJ 00:24:15 Tidy up before we go There is a playlist of TDD Gilded Rose episodes - • Test Driven Gilded Rose in Kotlin and one for Gradle • Gradle The codebase is available on GitHub https://github.com/dmcg/gilded-rose-tdd I get lots of questions about the test progress bar. It was written by the inimitable @dmitrykandalov. To use it install his Liveplugin (https://plugins.jetbrains.com/plugin/...) and then this gist https://gist.github.com/dmcg/1f56ac39... If you are going to be at KotlinConf 2025, or even just in Copenhagen in May, then you should sign up for the workshop that Nat Pryce and I are running. It’s called Refactoring to Functional Kotlin, and will give you hands-on experience of taking legacy code and safely migrating it to a functional style. Places are limited, so buy now at https://kotlinconf.com/workhops If you like this video, you’ll probably like my book Java to Kotlin, A Refactoring Guidebook (http://java-to-kotlin.dev). It's about far more than just the syntax differences between the languages - it shows how to upgrade your thinking to a more functional style.