[
http://jira.amdatu.org/jira/browse/AMDATU-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11850#comment-11850
]
Bram de Kruijff commented on AMDATU-418:
----------------------------------------
After the Pax Exam upgrade I wrote a simple benchmark test as part of the
integration test module. Instead of actually spawning a Jmeter I am simply
using a threadpool to do basically the same thing. We are not doing remote
testing and do we really need all the Jmeter power to benchmark some core and
web mechanics?
{code}
amdatu-web\itest\tests> mvn -Dtest=BenchmarkTest
{code}
Pro's are:
* flexible provisioning instead op zip files
* flexible components instead of test artifacts
* integrated with build/surefire/junit/itest/bamboo
At this point I think we do not need the performance test framework in it's
current form as part of the platform and suggest to (re)move it.
WDYT?
> Restore performance test framework and implement platform tests
> ---------------------------------------------------------------
>
> Key: AMDATU-418
> URL: http://jira.amdatu.org/jira/browse/AMDATU-418
> Project: Amdatu
> Issue Type: Improvement
> Components: Amdatu Testing - Performance, Amdatu Web
> Affects Versions: 0.2.1
> Reporter: Bram de Kruijff
>
> The performance test framework hasn't been used in a while and currently
> fails at startup. Furthermore, it was designed to handle one big amdatu zip
> and there are no platform tests. This issue should cover getting the thing up
> and running and implementing some basic platform tests.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers