DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • How to Test Gradle Plugins
  • Agentic Testing: Moving Quality From Checkpoint to Control Layer
  • Why Your QA Engineer Should Be the Most Stubborn Person on the Team
  • The Only AI Test That Still Humbles Every Machine on Earth

Trending

  • Product-Led Software Delivery: Intelligent Platforms for DevOps at Scale
  • Zero-Downtime Deployments for Java Apps on Kubernetes
  • Docker Hardened Images Are Free Now — Here's What You Still Need to Build
  • Why Google Data Migration Gets Stuck at 99%: Causes and Proven Fixes
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Testing, Tools, and Frameworks
  4. Gradle Goodness: Running All Tests From One Package

Gradle Goodness: Running All Tests From One Package

Hubert Klein Ikkink shows how to run all tests in Gradle from one package, complete with a set of instructions for different scenarios.

By 
Hubert Klein Ikkink user avatar
Hubert Klein Ikkink
·
Jun. 16, 16 · Tutorial
Likes (1)
Comment
Save
Tweet
Share
5.3K Views

Join the DZone community and get the full member experience.

Join For Free

If we have a Gradle task of type Test we can use a filter on the command line when we invoke the task. We define a filter using the --tests option. If, for example, we want to run all tests from a single package, we must define the package name as value for the --tests option. It is good to define the filter between quotes, so it is interpreted as is, without any shell interference.

If we configure the test task to output the test class name, we can see that which tests are executed. In the following snippet, we reconfigure the test task:

...
test {
    beforeTest { descriptor ->
       logger.lifecycle("Running test: $descriptor.className")
    }
}
...

Suppose we have a project and we execute all tests:

$ gradle test
...
:test
Running test: mrhaki.gradle.model.CourseSpec
Running test: mrhaki.gradle.model.TeacherSpec
Running test: mrhaki.gradle.service.CourseServiceSpec
...
$

To only run the tests in the mrhaki.gradle.model package, we use the following command:

$ gradle test --tests "mrhaki.gradle.model.*"
...
:test
Running test: mrhaki.gradle.model.CourseSpec
Running test: mrhaki.gradle.model.TeacherSpec
...
$

We can even filter on a single test to be executed:

$ gradle test --tests "mrhaki.gradle.model.CourseSpec"
...
:test
Running test: mrhaki.gradle.model.CourseSpec
...
$

If we only want to run a single method of a test, we can specify the method name as a filter:

$ gradle test --tests "test --tests "mrhaki.gradle.model.CourseSpec.create new Course as immutable""
...
:test
Running test: mrhaki.gradle.model.CourseSpec
...
$


Written with Gradle 2.13.

Testing Gradle

Published at DZone with permission of Hubert Klein Ikkink. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • How to Test Gradle Plugins
  • Agentic Testing: Moving Quality From Checkpoint to Control Layer
  • Why Your QA Engineer Should Be the Most Stubborn Person on the Team
  • The Only AI Test That Still Humbles Every Machine on Earth

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook