From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

let's say I have a `Test` task named `"testFoo"`. For Reasons, I want to register a lifecycle task (_not_ a `Test` task), named simply `"test"`, which will have a `dependsOn` relationship with the original `"testFoo"`. Is there any way to propagate command-line options to the underlying "real" task? E.g., a test filter `--tests="*.foo.*"`?

ah! I have an idea. I can perma-configure `testFoo` to always have the filter set (so users aren't required to pass the option, which is today's case). Then the `dependsOn` just works