Screenshot tests for Compose Multiplatform on a plain JVM. One annotation on a composable gives a golden-file test and an entry in a component browser — rendered through Compose Desktop/Skiko, with no emulator, no AVD and no layoutlib.

@ViddikScreenshot(name = "Primary", group = "Buttons")
@Composable
fun PrimaryButton() {
    MaterialTheme(typography = viddikTypography()) {
        Button(onClick = {}) { Text("Continue") }
    }
}

./gradlew :yourModule:viddikRecord     # write the goldens
./gradlew :yourModule:viddikVerify     # compare against them
./gradlew :yourModule:viddikShowroom   # browse the components in a window

// settings.gradle.kts — mavenCentral() in both blocks, google() beside the second
pluginManagement {
    repositories {
        gradlePluginPortal()
        mavenCentral()
    }
}
dependencyResolutionManagement {
    repositories {
        google()
        mavenCentral()
    }
}

// build.gradle.kts of the module that holds the fixtures
plugins {
    id("com.google.devtools.ksp") version "<KSP_VERSION>" // must match your Kotlin compiler version
    id("io.github.youndie.viddik") version "0.7.0"
}

That is the whole setup: the plugin adds the dependencies, the KSP processor and the tasks, with the names your module's shape needs. viddik 0.7 works with Compose Multiplatform 1.12, Kotlin 2.4 and JDK 21. Options, compatibility and the setup without the plugin: docs/configuration.md.

Measured in screenshot-bench: the same generated composables at 360×640, each tool set up as its own documentation says, one build machine (20 cores, Linux), medians. viddik 0.6.1.45 for the speed rows, which is the code of 0.7.0 there.

On large suites the two Skiko tools and Paparazzi are within a few seconds of each other; the edit-and-record cycle is where they differ most. viddik's goldens travel between operating systems on Skiko, where Roborazzi's do not — the Android renderers get that for free. The price is a tolerance: at the default 0.05% a 12-pixel change on a full screen passes; with tolerancePercent = 0.0 it is caught and the cross-OS goldens still pass (how a comparison decides).

• Fixtures — @ViddikScreenshot, or @Preview metadata read off the same function, multipreviews, @PreviewParameter, dark variants, one theme for all of them through @PreviewWrapper. docs/fixtures.md
• Recording and verifying — a record writes only the goldens a verification would reject; --component selects one fixture; one scene, two forks and a KSP that ignores body edits by default. docs/running.md
• Goldens across operating systems — record on macOS, verify on Linux: viddik rasterizes glyphs itself, and a bundled font (viddikTypography()) does the rest. docs/portability.md
• The showroom — a component browser over the same registry, in a desktop window or in an Android or iOS app. docs/showroom.md
• Design parity — how far each fixture is from the PNG exported from its design. docs/design-parity.md

API reference: youndie.github.io/viddik. Release notes: GitHub releases.

MIT, see LICENSE.