jmeter-maven-plugin 1.4.1 reports with 1.6.0 and jmeter-analysis-maven-plugin 1.0.0
nano_nate
I do have several questions about this new release of the jmeter-maven-plugin and the jmeter-analysis-maven-plugin.
1) jmeter-analysis-maven-plugin 1.0.0 seems to create the reports at the "/target" directory, no mater what address I do set to the <target> tag. I'm using <target>${project.build.directory}/jmeter/upload/</target>, but it always the reports at <target>${project.build.directory}</target> no mater what I write
2) Big problem for me. jmeter-maven-plugin 1.4.1 used to build the report according to the *.jmx name. So if I had for two *.jmx files (test_1.jmx and test_2.jmx) it would create two separate *.jtl files (test_1.jtl and test_2.jtl) and when generating the report it would do the very same thing, two *.html files (test_1.html and test_2.html) based on the *.jtl files that are present at the ../report/ directory.
The jmeter-analysis-maven-plugin 1.0.0 always does use "sumary" to name the reports, so when I have several *.jtl files, at ../reports, I have nothing but a sumary.html report at the end with the information of the last (alphabetical) test.
3) The kind of reporting that the jmeter-analysis-maven-plugin 1.0.0 generates is the statistics kind (response times and numbers). Is it possible to have the jmeter-maven-plugin 1.4.1 simple pass/fail format with this new plugin?
4) I'm a developer to, and I know how hard it is to document the tools as I develop them, but
I know the easiest thing would be to go back to the jmeter-maven-plugin 1.4.1, but the jmeter-maven-plugin 1.6.0 works better for me because of the jmeter version that it uses. So I'll appreciate any help with these 3 questions.
Regards,
Nate
nano_nate
Hi,
I do have several questions about this new release of the jmeter-maven-plugin and the jmeter-analysis-maven-plugin.
1) jmeter-analysis-maven-plugin 1.0.0 seems to create the reports at the "/target" directory, no mater what address I do set to the <target> tag. I'm using <target>${project.build.directory}/jmeter/upload/</target>, but it always the reports at <target>${project.build.directory}</target> no mater what I write
2) Big problem for me. jmeter-maven-plugin 1.4.1 used to build the report according to the *.jmx name. So if I had for two *.jmx files (test_1.jmx and test_2.jmx) it would create two separate *.jtl files (test_1.jtl and test_2.jtl) and when generating the report it would do the very same thing, two *.html files (test_1.html and test_2.html) based on the *.jtl files that are present at the ../report/ directory.
The jmeter-analysis-maven-plugin 1.0.0 always does use "sumary" to name the reports, so when I have several *.jtl files, at ../reports, I have nothing but a sumary.html report at the end with the information of the last (alphabetical) test.
3) The kind of reporting that the jmeter-analysis-maven-plugin 1.0.0 generates is the statistics kind (response times and numbers). Is it possible to have the jmeter-maven-plugin 1.4.1 simple pass/fail format with this new plugin?
4) I'm a developer to, and I know how hard it is to document the tools as I develop them, but I has been really hard to find information about how to use these plugins, so I'll appreciate if you can make a small guide at least with the tags that can be used to configure the plugins them selfs.
I know the easiest thing would be to go back to the jmeter-maven-plugin 1.4.1, but the jmeter-maven-plugin 1.6.0 works better for me because of the jmeter version that it uses. So I'll appreciate any help with these 4 questions.
Regards,
Nate
Mark Collin
I would agree that documentation is a bit too sparse at the moment. I think the best documentation we have for the jmeter-maven-plugin is accessed by doing:
mvn site:run
and then browsing to the documentation on http://localhost:8080
For the analysis plugin it is best to look at:
https://github.com/afranken/jmeter-analysis-maven-plugin
I know I’ve not really done anything on the jmeter maven plugin, or the jmeter analysis maven plugin, the past couple of months, but that is largely because we haven’t had any feedback saying things need to change.
The reasons that we took the old reporting functionality out is because:
1. It was very inefficient and it more than doubled the time taken to run a test.
2. It seemed more sensible to focus the JMeter maven plugin purely on running the tests, and then have an additional plugin to do the reporting. This way you can potentially add any reporting plugin to the mix rather than being forced to use the one we offered.
As to your questions, I’m not familiar with the Jmeter analysis maven plugin codebase at the moment so my answers below may not be totally accurate:
1. Sounds like a bug, we will need to investigate and fix that if it is.
2. Again sounds like a bug, we should be providing sensible names by default.
3. I think this is possible by using a custom freemarker template.
4. I agree we need to spend some time on this (hopefully the info at the start of the mail will be of some use)
--
You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/maven-jmeter-plugin-users/-/QLdlijdim2oJ.
To post to this group, send an email to maven-jmeter...@googlegroups.com.
To unsubscribe from this group, send email to maven-jmeter-plugi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
nano_nate
I'm moving forward with the FreeMarker templates. This question may not concern you but maybe you'll be able to help me a little bit with this.
I'm not an expert with FreeMarker, writing an template is not a big deal though, but I don't know how to read the data from the *.jtl file (i.e. <httpSample t="861" lt="860" ts="1343160490414" s="true" lb="login" rc="200" rm="OK" tn="ArmDisarm 1-1" dt="text" by="521"/>)... Any Ideas about this?
I figured out what was wrong with the target location for the reports, basically it is a wrong tag name at the documentation you provide. I've set the maven in debug mode and I found out this:
[DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?>
<configuration>
<generateCSVs default-value="true">false</generateCSVs>
<generateCharts default-value="true">false</generateCharts>
<maxSamples default-value="50000">${maxSamples}</maxSamples>
<source>/home/natanael/ucontrol/automation/trunk/rest-api-test/target/jmeter/results/*.jtl</source>
<targetDirectory default-value="${project.build.directory}">${targetDirectory}</targetDirectory>
<templateDirectory>/home/natanael/ucontrol/automation/trunk/rest-api-test/resources/</templateDirectory>
</configuration>
so basically the tag name should be <targetDirectory> instead of just <target> as it says at the documentation.
I don't see anything, so far, that can help me with the reports' names (summary.*). BUt I'll keep looking. What I can do so far is to use the ant plugin to cat the results into a single file and generate a massive report from it. Not that I like it but I don't have too many options.
Regards,
Nate.
To post to this group, send an email to maven-jmeter-plugin-users@googlegroups.com.
To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
Mark Collin
Could you raise the following as bugs at https://github.com/afranken/jmeter-analysis-maven-plugin/issues:
1. Tag is called <targetDirectory> not <target>
2. Report names not being set correctly.
The parser that is reading in the .jtl file is here:
Hopefully that will help you out a bit.
I’m going to need some time going through the code beore I can supply anything more concrete I’m afraid.
From: maven-jmeter...@googlegroups.com [mailto:maven-jmeter...@googlegroups.com] On Behalf Of nano_nate
Sent: 23 July 2012 22:15
To: maven-jmeter...@googlegroups.com
Subject: [jmeter-maven-plugin-users] Re: jmeter-maven-plugin 1.4.1 reports with 1.6.0 and jmeter-analysis-maven-plugin 1.0.0
Hi,
I do have several questions about this new release of the jmeter-maven-plugin and the jmeter-analysis-maven-plugin.
1) jmeter-analysis-maven-plugin 1.0.0 seems to create the reports at the "/target" directory, no mater what address I do set to the <target> tag. I'm using <target>${project.build.directory}/jmeter/upload/</target>, but it always the reports at <target>${project.build.directory}</target> no mater what I write
2) Big problem for me. jmeter-maven-plugin 1.4.1 used to build the report according to the *.jmx name. So if I had for two *.jmx files (test_1.jmx and test_2.jmx) it would create two separate *.jtl files (test_1.jtl and test_2.jtl) and when generating the report it would do the very same thing, two *.html files (test_1.html and test_2.html) based on the *.jtl files that are present at the ../report/ directory.
The jmeter-analysis-maven-plugin 1.0.0 always does use "sumary" to name the reports, so when I have several *.jtl files, at ../reports, I have nothing but a sumary.html report at the end with the information of the last (alphabetical) test.
3) The kind of reporting that the jmeter-analysis-maven-plugin 1.0.0 generates is the statistics kind (response times and numbers). Is it possible to have the jmeter-maven-plugin 1.4.1 simple pass/fail format with this new plugin?
4) I'm a developer to, and I know how hard it is to document the tools as I develop them, but I has been really hard to find information about how to use these plugins, so I'll appreciate if you can make a small guide at least with the tags that can be used to configure the plugins them selfs.
I know the easiest thing would be to go back to the jmeter-maven-plugin 1.4.1, but the jmeter-maven-plugin 1.6.0 works better for me because of the jmeter version that it uses. So I'll appreciate any help with these 4 questions.
Regards,
Nate
--
You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/maven-jmeter-plugin-users/-/QLdlijdim2oJ.
To post to this group, send an email to maven-jmeter...@googlegroups.com.
To unsubscribe from this group, send email to maven-jmeter-plugi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
--
You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/maven-jmeter-plugin-users/-/OIkd085w2QAJ.
To post to this group, send an email to maven-jmeter...@googlegroups.com.
To unsubscribe from this group, send email to maven-jmeter-plugi...@googlegroups.com.
Natanael Castro
I don't see this working for real... what's the main node's name that is set by the "engine" to be able accessing the data from the xml code? I'm trying with "testResults" and "httpSample" as it is explained at the parser info... nothing works
--
Natanael Castro Ortega.
(+506) 8342-0141
Natanael Castro
The thing is... I haven't been able to access the other nodes, where the data is stored. This because the names of the nodes doesn't seem to match with the tags at the xml file.
I'll keep looking on this. It does seems to be pretty simple, it is just that the information (node name standards) is not so clear.
Nate.
Arne Franken
2012/7/26 Natanael Castro <ncog...@gmail.com>
To post to this group, send an email to maven-jmeter-plugin-users@googlegroups.com.
To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
--
You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
To view this discussion on the web, visit https://groups.google.com/d/msg/maven-jmeter-plugin-users/-/OIkd085w2QAJ.
To post to this group, send an email to maven-jmeter-plugin-users@googlegroups.com.
To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
--
You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
To post to this group, send an email to maven-jmeter-plugin-users@googlegroups.com.
To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
--
Natanael Castro Ortega.
(+506) 8342-0141
Mark Collin
be available in our current dev snapshot which is available here:
https://oss.sonatype.org/content/repositories/snapshots/com/lazerycode/jmete
r/jmeter-analysis-maven-plugin/
If you can let us know if that fixes 1 and 2 for you that would be useful.
This is of course a snapshot and will change every time we check in new code
so probably isn't something to rely on in the long term.
>>>
>>> ** **
>>>
>>> **1. **Tag is called <targetDirectory> not <target>****
>>>
>>> **2. **Report names not being set correctly.****
>>>
>>> ** **
>>>
>>> The parser that is reading in the .jtl file is here:****
>>>
>>> ** **
>>>
>>>
>>> https://github.com/afranken/jmeter-analysis-maven-plugin/blob/master
>>> /src/main/java/com/lazerycode/jmeter/analyzer/parser/JMeterResultPar
>>> ser.java
>>> ****
>>>
>>> ** **
>>>
>>> Short
>>> Link<https://github.com/afranken/jmeter-analysis-maven-plugin/blob/m
>>> aster/src/main/java/com/lazerycode/jmeter/analyzer/parser/JMeterResu
>>> ltParser.java>
>>> ****
>>>
>>> ** **
>>>
>>> Hopefully that will help you out a bit.****
>>>
>>> ** **
>>> I’m going to need some time going through the code beore I can
>>>
>>> ** **
>>>
>>> ** **
>>>
>>> *From:* maven-jmeter...@googlegroups.com [mailto:
>>> maven-jmeter...@googlegroups.com] *On Behalf Of *nano_nate
>>> *Sent:* 24 July 2012 21:31
>>> *To:* maven-jmeter...@googlegroups.com
>>> *Subject:* Re: [jmeter-maven-plugin-users] Re: jmeter-maven-plugin
>>> 1.4.1 reports with 1.6.0 and jmeter-analysis-maven-plugin 1.0.0****
>>>
>>> ** **
>>> Thanks for the reply...
>>>
>>> I'm moving forward with the FreeMarker templates. This question may
>>> not concern you but maybe you'll be able to help me a little bit with
this.
>>>
>>> I'm not an expert with FreeMarker, writing an template is not a big
>>> deal though, but I don't know how to read the data from the *.jtl file
(i.e.
>>> <httpSample t="861" lt="860" ts="1343160490414" s="true" lb="login"
>>> rc="200" rm="OK" tn="ArmDisarm 1-1" dt="text" by="521"/>)... Any
>>> Ideas about this?
>>>
>>> I figured out what was wrong with the target location for the
>>> reports, basically it is a wrong tag name at the documentation you
>>> provide. I've set the maven in debug mode and I found out this:
>>>
>>> [DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?>
>>> <configuration>
>>> <generateCSVs default-value="true">false</generateCSVs>
>>> <generateCharts default-value="true">false</generateCharts>
>>> <maxSamples default-value="50000">${maxSamples}</maxSamples>
>>>
>>>
<source>/home/natanael/ucontrol/automation/trunk/rest-api-test/target/jmeter
/results/*.jtl</source>
>>> tDirectory>
>>>
>>> <templateDirectory>/home/natanael/ucontrol/automation/trunk/rest-api
>>> </configuration>
>>>
>>> so basically the tag name should be <targetDirectory> instead of
>>> just <target> as it says at the documentation.
>>>
>>> I don't see anything, so far, that can help me with the reports'
>>> names (summary.*). BUt I'll keep looking. What I can do so far is to
>>> use the ant plugin to cat the results into a single file and
>>> generate a massive report from it. Not that I like it but I don't have
too many options.
>>>
>>> Regards,
>>> Nate.
>>>
>>> I would agree that documentation is a bit too sparse at the moment.
>>> I think the best documentation we have for the jmeter-maven-plugin
>>>
>>> ****
>>>
>>> mvn site:run ****
>>>
>>> ****
>>>
>>> and then browsing to the documentation on http://localhost:8080****
>>>
>>> ****
>>>
>>> For the analysis plugin it is best to look at:****
>>>
>>> ****
>>>
>>> https://github.com/afranken/jmeter-analysis-maven-plugin****
>>>
>>> ****
>>> I know I’ve not really done anything on the jmeter maven plugin, or
>>> the jmeter analysis maven plugin, the past couple of months, but
>>> that is largely because we haven’t had any feedback saying things need
to change.
>>>
>>> ****
>>> The reasons that we took the old reporting functionality out is because:
>>>
>>> ****
>>> 1. It was very inefficient and it more than doubled the time
>>> 2. It seemed more sensible to focus the JMeter maven plugin
>>> purely on running the tests, and then have an additional plugin to
>>> do the reporting. This way you can potentially add any reporting
>>> plugin to the mix rather than being forced to use the one we
>>>
>>> ****
>>> As to your questions, I’m not familiar with the Jmeter analysis
>>> maven plugin codebase at the moment so my answers below may not be
>>> totally
>>>
>>> ****
>>> 1. Sounds like a bug, we will need to investigate and fix that if
>>> 2. Again sounds like a bug, we should be providing sensible names
>>>
>>> 3. I think this is possible by using a custom freemarker template=
Mark Collin
tag name in the code hasn't changed.
You received this message because you are subscribed to the Google Groups
"Maven JMeter Plugin Users" group.
To post to this group, send an email to
Natanael Castro
After a little work I was able to give it a try on the 1.0.1-SNAPSHOT to see if the report names match the *.jtl file names... it still generates a summary.html and summary.txt... with overwritten info
Mark Collin
The new code is passing all the tests which check that it uses the new
naming structure and it's working locally here and producing files in the
format summary.
Can you provide a log of the run?
-----Original Message-----
From: maven-jmeter...@googlegroups.com
[mailto:maven-jmeter...@googlegroups.com] On Behalf Of Natanael
Castro
Sent: 01 August 2012 18:50
To: maven-jmeter...@googlegroups.com
Subject: Re: [jmeter-maven-plugin-users] Re: jmeter-maven-plugin 1.4.1
reports with 1.6.0 and jmeter-analysis-maven-plugin 1.0.0
Hi,
if the report names match the *.jtl file names... it still generates a
summary.html and summary.txt... with overwritten info
2012/7/27 Mark Collin <mark....@lazeryattack.com>
> Well when I say fixes for 1 and 2, 2 is a documentation change really.
> The tag name in the code hasn't changed.
>
> -----Original Message-----
> From: maven-jmeter...@googlegroups.com
> [mailto:maven-jmeter...@googlegroups.com] On Behalf Of Mark
> Collin
> Sent: 27 July 2012 14:59
> To: maven-jmeter...@googlegroups.com
> Subject: RE: [jmeter-maven-plugin-users] Re: jmeter-maven-plugin 1.4.1
> reports with 1.6.0 and jmeter-analysis-maven-plugin 1.0.0
>
> I have checked in fixes for issue 1 and 2 that you raised, these fixes
> will be available in our current dev snapshot which is available here:
>
>
> https://oss.sonatype.org/content/repositories/snapshots/com/lazerycode
> /jmete
> r/jmeter-analysis-maven-plugin/
>
> If you can let us know if that fixes 1 and 2 for you that would be
Natanael Castro
mvn pre-site -f test-pom.xml
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building com.icontrol.automation.rest-api-test 1.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT:analyze (jmeter-report-generation) @ rest-api-test ---
[WARNING] The POM for org.springframework:org.springframework.core:jar:3.0.7.RELEASE is missing, no dependency information available
ThermostatFanMode
time: 20120801T154952-0600 - 20120801T154953-0600
total duration: 1
requests: 1
requests per second: 1
response duration (ms)
min: 620
average: 620
max: 620
standard deviation: 0
quantiles (ms)
10% 0
20% 0
30% 0
40% 0
50% 0
60% 0
70% 0
80% 0
90% 0
99% 0
99.9% 0
100.0% 620 (max. value)
response size (bytes)
total: 521
min: 521
average: 521
max: 521
standard deviation: 0
response status codes
200: 1 (50%)
401: 1 (50%)
--
You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
To post to this group, send an email to maven-jmeter...@googlegroups.com.
To unsubscribe from this group, send email to maven-jmeter-plugi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
Mark Collin
If you pass -X to your maven command line it will print debug information to the console as well, so something like:
mvn verify -X
(It will probably be quite a lot of output getting logged)
It would be useful to see the relevant part of your POM that configures the plugin as well so I can mirror it on my environment.
Mark Collin
Gone through this again this morning and I still get appropriately named files written to my <targetDirectory>.
It isn’t logging multiple summaries in the console, is that what you are looking at?
Here is a copy of the relevant section from my POM:
<plugin>
<groupId>com.lazerycode.jmeter</groupId>
<artifactId>jmeter-analysis-maven-plugin</artifactId>
<version>1.0.1-SNAPSHOT</version>
<executions>
<execution>
<phase>verify</phase>
<goals>
<goal>analyze</goal>
</goals>
<configuration>
<source>${project.build.directory}/jmeter/results/*</source>
<targetDirectory>${project.build.directory}/jmeter/reports</targetDirectory>
<generateCSVs>true</generateCSVs>
<generateCharts>true</generateCharts>
<processAllFilesFound>true</processAllFilesFound>
</configuration>
</execution>
</executions>
</plugin>
Mark Collin
Version 1.0.1 is now out (and in maven central), see:
https://groups.google.com/forum/?fromgroups#!topic/maven-jmeter-plugin-users/8wJ9BNudaY0
It should fix the problems you are seeing, however we have do have a cosmetic bug with console output that is still outstanding:
https://github.com/afranken/jmeter-analysis-maven-plugin/issues/3
Natanael Castro
The only considerable differences between your pom and mine are that you do have the graphs and cvs files been generated, I don't.
Then the thing that makes all the trouble, I think... This tag:
<processAllFilesFound>true</processAllFilesFound>
There's no mention of this before, at least as I remember...
Whith this tag and the graphs and cvs set to be generated, you're right, all the files are generated, but, the one that concerns me keeps been overwritten. I'm seeking for the HTML file that is generated unther the name "sumary.html" because I need to upload the reports based on the freemarker template that I'm building.
So yes, you got different graphs and cvs files, but only one overwritten html file.
Natanael Castro
mvn pre-site -f test-pom.xml -X
Apache Maven 3.0.4 (r1232337; 2012-01-17 02:44:56-0600)
Maven home: /home/natanael/apache-maven-3.0.4
Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.0.0-23-generic", arch: "amd64", family: "unix"
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from /home/natanael/apache-maven-3.0.4/conf/settings.xml
[DEBUG] Reading user settings from /home/natanael/.m2/settings.xml
[DEBUG] Using local repository at /home/natanael/.m2/repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for /home/natanael/.m2/repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project com.icontrol.automation:rest-api-test:pom:1.0.1-SNAPSHOT: (none)
[DEBUG] Looking up lifecyle mappings for packaging pom from ClassRealm[plexus.core, parent: null]
[DEBUG] === REACTOR BUILD PLAN ================================================
[DEBUG] Project: com.icontrol.automation:rest-api-test:pom:1.0.1-SNAPSHOT
[DEBUG] Tasks: [pre-site]
[DEBUG] Style: Regular
[DEBUG] =======================================================================
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building com.icontrol.automation.rest-api-test 1.0.1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[DEBUG] Could not find metadata org.apache.maven.plugins:maven-jar-plugin/maven-metadata.xml in local (/home/natanael/.m2/repository)
[DEBUG] Skipped remote update check for org.apache.maven.plugins:maven-jar-plugin/maven-metadata.xml, locally cached metadata up-to-date.
[DEBUG] Skipped remote update check for org.apache.maven.plugins:maven-jar-plugin/maven-metadata.xml, locally cached metadata up-to-date.
[DEBUG] Resolved plugin version for org.apache.maven.plugins:maven-jar-plugin to 2.4 from repository central (http://bamboo.test.ucontrol.com:8081/artifactory/repo, releases)
[DEBUG] Resolving plugin version for org.apache.maven.plugins:maven-war-plugin
[DEBUG] Could not find metadata org.apache.maven.plugins:maven-war-plugin/maven-metadata.xml in local (/home/natanael/.m2/repository)
[DEBUG] Skipped remote update check for org.apache.maven.plugins:maven-war-plugin/maven-metadata.xml, locally cached metadata up-to-date.
[DEBUG] Skipped remote update check for org.apache.maven.plugins:maven-war-plugin/maven-metadata.xml, locally cached metadata up-to-date.
[DEBUG] Resolved plugin version for org.apache.maven.plugins:maven-war-plugin to 2.2 from repository central (http://bamboo.test.ucontrol.com:8081/artifactory/repo, releases)
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[DEBUG] Could not find metadata com.lazerycode.jmeter:jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT/maven-metadata.xml in local (/home/natanael/.m2/repository)
[DEBUG] Skipped remote update check for com.lazerycode.jmeter:jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT/maven-metadata.xml, locally cached metadata up-to-date.
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN ================================================
[DEBUG] Project: com.icontrol.automation:rest-api-test:1.0.1-SNAPSHOT
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): []
[DEBUG] Repositories (dependencies): [bootstrap (http://bamboo.test.ucontrol.com:8081/artifactory/repo, releases), central (http://bamboo.test.ucontrol.com:8081/artifactory/repo, releases), snapshots (http://bamboo.test.ucontrol.com:8081/artifactory/repo, snapshots)]
[DEBUG] Repositories (plugins) : [central (http://bamboo.test.ucontrol.com:8081/artifactory/repo, releases), snapshots (http://bamboo.test.ucontrol.com:8081/artifactory/repo, snapshots)]
[DEBUG] -----------------------------------------------------------------------
[DEBUG] Goal: com.lazerycode.jmeter:jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT:analyze (jmeter-report-generation)
[DEBUG] Style: Regular
[DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?>
<configuration>
<generateCharts default-value="true">true</generateCharts>
<maxSamples default-value="50000">${maxSamples}</maxSamples>
<source>/home/natanael/ucontrol/automation/trunk/rest-api-test/target/jmeter/results/*.jtl</source>
<targetDirectory default-value="${project.build.directory}">/home/natanael/ucontrol/automation/trunk/rest-api-test/target/jmeter/upload/</targetDirectory>
</configuration>
[DEBUG] =======================================================================
[INFO]
[INFO] --- jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT:analyze (jmeter-report-generation) @ rest-api-test ---
[DEBUG] Importing foreign packages into class realm maven.api
[DEBUG] Imported: org.apache.maven.wagon.events < plexus.core
[DEBUG] Imported: org.sonatype.aether.transfer < plexus.core
[DEBUG] Imported: org.apache.maven.exception < plexus.core
[DEBUG] Imported: org.sonatype.aether.metadata < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.Xpp3Dom < plexus.core
[DEBUG] Imported: org.sonatype.aether.collection < plexus.core
[DEBUG] Imported: org.sonatype.aether.version < plexus.core
[DEBUG] Imported: org.apache.maven.monitor < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.repository < plexus.core
[DEBUG] Imported: org.apache.maven.repository < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.resource < plexus.core
[DEBUG] Imported: org.codehaus.plexus.logging < plexus.core
[DEBUG] Imported: org.apache.maven.profiles < plexus.core
[DEBUG] Imported: org.sonatype.aether.repository < plexus.core
[DEBUG] Imported: org.apache.maven.classrealm < plexus.core
[DEBUG] Imported: org.apache.maven.execution < plexus.core
[DEBUG] Imported: org.sonatype.aether.artifact < plexus.core
[DEBUG] Imported: org.sonatype.aether.spi < plexus.core
[DEBUG] Imported: org.apache.maven.reporting < plexus.core
[DEBUG] Imported: org.apache.maven.usability < plexus.core
[DEBUG] Imported: org.codehaus.plexus.container < plexus.core
[DEBUG] Imported: org.codehaus.plexus.component < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlSerializer < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authentication < plexus.core
[DEBUG] Imported: org.apache.maven.lifecycle < plexus.core
[DEBUG] Imported: org.codehaus.plexus.classworlds < plexus.core
[DEBUG] Imported: org.sonatype.aether.graph < plexus.core
[DEBUG] Imported: org.sonatype.aether.* < plexus.core
[DEBUG] Imported: org.apache.maven.settings < plexus.core
[DEBUG] Imported: org.codehaus.classworlds < plexus.core
[DEBUG] Imported: org.sonatype.aether.impl < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.* < plexus.core
[DEBUG] Imported: org.apache.maven.toolchain < plexus.core
[DEBUG] Imported: org.sonatype.aether.deployment < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.observers < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParserException < plexus.core
[DEBUG] Imported: org.codehaus.plexus.util.xml.pull.XmlPullParser < plexus.core
[DEBUG] Imported: org.apache.maven.configuration < plexus.core
[DEBUG] Imported: org.apache.maven.cli < plexus.core
[DEBUG] Imported: org.sonatype.aether.installation < plexus.core
[DEBUG] Imported: org.codehaus.plexus.context < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.authorization < plexus.core
[DEBUG] Imported: org.apache.maven.project < plexus.core
[DEBUG] Imported: org.apache.maven.rtinfo < plexus.core
[DEBUG] Imported: org.codehaus.plexus.lifecycle < plexus.core
[DEBUG] Imported: org.codehaus.plexus.configuration < plexus.core
[DEBUG] Imported: org.apache.maven.artifact < plexus.core
[DEBUG] Imported: org.apache.maven.model < plexus.core
[DEBUG] Imported: org.apache.maven.* < plexus.core
[DEBUG] Imported: org.apache.maven.wagon.proxy < plexus.core
[DEBUG] Imported: org.sonatype.aether.resolution < plexus.core
[DEBUG] Imported: org.apache.maven.plugin < plexus.core
[DEBUG] Imported: org.codehaus.plexus.* < plexus.core
[DEBUG] Imported: org.codehaus.plexus.personality < plexus.core
[DEBUG] Populating class realm maven.api
[WARNING] The POM for org.springframework:org.springframework.core:jar:3.0.7.RELEASE is missing, no dependency information available
[DEBUG] org.freemarker:freemarker:jar:2.3.19:runtime
[DEBUG] org.jfree:jfreechart:jar:1.0.14:runtime
[DEBUG] org.jfree:jcommon:jar:1.0.17:runtime
[DEBUG] xml-apis:xml-apis:jar:1.3.04:runtime
[DEBUG] com.lowagie:itext:jar:2.1.5:runtime
[DEBUG] bouncycastle:bcmail-jdk14:jar:138:runtime
[DEBUG] bouncycastle:bcprov-jdk14:jar:138:runtime
[DEBUG] org.springframework:org.springframework.core:jar:3.0.7.RELEASE:runtime
[DEBUG] commons-logging:commons-logging:jar:1.1.1:runtime
[DEBUG] org.slf4j:slf4j-simple:jar:1.6.6:runtime
[DEBUG] org.slf4j:slf4j-api:jar:1.6.6:runtime
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.1:runtime
[DEBUG] Created new class realm plugin>com.lazerycode.jmeter:jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT
[DEBUG] Importing foreign packages into class realm plugin>com.lazerycode.jmeter:jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT
[DEBUG] Imported: < maven.api
[DEBUG] Populating class realm plugin>com.lazerycode.jmeter:jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT
[DEBUG] Included: com.lazerycode.jmeter:jmeter-analysis-maven-plugin:jar:1.0.1-SNAPSHOT
[DEBUG] Included: org.freemarker:freemarker:jar:2.3.19
[DEBUG] Included: org.jfree:jfreechart:jar:1.0.14
[DEBUG] Included: org.jfree:jcommon:jar:1.0.17
[DEBUG] Included: xml-apis:xml-apis:jar:1.3.04
[DEBUG] Included: com.lowagie:itext:jar:2.1.5
[DEBUG] Included: bouncycastle:bcmail-jdk14:jar:138
[DEBUG] Included: bouncycastle:bcprov-jdk14:jar:138
[DEBUG] Included: org.springframework:org.springframework.core:jar:3.0.7.RELEASE
[DEBUG] Included: commons-logging:commons-logging:jar:1.1.1
[DEBUG] Included: org.slf4j:slf4j-simple:jar:1.6.6
[DEBUG] Included: org.slf4j:slf4j-api:jar:1.6.6
[DEBUG] Included: org.codehaus.plexus:plexus-utils:jar:1.1
[DEBUG] Configuring mojo com.lazerycode.jmeter:jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT:analyze from plugin realm ClassRealm[plugin>com.lazerycode.jmeter:jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT, parent: sun.misc.Launcher$AppClassLoader@6d6f0472]
[DEBUG] Configuring mojo 'com.lazerycode.jmeter:jmeter-analysis-maven-plugin:1.0.1-SNAPSHOT:analyze' with basic configurator -->
[DEBUG] (f) generateCSVs = true
[DEBUG] (f) generateCharts = true
[DEBUG] (f) maxSamples = 50000
[DEBUG] (f) processAllFilesFound = true
[DEBUG] (f) source = /home/natanael/ucontrol/automation/trunk/rest-api-test/target/jmeter/results/*.jtl
[DEBUG] (f) targetDirectory = /home/natanael/ucontrol/automation/trunk/rest-api-test/target/jmeter/upload
[DEBUG] -- end configuration --
HistoryByDate
time: 20120803T170923-0600 - 20120803T170924-0600
total duration: 2
requests: 2
requests per second: 1
response duration (ms)
average: 527
max: 683
standard deviation: 155
quantiles (ms)
10% 0
20% 0
30% 0
40% 0
60% 372
70% 372
80% 372
90% 372
99% 372
99.9% 372
100.0% 683 (max. value)
response size (bytes)
total: 9986
min: 522
average: 4993
max: 9464
standard deviation: 4471
response status codes
200: 2 (66.67%)
400: 1 (33.33%)
Mark Collin
Have you tried the 1.0.1 final release I previously linked to?
The tag <processAllFilesFound>true</processAllFilesFound> is new for version 1.0.1 it did not exist before (in version 1.0.1 the plugin would only process one .jtl file as specified in <source> element. If multiple files were found it would only process the first one).
It looks like issue #3 is removing any useful output getting logged to the console so I can’t see the debug logging that shows the filename used for writing.
There should no longer be a summary.html generated. Assuming that the .jtl file that is being read in is called “foo.jtl”, it should be called “foo.html”.
It will probably be worth doing the following on the command line to clean out any old junk:
mvn clean pre-site -f test-pom.xml
Natanael Castro
I'm gonna keep working on the freemarker template.
Thanks for the help and good work with the plugin
Mark Collin
Good to hear you got it working J
Natanael Castro
In the report that I'm generating with the freemarker template I need to access some information that I can't see in the default report that you're generating, Things like the returning code from each step of the test.
Let's say for example that I do have this:
<httpSample t="920" lt="919" ts="1344292613878" s="true" lb="login" rc="200" rm="OK" tn="ArmDisarm 1-1" dt="text" by="521"/>
<httpSample t="697" lt="551" ts="1344292615469" s="true" lb="Intance id" rc="200" rm="OK" tn="ArmDisarm 1-1" dt="text" by="9452"/>
<httpSample t="340" lt="340" ts="1344292616351" s="true" lb="arm system" rc="202" rm="Accepted" tn="ArmDisarm 1-1" dt="text" by="273"/>
<httpSample t="332" lt="332" ts="1344292616923" s="true" lb="disarm system" rc="202" rm="Accepted" tn="ArmDisarm 1-1" dt="text" by="273"/>
How, using the freemarker, can I know that the returning code from the step called "instance id" was 200? and even further, how do I know that this sample is labeled as "instance id"?
Nate
Mark Collin
Sorry for the late response to this, I’ve not looked here for a couple of days.
All of the keys available are shown as comments at the top of aggregatedResponse.ftl:
<#-- @ftlvariable name="key" type="java.lang.String" -->
<#-- @ftlvariable name="aggregatedResponses" type="com.lazerycode.jmeter.analyzer.parser.AggregatedResponses" -->
<#-- @ftlvariable name="bytes" type="com.lazerycode.jmeter.analyzer.statistics.Samples" -->
<#-- @ftlvariable name="requests" type="com.lazerycode.jmeter.analyzer.statistics.Samples" -->
<#-- @ftlvariable name="Q_QUANTILES" type="java.lang.Integer" -->
<#-- @ftlvariable name="K_99_PERCENT" type="java.lang.Integer" -->
<#-- @ftlvariable name="K_99_PONT_9_PERCENT" type="java.lang.Integer" -->
<#-- @ftlvariable name="PERCENT_100" type="java.lang.Integer" -->
<#-- @ftlvariable name="CHARTS" type="java.lang.Boolean" -->
<#-- @ftlvariable name="DETAILS" type="java.lang.Boolean" -->
<#-- @ftlvariable name="SUMMARY_FILE_NAME" type="java.lang.String" -->
Looking through jMeterResultParser.java it would appear that the key element is either set to tn or lb, so I think ${key} would be the place to look for lb values.
Status codes are stored as part of ${aggregatedResponses} (code is here AggregatedResponses.java) so I think what you are looking for is ${aggregatedResponses.statusCodes.codes} which will be a list of status codes returned for a specific ${key}.
Hope that helps
pas...@gmail.com
I have a query (may be similar to the one which is raised below). Is it possible to get the result code for each test case, and if so can you guide me a little further on how to go ahead on this.
Thanks in advance.
Pranesh
Arne Franken
> To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
>
>
>
> --
> Natanael Castro Ortega.
> (+506) 8342-0141
> --
> You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
> To post to this group, send an email to maven-jmeter...@googlegroups.com.
> To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
>
>
> --
> You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
> To post to this group, send an email to maven-jmeter...@googlegroups.com.
> To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
>
>
>
> --
> Natanael Castro Ortega.
> (+506) 8342-0141
>
>
>
> --
> Natanael Castro Ortega.
> (+506) 8342-0141
> --
> You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
> To post to this group, send an email to maven-jmeter...@googlegroups.com.
> To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
>
>
> --
> You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
> To post to this group, send an email to maven-jmeter...@googlegroups.com.
> To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
>
>
>
> --
> Natanael Castro Ortega.
> (+506) 8342-0141
> --
> You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
> To post to this group, send an email to maven-jmeter...@googlegroups.com.
> To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
>
>
> --
> You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
> To post to this group, send an email to maven-jmeter...@googlegroups.com.
> To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/maven-jmeter-plugin-users?hl=en-GB.
>
>
>
> --
> Natanael Castro Ortega.
> (+506) 8342-0141
> --
> You received this message because you are subscribed to the Google Groups "Maven JMeter Plugin Users" group.
> To post to this group, send an email to maven-jmeter...@googlegroups.com.
> To unsubscribe from this group, send email to maven-jmeter-plugin-users+unsub...@googlegroups.com.
Ashrit Pranesh
A test case would mean "a HTTP request in a Thread group". When this request is executed in the JMeter, it returns with a response code and response message. Currently, the maven analysis plugin provides the summary of "Status Codes". If i have 5 requests, then it gives Status Codes 100% (5). I wanted the status code for each request and the corresponding response code.
I enabled generateCSV to true, but it does not give me the status codes.
Please provide your suggestions on this further.
Thanks,
Pranesh