// limitations under the License.

:metadata-file-spec: https://github.com/gradle/gradle/blob/master/platforms/documentation/docs/src/docs/design/gradle-module-metadata-1.0-specification.md

[[java_testing]]
= Testing in Java & JVM projects

 * }).run();
 * </pre>
 * <p>
 * All methods on this interface (including the class and method selection) support patterns as arguments. The patterns follow the rules of
 * <a href="https://docs.gradle.org/current/userguide/java_testing.html#test_filtering">test filtering</a>.
 * <p>
 * The test execution will fail if any of the selected classes, methods, or patters have no matching tests.
 *
 * @since 7.6
 */
@Incubating

Testing C++ projects in Gradle is fairly limited when compared to <<java_testing.adoc#java_testing,Testing in Java & JVM projects>>. In this chapter, we explain the ways to control how tests are run (<<#sec:cpp_test_execution,Test execution>>).

But first, we look at the basics of native testing in Gradle.

link:{userManualPath}/application_plugin.html#sec:application_modular[Java Module support in the Application Plugin] and

link:{userManualPath}/application_plugin.html#sec:application_modular[Java Module support in the Application Plugin] and

BUILD SUCCESSFUL
24 actionable tasks: 24 executed
----

The aggregated HTML report can now be found under `application/build/reports/tests/unit-tests/aggregated-results`.

[listing.terminal.sample-command]
----
$ ./gradlew check

BUILD SUCCESSFUL
14 actionable tasks: 14 executed
----

link:{userManualPath}/application_plugin.html#sec:application_modular[Java Module support in the Application Plugin] and

BUILD SUCCESSFUL
25 actionable tasks: 25 executed
----

XML and HTML reports can now be found under `application/build/reports/jacoco/testCodeCoverageReport`.

[listing.terminal.sample-command]
----
$ ./gradlew check

BUILD SUCCESSFUL
14 actionable tasks: 14 executed
----