[
http://jira.codehaus.org/browse/MOJO-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124923
]
soelvpil edited comment on MOJO-1030 at 2/25/08 2:56 AM:
---------------------------------------------------------------
New version with the following improvements:
1. Fixed problem with transitive dependencies when executing performancetests
with jmeter.
2. Fixed classpath problem with dependencies conflicting with
jmeterdependencies when executing performancetests with jmeter.
3. Fixed problem with saving history and validating performance in multimodule
builds.
4. Slight improvement of generated reports: When reponsetimes are shown for
individual tests, aggregated resposnetimes (throughout all tests) will not be
shown, since they are irrelevant.
Please download, ??mvn install?? and follow the guidelines ind the site
documentation!
was (Author: soelvpil):
New version with the following improvements:
1. Fixed problem with transitive dependencies when executing performancetests
with jmeter.
2. Fixed classpath problem with dependencies conflicting with
jmeterdependencies when executing performancetests with jmeter.
3. Fixed problem with saving history and validating performance in multimodule
builds.
4. Slight improvement of generated reports: When reponsetimes are shown for
individual tests, aggregated resposnetimes (throughout all tests) will not be
shown, since they are irrelevant.
Please download, <i>mvn install</i> and follow the guidelines ind the site
documentation!
> Chronos: A plugin for contiuous performancetesting
> --------------------------------------------------
>
> Key: MOJO-1030
> URL: http://jira.codehaus.org/browse/MOJO-1030
> Project: Mojo
> Issue Type: New Feature
> Components: Plugin Submission
> Reporter: Kent Soelvsten
> Attachments: chronos.zip, chronos.zip
>
>
> At my company, we have developed a Maven2 plugin which we use for "continuous
> performancetesting".
> We use it to integrate performancetesting in our nightly Maven builds.
> The tests are performed using JMeter (it is pluggable though, other tools
> could potentially be used). The tests can be either Junittests or HTTP
> requests.
> It is possible to validate whether performancetargets have been met and
> generate nice reports of the results. The content of the reports are highly
> configurable.
> A few reports are built in (responsetimes, histograms, throughput and garbage
> collections). Through a plugin mechanism it is possible to add additional
> graphs to the generated report (ideas could be CPU usage over time or the
> size of an application servers connectionpool).
> Example reports can be seen at
> http://www.sosi.dk/sosi/seal/jmeter-scalability-report.html
> http://www.sosi.dk/sosi/seal/jmeter-endurance-report.html
> http://www.sosi.dk/sosi/seal/jmeter-response-report.html
> It is also possible to generate historical reports, allowing the user to see
> how performance has changed over time, thus helping him to pinpoint when a
> problem has been introduced.
> The code is attached her with an MIT license.
> Generate the site documentation and have a look at the examples!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
