Stop rerunning your tests

Gradle's build cache and incremental build features can skip test runs when inputs haven't changed, saving significant time. Using `outputs.upToDateWhen { false }` to force test reruns is an anti-pattern that wastes team productivity. For genuinely non-deterministic tests (randomized, system integration, or flaky), the right approach is to model the non-determinism as explicit task inputs—such as a random seed or a date—rather than disabling caching entirely. Separate Test tasks should be created for different test types, each configured with appropriate inputs to control when reruns are necessary.