li'lfluf
10/23/2026, 7:10 PM// in compiler-plugin/build.gradle.kts
tasks.named<KotlinCompile>("compileTestKotlin") {
pluginClasspath.from(tasks.named("jar"))
pluginClasspath.from(configurations.runtimeClasspath)
compilerOptions {
freeCompilerArgs.addAll("-P", "plugin:myPlugin:myRequiredOption=true")
}
}Youssef Shoaib [MOD]
10/23/2026, 7:34 PMinternal-test-framework. The setup is kinda hefty, but you can copy it from the template!Youssef Shoaib [MOD]
10/23/2026, 7:42 PMli'lfluf
10/23/2026, 9:36 PMinternal-test-framework, I definitely looked at it but I don't quite understand why I would want to use it. Isn't behavior the one thing I'd want to test? (As long as I don't do any checking)li'lfluf
10/23/2026, 9:37 PMYoussef Shoaib [MOD]
10/23/2026, 9:52 PMinternal-test-framework lets you test behavior and diagnostics (which isn't as applicable to IR plugins).
It also lets you dump the IR, which means you can check the exact code that your plugin is producing and find out when it changes.
It also lets you do JS, Wasm, and Native tests, with IR dumps and such