Package-level declarations

Types

Link copied to clipboard
abstract class ViddikDeclarationsTransform : TransformAction<TransformParameters.None>

The same snapshot for a project dependency on the test compile classpath — a sibling module's jar or class directory — for the layout where the fixtures sit in a module of their own and every component they draw comes from elsewhere (issue #53).

Link copied to clipboard
interface ViddikExtension

Configuration for the io.github.youndie.viddik plugin, available as viddik { } in a consumer's build script.

Link copied to clipboard
@DisableCachingByDefault(because = "The output is a fixed string; writing it is cheaper than looking it up in a build cache.")
abstract class ViddikGenerateTestsTask : DefaultTask

Writes the JUnit 5 class that drives the goldens, for the viddik { showroomTargets = true } shape where the fixtures — and therefore the registry — live in commonMain.

Link copied to clipboard
@DisableCachingByDefault(because = "Reading the main classes is cheaper than a cache round trip, and the output is only useful in place.")
abstract class ViddikKspDeclarationsTask : DefaultTask

Copies the main compilation's output with everything but the declarations taken out, for the test source set's KSP run to read instead of the real classes.

Link copied to clipboard
class ViddikPlugin : Plugin<Project>

Wires viddik screenshot testing into a module.

Link copied to clipboard
@DisableCachingByDefault(because = "Recording writes goldens into the source tree as an undeclared output.")
abstract class ViddikRecordTask : ViddikScreenshotTask

The recording task, which has one more switch than a verification does.

Link copied to clipboard
@DisableCachingByDefault(because = "The same type serves recording, which writes goldens into the source tree as an undeclared output — a cache hit would skip producing the very files the run exists to produce.")
abstract class ViddikScreenshotTask : Test

A Test task that can be pointed at a single screenshot.