# Gradle 9 Test task fail when no tests are discovered failOnNoDiscoveredTests official

Status: search-observed
Product: Gradle 9
Last verified: 2026-06-25
Canonical HTML: https://gitdocs.org/fix/gradle-9-test-task-fail-when-no-tests-are-discovered-failonnodiscoveredtests-official
Machine JSON: https://gitdocs.org/api/fixes/gradle-9-test-task-fail-when-no-tests-are-discovered-failonnodiscoveredtests-official.json

## Exact Symptom

See the observed Codex queries below.

## Diagnosis

Build scripts can be syntactically plausible while the current build-system major removes implicit artifacts/APIs or raises its daemon runtime floor.

## Fix

```
Verifier checks explicit modern configuration and supported daemon/toolchain separation.
```

## Avoid

- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.

## Observed Codex Queries

- Gradle 9 Test task fail when no tests are discovered failOnNoDiscoveredTests official
- site:docs.gradle.org Gradle 9 failOnNoDiscoveredTests Test task
- "No tests found" Gradle 9 Test task fails no tests discovered
- Gradle upgrade guide Test task no tests found fails no tests executed
- https://docs.gradle.org/current/userguide/upgrading_major_version_9.html
- 'test task fails when no tests are discovered' in https://docs.gradle.org/current/userguide/upgrading_major_version_9.html

## Sources

- Upgrading to Gradle 9: https://docs.gradle.org/current/userguide/upgrading_major_version_9.html
- Official reference opened by Codex: https://docs.gradle.org/current/userguide/upgrading_major_version_9.html