No testrun found for build id
Hello,
I almost have all the pieces together for test automation.
I could use some help finishing up.
This part looks right:
[DtSetTestInformation] Setting Test Information for ACBS-PHX: Version 1.0.0.2014-06-18_02-21-52 Milestone 1 on agent group UI-WS-NG [echo] Set Test Information with status : true
Then my JMeter runs with a server agent listening and I collect pure paths.
Waiting for 10 more seconds to get test run info ID from dynaTrace... 5 try out of 6 Fetching XML Report from server No testrun found for build id 2014-06-18_02-21-52 No test run recorded by the configured dynaTrace server - skipping data collection Finished: SUCCESS
My best guess is that the starting "1.0.0.2014-06-18_02-21-52" doesn't match up with the ending "2014-06-18_02-21-52"
but I couldn't find that data in the pure path anywhere.
Full log is below.
Thanks,'
--Erik
Started by user [8mha:AAAAlh+LCAAAAAAAAP9b85aBtbiIQTGjNKU4P08vOT+vOD8nVc83PyU1x6OyILUoJzMv2y+/JJUBAhiZGBgqihhk0NSjKDWzXb3RdlLBUSYGJk8GtpzUvPSSDB8G5tKinBIGIZ+sxLJE/ZzEvHT94JKizLx0a6BxUmjGOUNodHsLgAzOEgYu/dLi1CL9vNKcHACFIKlWvwAAAA==[0manonymous Building in workspace C:\Program Files (x86)\Jenkins\jobs\DynaTraceTestAutomation\workspace [jmeter] $ cmd.exe /C '"ant.bat -file build2.xml -DetoBuildId=2014-06-18_02-21-52 SetTestInformationForTestAutomation && exit %%ERRORLEVEL%%"' Buildfile: C:\Progra~2\Jenkins\jobs\DynaTraceTestAutomation\workspace\target\jmeter\build2.xml
[8mha:AAAAYB+LCAAAAAAAAP9b85aBtbiIQT6jNKU4P0+vJLE4u1gvPjGvRM8xryQksSg9tcQvvyTVvqNr/s+Vl9uYGBgqihikoKqT8/OK83NS9ZwhNEghAwQwghQWAADROOumXQAAAA==[0mSetTestInformationForTestAutomation: [DtSetTestInformation] Setting Test Information for ACBS-PHX: Version 1.0.0.2014-06-18_02-21-52 Milestone 1 on agent group UI-WS-NG [echo] Set Test Information with status : true
[8mha:AAAAYB+LCAAAAAAAAP9b85aBtbiIQSGjNKU4P0+vJLE4u1gvPjGvRM8xr8S/tCQ5PzfVL78ktUuDM0uMry+HiYGhoohBCqo8OT+vOD8nVc8ZQoMUMkAAI0hhAQAUXUdTXgAAAA==[0mBUILD SUCCESSFUL Total time: 0 seconds [workspace] $ C:\Progra~2\maven\apache-maven-3.1.1\bin\mvn.bat verify [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building DynaTraceTestAutomation 1.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [8mha:AAAAYB+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEGvvmZ+X75ZekLlOVfvTjc8FPJgaGiiIGKaiG5Py84vycVD1nCA1SyAABjCCFBQCV27OjYAAAAA==[0m[INFO] --- tomcat7-maven-plugin:2.0:exec-war-only (tomcat-run) @ JMeterTest --- [INFO] [8mha:AAAAYB+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEGvvmZ+X75ZekLlOVfvTjc8FPJgaGiiIGKaiG5Py84vycVD1nCA1SyAABjCCFBQCV27OjYAAAAA==[0m[INFO] --- jmeter-maven-plugin:1.9.0:jmeter (jmeter-tests) @ JMeterTest --- [INFO] [INFO] ------------------------------------------------------- [INFO] P E R F O R M A N C E T E S T S [INFO] ------------------------------------------------------- [INFO] [INFO] [info] [debug] JMeter is called with the following command line arguments: -n -t C:\Program Files (x86)\Jenkins\jobs\DynaTraceTestAutomation\workspace\src\test\jmeter\WebLinkHTTPRequestDefaults.jmx -l C:\Program Files (x86)\Jenkins\jobs\DynaTraceTestAutomation\workspace\target\jmeter\results\WebLinkHTTPRequestDefaults.jtl -d C:\Program Files (x86)\Jenkins\jobs\DynaTraceTestAutomation\workspace\target\jmeter -j C:\Program Files (x86)\Jenkins\jobs\DynaTraceTestAutomation\workspace\target\jmeter\logs\WebLinkHTTPRequestDefaults.jmx.log [info] Executing test: WebLinkHTTPRequestDefaults.jmx [info] Completed Test: WebLinkHTTPRequestDefaults.jmx [INFO] [INFO] Test Results: [INFO] [INFO] Tests Run: 1, Failures: 0 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2:37.049s [INFO] Finished at: Wed Jun 18 02:24:34 PDT 2014 [INFO] Final Memory: 18M/162M [INFO] ------------------------------------------------------------------------ Sleeping for the configured delay of 10sec Verify connection to dynaTrace Server REST interface ... Connection successful, getting testruninfo for this build (2014-06-18_02-21-52) Fetching XML Report from server No testrun found for build id 2014-06-18_02-21-52 Waiting for 10 more seconds to get test run info ID from dynaTrace... 0 try out of 6 Fetching XML Report from server No testrun found for build id 2014-06-18_02-21-52 Waiting for 10 more seconds to get test run info ID from dynaTrace... 1 try out of 6 Fetching XML Report from server No testrun found for build id 2014-06-18_02-21-52 Waiting for 10 more seconds to get test run info ID from dynaTrace... 2 try out of 6 Fetching XML Report from server No testrun found for build id 2014-06-18_02-21-52 Waiting for 10 more seconds to get test run info ID from dynaTrace... 3 try out of 6 Fetching XML Report from server No testrun found for build id 2014-06-18_02-21-52 Waiting for 10 more seconds to get test run info ID from dynaTrace... 4 try out of 6 Fetching XML Report from server No testrun found for build id 2014-06-18_02-21-52 Waiting for 10 more seconds to get test run info ID from dynaTrace... 5 try out of 6 Fetching XML Report from server No testrun found for build id 2014-06-18_02-21-52 No test run recorded by the configured dynaTrace server - skipping data collection Finished: SUCCESS
Hi Erik,
I had the same problem a little while ago, this is the part of the Test Automation Plugin for Jenkins page I missed:
| In the build that is executed, the DtSetTestInformation call to the dynaTrace Server has set the BUILD_ID provided by Jenkins as the build number. |
|---|
So essentially I needed to make this change to my Ant task:
<DtSetTestInformation ... versionBuild="${BUILD_ID}" ... </DtSetTestInformation> |
|---|
Hope that helps,
Rick B
Thanks for the quick reply, but I think I have that part in place.
SetTestInformationForTestAutomation: [DtSetTestInformation] Setting Test Information for ACBS-PHX: Version 1.0.0.2014-06-18_06-08-03 Milestone 1 on agent group UI-WS-NG [echo] Set Test Information with status : true
In the above output, my BUILD_ID is there, and it is prefixed with "1.0.0."
Is that ok? Could someone check to see if their BUILD_ID has this same prefix?
Thanks,
--Erik
Hi Erik,
The 1.0.0 is the versionMajor/versionMinor/versionRevision field to the DtSetTestInformation call (would be somewhere in the pom.xml). It shouldn't affect the BUILD_ID though - please verify, as Rick said, if you're able to see the build ID on data points in the test automation dashlet
Thanks
Wolfgang
No, I cannot see data in the test automation dashlet, but there is plenty of recent data in "Tagged web requests" and pure paths, etc...
I don't see any licensing errors, but I'm using Test Center Edition, Agent Version: 5.6.0.5802.
Jenkins is kicking off JMeter test with DT tags, and the dt data is collected by a java agent on the websphere server.
--Erik
Hi Erik,
That's why it's not working - the Jenkins plugin works off of the Test Automation dashlet data. You will need to follow the instructions in this tutorial, adding a dummy Unit test to initiate Test Automation and also adding the parameter category="load" to the dtsettestinformation task in Ant. After that the only other thing you might be missing is a saved dashboard with the Test Automation dashlet on it, referenced by the Jenkins plugin configuration.
Rick B
FYI - I just met Erik here at PERFORM DAY Atlanta and will sit down with him to discuss his open Test Automation Questions. Will update the forum with our findings
We just had a conversation. The challenge here is that Erik uses JMeter tests where we wants individual Web Requests executed by JMeter analyzed similar to what we do with Unit Tests. Right now the Test Automation Dashlet only supports Unit Tests as well as Browser-driven tests where the Test Automation Dashlet automatically analysis metrics such as DB Count, Exception Count, ...
We have an RFE we are working on to also do this for individual "Web Unit Test PurePaths" executed by JMeter. This is not available in the moment though
We have however discussed a strategy to get these metrics out of dynaTrace for every test Erik runs in their automation environment. Here is a little writeup of the steps to get performance data such as #SQL, #Exceptions, out of dynaTrace for every executed JMeter test.
The global idea is to
a) Create a Dashboard that contains the dashlets you are interested in, e.g: Tagged Web Requests, Database, Exceptions
b) Save that Dashboard on the dT Server, e.g: “JMeterResults”
c) After you run your load test you execute the REST Call to query that dashboard for a specific test you just executed. On the REST URL you can specify the Dashboard (e.g: JMeterResult) as well as the Filter for a particular Test Name (e.g: YourLoginTest)
Here are more links to the community
- Querying Dashboards: https://community.compuwareapm.com/community/display/DOCDT56/Server-+and+Clientside+XML+Reporting#Server-andClientsideXMLReporting-TheRequestInterface
- Filter Options for REST Interface: https://community.compuwareapm.com/community/display/DOCDT56/REST+Filters
Hope this helps
Getting "Load Tests" it into the Test Automation Dashlet is really just a shortcut to open the Load Testing Dashboard when double clicking on it. Right now we do not calculate metrics for Load Tests therefore the only advantage you get is that you have your load test listed there.
As mentioned - we want to improve our capabilities to also calculate measures for HTTP based testing
