Wayland Support in IntelliJ

Today I learned, that IntelliJ has support for Wayland Compositor since version 2024.2, so seems like im rather late to the game. Simply go to Help > Edit custom VM options and add -Dawt.toolkit.name=WLToolkit. For me it so far works nicely. And the issue of some overlay windows (like object inspector) not being resizable in Sway … are just gone. Yay 🥳

Status: 🌱 Seedling · Planted: Mar 18, 2025 · 1 min

Scripting IntelliJ

Recently I learned, that it’s possible to script IntelliJ. I picked up on it while Writing an IntelliJ Plugin for my Coverage Tracker project, aka “Undercovered”. So there is the IDE scripting console, which comes out-of-the-box. You just open the Action panel and search for IDE Scripting Console, next a tiny popup menu should show, asking for whether it should be Groovy or Kotlin (beta). Right away you can enter some code and evaluate it by pressing Control + Return....

Status: 🌿 Budding · Planted: Mar 17, 2025 · Last tended: Mar 18, 2025 · 5 min

Chromium Site Search

Pretty likely this is a well-known thing to many 🥱, and to be honest, I also kindof knew that Chromium has some search shortcuts, but I never bothered to learn how to use them. To even add to that, I’m even well aware that I quite regularly went to pages like dict.leo.org, and used the search feature there. Or I went to our Jira instance, and used the search feature there, regularly just typing a ticket number....

Status: 🌱 Seedling · Planted: Feb 3, 2025 · 3 min

JUnit Parameter Resolvers

Today (err, recently) I learned … that JUnit’s extension API allows for parameter resolvers. These kick in every time you use arguments on a test method, lifecycle method or class constructor. For me, so far, none of these methods ever took an argument. But turns out, it’s possible … and even useful. They have a primitive example here where they allow a test method to take a random number like so:...

Status: 🌿 Budding · Planted: Dec 11, 2024 · 1 min

JUnit Assumptions API

Today, I discovered a powerful feature in JUnit: the Assumptions API. This API allows you to define assumptions for your tests. If an assumption isn’t met, the test execution is aborted rather than marked as failed. This distinction is crucial in scenarios like conditional test execution in CI pipelines. When a test is skipped due to an unmet assumption, it appears as “skipped” in the test reports, not as “passed” or “failed....

Status: 🌿 Budding · Planted: Aug 24, 2024 · 1 min