Created
December 13, 2013 14:14
-
-
Save anthonydahanne/7944865 to your computer and use it in GitHub Desktop.
gradle run single test method
--> supposed to work according to http://www.gradle.org/docs/release-candidate/release-notes#executing-specific-tests-from-the-command-line
--> not documented though : http://www.gradle.org/docs/1.7/userguide/java_plugin.html#sec:java_test
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
$ gradle --version | |
------------------------------------------------------------ | |
Gradle 1.7 | |
------------------------------------------------------------ | |
Build time: 2013-08-06 11:19:56 UTC | |
Build number: none | |
Revision: 9a7199efaf72c620b33f9767874f0ebced135d83 | |
Groovy: 1.8.6 | |
Ant: Apache Ant(TM) version 1.8.4 compiled on May 22 2012 | |
Ivy: 2.2.0 | |
JVM: 1.7.0_25 (Oracle Corporation 23.25-b01) | |
OS: Mac OS X 10.9 x86_64 | |
$ gradle test --tests net.dahanne.MyTest.parseDetailsTest | |
Relying on packaging to define the extension of the main artifact has been deprecated and is scheduled to be removed in Gradle 2.0 | |
The Test.testReportDir property has been deprecated and is scheduled to be removed in Gradle 2.0. Please use the Test.getReports().getHtml().getDestination() property instead. | |
FAILURE: Build failed with an exception. | |
* What went wrong: | |
Problem configuring task :project:test from command line. Unknown command-line option '--tests'. | |
* Try: | |
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. | |
BUILD FAILED | |
Total time: 7.202 secs |
The question is ages old, but nevertheless, try
$ gradle test --tests *MyTest.parseDetailsTest
Thanks SimplyJaymin!!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I'm having the same issue here, did you find any workaround?