Assume we have a JUnit5 dynamic test like this:
public class ProbaTest {
#TestFactory
public Iterable<DynamicNode> tests() {
return Collections.singleton(
DynamicTest.dynamicTest("aaa", () -> {
throw new AssertionError("FAIL, as planned");
})
);
}
}
When being ran by Surefire Maven plugin, it fails in the following way:
[INFO] --- maven-surefire-plugin:2.22.2:test (default-test) # proba-retrolambda ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running com.proba.ProbaTest
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.025 s <<< FAILURE! - in com.proba.ProbaTest
[ERROR] tests[1] Time elapsed: 0.007 s <<< FAILURE!
java.lang.AssertionError: FAIL, as planned
at com.proba.ProbaTest.lambda$tests$0(ProbaTest.java:14)
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] ProbaTest.lambda$tests$0:14 FAIL, as planned
[INFO]
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0
Notable thing about the output is the dynamic name, given to the test by JUnit5 - "tests[1]". It doesn't use the "aaa" display name, given by the test factory, and as far as I saw, there are reasons for that.
I wonder, however - is there a way of explicitly overriding the naming behavior? Is there any way of how can I provide explicit names for a dynamic JUnit test cases by my own?
One thing I've noticed is that you're using Maven Surefire Plugin version 2.22.2, which is a bit outdated.
As far as I know there is no way of getting the #DisplayName output only by configuration, but since version 3.0.0-M4 there's a way of developing extensions to Maven Surefire, so you can make it deal with the #DisplayName the way you want to for reports and console outputs.
Knowing that, the solution to override the test naming is to develop your own extension or to use an existing one.
I've already followed the above path and developed an extension, so feel free to use it, either as reference to develop a new one or as a possible solution.
Just tried running dynamic tests samples with it:
public class TestTest {
#TestFactory
public Iterable<DynamicNode> tests() {
return Collections.singleton(
DynamicTest.dynamicTest("aaa", () -> {
throw new AssertionError("FAIL, as planned");
})
);
}
Collection<DynamicTest> tests = Arrays.asList(
DynamicTest.dynamicTest("Add test",
() -> assertEquals(2, Math.addExact(1, 1))),
DynamicTest.dynamicTest("Multiply Test",
() -> assertEquals(4, Math.multiplyExact(2, 2))));
#TestFactory
Collection<DynamicTest> dynamicTestsWithCollection() {
return tests;
}
#TestFactory
#DisplayName("Calculating")
Collection<DynamicTest> dynamicTestsWithCollectionWithDisplayName() {
return tests;
}
}
And got the following output:
[INFO] --- maven-surefire-plugin:3.0.0-M7:test (default-test) # maven-surefire-junit5-tree-reporter ---
[INFO] Using auto detected provider org.apache.maven.surefire.junitplatform.JUnitPlatformProvider
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] ├─ TestTest - 0.046s
[INFO] │ ├─ ✔ Calculating Add test - 0.008s
[INFO] │ ├─ ✔ Calculating Multiply Test - 0.001s
[INFO] │ ├─ ✘ tests() aaa - 0s
[INFO] │ ├─ ✔ dynamicTestsWithCollection() Add test - 0.001s
[INFO] │ └─ ✔ dynamicTestsWithCollection() Multiply Test - 0.001s
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] TestTest.lambda$tests$0:15 FAIL, as planned
[INFO]
[ERROR] Tests run: 5, Failures: 1, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.909 s
[INFO] Finished at: 2022-07-24T14:56:02+02:00
[INFO] ------------------------------------------------------------------------
You can check that the #DisplayName is printed as desired. To try it by yourself, just add this to your pom file:
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M7</version>
<dependencies>
<dependency>
<groupId>me.fabriciorby</groupId>
<artifactId>maven-surefire-junit5-tree-reporter</artifactId>
<version>1.1.0</version>
</dependency>
</dependencies>
<configuration>
<reportFormat>plain</reportFormat>
<consoleOutputReporter>
<disable>true</disable>
</consoleOutputReporter>
<statelessTestsetInfoReporter
implementation="org.apache.maven.plugin.surefire.extensions.junit5.JUnit5StatelessTestsetInfoTreeReporterUnicode">
</statelessTestsetInfoReporter>
</configuration>
</plugin>
Related
#ptrthomas
I am also facing issue of "Exception in thread "main" java.lang.StackOverflowError"
https://github.com/intuit/karate/issues/661
According to you,this has been fixed in version '1.0.0' in develop branch.
I am not able to create the jar from develop branch (As I am following these steps:-https://github.com/intuit/karate/wiki/Developer-Guide)
Please push this fix to master and release the new version or tell me how to create jar.
What I did is:-
git clone https://github.com/intuit/karate.git
cd karate
git checkout develop
mvn clean install -P pre-release
After this I am getting this error:-
10:53:42.068 [main] DEBUG com.intuit.karate.XmlUtilsTest - map: {env:Envelope={_={env:Header=null, env:Body={_={QueryUsageBalanceResponse={_={Balance=null, Result={Success=null, Error={Category=DAT, Code=DAT_USAGE_1003, Description=Invalid Request: Invalid Input criteria: No asset found for license/eoc (630289335971198/855939)., Source=SIEBEL}}}, #={xmlns=http://www.intuit.com/iep/ServiceUsage/IntuitServiceUsageABO/V1}}}, #={xmlns=http://www.intuit.com/iep/ServiceUsage/IntuitServiceUsageABO/V1}}}, #={xmlns:S=http://schemas.xmlsoap.org/soap/envelope/, xmlns:env=http://schemas.xmlsoap.org/soap/envelope/}}}
[INFO] Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.065 s - in com.intuit.karate.XmlUtilsTest
[INFO]
[INFO] Results:
[INFO]
[ERROR] Failures:
[ERROR] RunnerTest.testRunningFeatureFromJavaApi:92 expected:<someValue> but was:<null>
[ERROR] RunnerTest.testRunningRelativePathFeatureFromJavaApi:100 expected:<someValue> but was:<null>
[ERROR]
ScriptTest.testFromJsKarateGetForJsonObjectVariableAndCallFeatureAndJs:1359
[ERROR] Errors:
[ERROR] ConfigTest.testSettingVariableViaKarateConfig:21 » Runtime javascript evaluati...
[INFO]
[ERROR] Tests run: 242, Failures: 3, Errors: 1, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] karate-parent ...................................... SUCCESS [ 0.342 s]
[INFO] karate-core ........................................ FAILURE [ 11.289 s]
[INFO] karate-apache ...................................... SKIPPED
[INFO] karate-junit4 ...................................... SKIPPED
[INFO] karate-junit5 ...................................... SKIPPED
[INFO] karate-netty ....................................... SKIPPED
[INFO] karate-gatling ..................................... SKIPPED
[INFO] karate-demo ........................................ SKIPPED
[INFO] karate-mock-servlet ................................ SKIPPED
[INFO] karate-jersey ...................................... SKIPPED
[INFO] karate-archetype ................................... SKIPPED
The CI build is green so it would help us if you find the root cause and let us know how to fix it.
For now please do this for step 4.
mvn clean install -P pre-release -DskipTests
We updated our Developer Kit and QA environment to product version 8.0.0.00-20170220-1900. We try to build the adapters and deploy the adapter to remote server using MFP CLI. But the deploy to server is failed with MAVEN plugin error.
Logs:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for metlife:NotificationsAdapter:adapter:1.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for com.ibm.mfp:adapter-maven-plugin is missing. # line 44, column 12
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building NotificationsAdapter 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- adapter-maven-plugin:8.0.2017021701:deploy (default-cli) # NotificationsAdapter ---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.824 s
[INFO] Finished at: 2017-03-28T12:36:16-04:00
[INFO] Final Memory: 10M/245M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.ibm.mfp:adapter-maven-plugin:8.0.2017021701:deploy (default-cli) on project NotificationsAdapter: Execution default-cli of goal com.ibm.mfp:adapter-maven-plugin:8.0.2017021701:deploy failed: A required class was missing while executing com.ibm.mfp:adapter-maven-plugin:8.0.2017021701:deploy: org/apache/commons/logging/LogFactory
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>com.ibm.mfp:adapter-maven-plugin:8.0.2017021701
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/var/root/.m2/repository/com/ibm/mfp/adapter-maven-plugin/8.0.2017021701/adapter-maven-plugin-8.0.2017021701.jar
[ERROR] urls[1] = file:/var/root/.m2/repository/org/apache/httpcomponents/httpclient-osgi/4.3.4/httpclient-osgi-4.3.4.jar
[ERROR] urls[2] = file:/var/root/.m2/repository/org/apache/httpcomponents/httpclient/4.3.4/httpclient-4.3.4.jar
[ERROR] urls[3] = file:/var/root/.m2/repository/org/apache/httpcomponents/httpcore/4.3.2/httpcore-4.3.2.jar
[ERROR] urls[4] = file:/var/root/.m2/repository/commons-codec/commons-codec/1.6/commons-codec-1.6.jar
[ERROR] urls[5] = file:/var/root/.m2/repository/org/apache/httpcomponents/httpmime/4.3.4/httpmime-4.3.4.jar
[ERROR] urls[6] = file:/var/root/.m2/repository/org/apache/httpcomponents/httpclient-cache/4.3.4/httpclient-cache-4.3.4.jar
[ERROR] urls[7] = file:/var/root/.m2/repository/org/apache/httpcomponents/fluent-hc/4.3.4/fluent-hc-4.3.4.jar
[ERROR] urls[8] = file:/var/root/.m2/repository/org/apache/httpcomponents/httpcore-osgi/4.3.2/httpcore-osgi-4.3.2.jar
[ERROR] urls[9] = file:/var/root/.m2/repository/org/apache/httpcomponents/httpcore-nio/4.3.2/httpcore-nio-4.3.2.jar
[ERROR] urls[10] = file:/var/root/.m2/repository/commons-logging/commons-logging/1.1.3/commons-logging-1.1.3.jar
[ERROR] urls[11] = file:/var/root/.m2/repository/javax/xml/jaxp-api/1.4.2/jaxp-api-1.4.2.jar
[ERROR] urls[12] = file:/var/root/.m2/repository/org/mozilla/rhino/1.7R4/rhino-1.7R4.jar
[ERROR] urls[13] = file:/var/root/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[project>metlife:NotificationsAdapter:1.0-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -----------------------------------------------------: org.apache.commons.logging.LogFactory
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContainerException
Error deploying adapter: NotificationsAdapter
If you can build successfully then Try to deploy manually from Operational Console.
From MFP Console try to deploy the adapter: your issue get fixed.
Try to change or add version detail (in-case missing) pom.xml as following. It resolved issue for me.
<build>
<plugins>
<plugin>
<groupId>com.ibm.mfp</groupId>
<artifactId>adapter-maven-plugin</artifactId>
<extensions>true</extensions>
<version>8.0.2020110500</version>
</plugin>
</plugins>
</build>
In my case it deploy using adapter-maven-plugin:8.0.2022030307:deploy and facing same error
[ERROR] Failed to execute goal com.ibm.mfp:adapter-maven-plugin:8.0.2022030307:deploy (default-cli) on project Project: Execution default-cli of goal com.ibm.mfp:adapter-maven-plugin:8.0.2022030307:deploy failed: A required class was missing while executing com.ibm.mfp:adapter-maven-plugin:8.0.2022030307:deploy: org/apache/commons/logging/LogFactory
I am trying to build my project in my local system using the below command
mvn clean install -Dmaven.test.skip=true
It fails with the below error. It is failing to connect to repo.maven.apache.org.
I pinged to the server repo.maven.apache.org, I can see the response back.
I am using maven 3 version and connecting to maven 2 repo (repo.maven.apache.org).
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building web-order-avpn 1702.0.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
Downloading: **https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.5/maven-clean-plugin-2.5.pom**
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 21.778 s
[INFO] Finished at: 2017-01-19T21:21:10-06:00
[INFO] Final Memory: 6M/15M
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its
dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.5:
Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.5 from/to central
(https://repo.maven.apache.org/maven2): Connect to repo.maven.apache.org:443 [repo.maven.apache.org/151.101.56.215] failed: Connection timed out: connect -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
Would be great if some one can suggest on what is wrong with my system?
I had this same issue and just like the comments suggested it was the maven proxy. Setup in \conf\settings.xml
http://maven.apache.org/guides/mini/guide-proxies.html
I was having problems getting my first service to run and decided to add the hello-api and hello-impl projects from the lagom Maven archtype project to see if it would work. It did but mine do not.
Background
Since other team members are pure Java developers, I was trying to avoid leveraging sbt and activator. Thus, the objective is that everything works in maven.
Here's a snippet of the 'mvn install' script output to show the other services built.
$ mvn install
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Archetype - mai-svcs
[INFO] mai-svc-common
[INFO] mai-actors-api <======= WANT THE SERVICE FOR THIS ONE TO RUN
[INFO] mai-namespace-api
[INFO] mai-actors-impl
[INFO] mai-namespace-impl
[INFO] mai-i18n-phrases-api
[INFO] hello-api
[INFO] hello-impl
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Archetype - mai-svcs 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Archetype - mai-svcs ............................... SUCCESS [ 2.774 s]
[INFO] mai-svc-common ..................................... SUCCESS [ 7.190 s]
[INFO] mai-actors-api ..................................... SUCCESS [ 24.706 s]
[INFO] mai-namespace-api .................................. SUCCESS [ 12.628 s]
[INFO] mai-actors-impl .................................... SUCCESS [ 29.061 s]
[INFO] mai-namespace-impl ................................. SUCCESS [ 21.294 s]
[INFO] mai-i18n-phrases-api ............................... SUCCESS [ 22.091 s]
[INFO] hello-api .......................................... SUCCESS [ 3.546 s]
NOTES: An MAIActorsModule class analogous to the HelloModule class was created and the application.conf file added in the src/main/resources folder.
When the command 'mvn lagom:runAll' is issued, initially, the services are the hello service port is logged but no other service's port is.
$ mvn lagom:runAll
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Archetype - mai-svcs
[INFO] mai-svc-common
[INFO] mai-actors-api
[INFO] mai-namespace-api
[INFO] mai-actors-impl
[INFO] mai-namespace-impl
[INFO] mai-i18n-phrases-api
[INFO] hello-api
[INFO] hello-impl
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Archetype - mai-svcs 0.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- lagom-maven-plugin:1.2.1:runAll (default-cli) # mai-svcs ---
[INFO] Starting Kafka
[INFO] Starting Cassandra
.[INFO] Did not find Netty's native epoll transport in the classpath, defaulting to NIO.
....[INFO] Using data-center name 'datacenter1' for DCAwareRoundRobinPolicy (if this is incorrect, please provide the correct datacenter name with DCAwareRoundRobinPolicy constructor)
[INFO] New Cassandra host /127.0.0.1:4000 added
[INFO] Cassandra server running at 127.0.0.1:4000
[INFO] Service locator is running at http://localhost:8000
[INFO] Service gateway is running at http://localhost:9000
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory C:\Users\lusp\mai_svcs\mai-svcs\hello-api\src\main\resources
[INFO] Nothing to compile - all classes are up to date
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 1 resource
**[INFO] Nothing to compile - all classes are up to date
[INFO] Service hello-impl listening for HTTP on 0:0:0:0:0:0:0:0:57797
// ----- NO ENTRY FOR mai-actors-impl!!! -----
[INFO] (Service started, press enter to stop and go back to the console...)**
What step(s) did I miss?
Each of your <service>-impl projects need to:
Invoke the lagom-maven-plugin
Configure it with the property <lagomService>true</lagomService>
Here's an example snippet of what you need to add to your pom.xml file in each service implementation project:
<build>
<plugins>
<plugin>
<groupId>com.lightbend.lagom</groupId>
<artifactId>lagom-maven-plugin</artifactId>
<configuration>
<lagomService>true</lagomService>
</configuration>
</plugin>
</plugins>
</build>
The Lagom documentation has more details in the page titled Defining a Lagom build
I've got an TestNG project which was running on Jenkins. For some reason which I don't know it stopped running the tests. It compiles perfectly but it doesn't run the the test. Here is the output of a run:
<===[JENKINS REMOTING CAPACITY]===>channel started
log4j:WARN No appenders could be found for logger
(org.apache.commons.beanutils.converters.BooleanConverter).
log4j:WARN Please initialize the log4j system properly.
Executing Maven: -B -f C:\Java\jenkins-1.523\workspace\TEST_HEAD_NOEXPORT\CMS-WEB SELENIUM-WEB-TEST\pom.xml clean install
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building TEST-CMS-WEB 0.0.1
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) # Web ---
[INFO]
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) # Web ---
[debug] execute contextualize
[INFO] Using 'cp1252' encoding to copy filtered resources.
[INFO] Copying 69 resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) # Web ---
[INFO] Compiling 73 source files to C:\Java\jenkins-1.523\workspace\TEST_HEAD_NOEXPORT\CMS-WEB\SELENIUM-WEB-TEST\target\classes
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) # Web ---
[debug] execute contextualize
[INFO] Using 'cp1252' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory C:\Java\jenkins-1.523\workspace\TEST_HEAD_NOEXPORT\CMS-WEB\SELENIUM-WEB-TEST\src\test\resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) # Web ---
[INFO] Compiling 2 source files to C:\Java\jenkins-1.523\workspace\TEST_HEAD_NOEXPORT\CMS-WEB\SELENIUM-WEB-TEST\target\test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) # Web ---
[JENKINS] Recording test results
[INFO]
[INFO] --- maven-jar-plugin:2.3.2:jar (default-jar) # Web ---
[INFO] Building jar: C:\Java\jenkins-1.523\workspace\TEST_HEAD_NOEXPORT\CMS-WEB\SELENIUM-WEB-TEST\target\Web-0.0.1.jar
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) # Web ---
[INFO] Installing C:\Java\jenkins-1.523\workspace\TEST_HEAD_NOEXPORT\CMS-WEB\SELENIUM-WEB-TEST\target\Web-0.0.1.jar to C:\.m2\repository\Test\Web\0.0.1\Web-0.0.1.jar
[INFO] Installing C:\Java\jenkins-1.523\workspace\TEST_HEAD_NOEXPORT\CMS-WEB\SELENIUM-WEB-TEST\pom.xml to C:\.m2\repository\Test\Web\0.0.1\Web-0.0.1.pom
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.211s
[INFO] Finished at: Wed Jan 15 14:21:03 UYST 2014
[INFO] Final Memory: 26M/310M
[INFO] ------------------------------------------------------------------------
[JENKINS] Archiving C:\Java\jenkins-1.523\workspace\TEST_HEAD_NOEXPORT\CMS-WEB\SELENIUM-WEB-TEST\pom.xml to C:\Java\jenkins-1.523\jobs\TEST_HEAD_NOEXPORT\modules\Test$Web\builds\2014-01-15_14-20-56\archive\Test\Web\0.0.1\Web-0.0.1.pom
[JENKINS] Archiving C:\Java\jenkins-1.523\workspace\TEST_HEAD_NOEXPORT\CMS-WEB\SELENIUM-WEB-TEST\target\Web-0.0.1.jar to C:\Java\jenkins-1.523\jobs\TEST_HEAD_NOEXPORT\modules\Test$Web\builds\2014-01-15_14-20-56\archive\Test\Web\0.0.1\Web-0.0.1.jar
Waiting for Jenkins to finish collecting data
If anyone knows what could be happening I would appreciate the help.
If your using Maven Surefire, did you correctly specify a "test include" filter? The test phase will search the packages in src/test/java for classes containing the #Test annotation. It's easy to misconfigure Maven for the location of the src/test/java directory and so just be careful and you will figure it out.
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>3.0.0-M3</version>
<configuration>
<suiteXmlFiles>
<suiteXmlFile>testng.xml</suiteXmlFile>
</suiteXmlFiles>
</configuration>
</plugin>
</plugins>
</build>
<dependencies>
Include maven surefire plugin end of the properties & before the dependencies. Use your "TestNG" XML file name.Use above code.