Sehr gut dargestellte Zusammenhänge. Jetzt bitte noch konstruktive Ansätze für eine strukturelle Korrektur. Wie wäre es, Medienkanäle systematisch, wissenschaftlich, stichprobenartig auf Faktentreue zu prüfen und Desinformation (Presse&Social) zu drosseln?
Posts by Oliver O.
Thank you so much for sticking with human curation. We still detect the intrinsic value that makes it stand out. Hope we'll all keep those firewalls against high-volume mediocrity in place.
Yep. It's a very useful step in the process. And yes, even with 100% coverage (which rarely makes sense anyway) you'll find other classes of bugs with different levels of component interaction tests up to full integration testing.
You did as well? So amazing to see how much happens on the edge! 🤩
An IntelliJ IDEA test results tree view, showing a multi-level hierarchy of test suites and tests generated with TestBalloon on three targets (JVM, Native, Android).
Made TestBalloon 🎈 (local dev version) play nicely ❤️ with Amper (v0.11.0-dev-3793) out of the box:
Photograph of Hamburg city center seen across the outer Alster lake.
Same here. But first, have lots of fun!
Upcoming Kotlin releases (2.3.21-RC and 2.4.0-Beta2) fix KT-82395, paving the way for TestBalloon to support incremental compilation for JS and Wasm targets. Yay!
Screenshot of two error messages: - CodeQL exited with errors - Kotlin version too new
April Fools' Day, GitHub CodeQL version. Or maybe just TestBalloon being ahead of the curve again.
Finally status codes that make sense!
In our age of non-determinism, I wanted to suggest a status code like 42 for "maybe successful". Fortunately, you had already considered that: 500 for "something could be wrong". 🤣
Apparently Kotlin/Wasm/WASI is now too fast for my 🧠 wetware's HTML decoding unit, but fortunately I can always hit ⏯️.
In a world of inverted truths, #502 implies that @kotlinweekly.bsky.social is actually an excellent gateway to carefully curated content every Sunday. Happy to see my article on TestBalloon flexibility featured in this episode.
Challenging the flexibility of TestBalloon, the DSL-based, Kotlin-first test framework. How much freedom does its API really support? How far can we go if we want to change its look and feel?
Join me on my dogfooding journey!
infix-de.github.io/testBalloon/...
To me, that article appears weak on the merits, resulting in what’s basically a big and complicated ad hominem argument.
If one wanted to position oneself in favor of a sustainable paradigm shift, I’d find this piece way more convincing: honnibal.dev/blog/ai-bubble
Are you confused by Gradle terminology? What's a module, a configuration, a build, a project? Unless you're deep into Gradle, they probably aren't what you think.
I wrote an article to organize all of that → ivan.canet.dev/blog/2026/03...
Wir müssen reden …
über Fun Facts
Hand aufs Hirn: Ist euch das Lachen (schon) vergangen? Mit Blick auf die Nachrichtenlage und in die Welt. Iran, Israel, USA, Russland, Ukraine, Pakistan, Afghanistan - 🧵1/8
(c) Clemens Porikys
I love it! ❤️
That's your bike? Did Louis convert you? 😃
Android testing at scale is either fast or easy, never both, right?
Integrating a modern DSL-based Kotlin test framework with class-based Roboelectric was considered impossible by genAI and others. Yet here it is: Roboelectric meets 🎈 TestBalloon
infix-de.github.io/testBalloon/...
Guidance I have been waiting for. 🎉👏❤️
Arguing about unit tests vs. integration tests sucks. It's dogma and I feel like a heretic.
This post discusses a different way to think about a test’s scope. I love it.
Good points in the article. Let's not get fooled by false dichotomies.
Note to self and other folks working on test infra: Make effective testing easy, regardless of scope. Simplify all kinds of high-value tests, so these will actually get written.
Signing up on LookupTracker. Adding ICFileMappingTracker.
Did you check this one?
youtrack.jetbrains.com/issue/IJPL-2...
Also, the introductory docs („why might I want to use this?“) are superb! 👏
I haven’t checked, but the more platforms to cover, the more it might call for a rewrite in Kotlin. 😉
If it’s JMH only, I’d agree. But you mentioned web…
Why not integrate with TestBalloon where suspend functions are readily available in tests everywhere?