Skip to content

Track Clojure test selectors without parent project lookups - #67

Merged
rpalcolea merged 2 commits into
mainfrom
isolated-projects/clojure-test-selector
Nov 5, 2026
Merged

rpalcolea merged 2 commits into
mainfrom
isolated-projects/clojure-test-selector

Conversation

@rpalcolea

@rpalcolea rpalcolea commented Nov 5, 2026 •

Copy link
Copy Markdown
Member

Changing clojuresque.test.vars now invalidates clojureTest inputs so the newly selected tests execute. Resolve the selector once during lazy task configuration, preferring the owning project's extra over tracked Gradle properties. Preserve local-extra precedence over -P, customization timing, explicit tests overrides, comma splitting, and absent/empty selection behavior. The existing ListProperty<String> API is retained and tracked as an optional input.

Parent-only extra properties must move to gradle.properties, -P, or local extra/tests configuration in each participating project. The README documents this adoption requirement. This change covers selector ownership and input tracking; enabled uber-JAR configuration-cache issues and documentation-input modeling remain separate work. Whole-plugin Isolated Projects compatibility is not claimed.

CI installs Java 8 for the existing toolchain tests and reports full test exceptions. Gradle 8.0 coverage runs on the compatible Java 17 lane; the current wrapper runs across Java 17, 21, and 25. The precedence tests use named configuration options and Spock's combination support.

Validation: test validatePlugins with Java 17 passed all 90 tests, including 58 selector cases; all 46 selector cases also passed locally on Java 25. GitHub Actions builds pass on Java 17, 21, and 25. The selector tests cover single, sibling, and nested projects under ordinary configuration cache and strict isolation, checking actual selected-test output, selector invalidation, subsequent cache reuse, source edits, and selected failures.

@rpalcolea
rpalcolea merged commit f923c3b into main Nov 5, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant