[
https://issues.apache.org/jira/browse/STREAMS-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15595612#comment-15595612
]
Steve Blackmon commented on STREAMS-424:
----------------------------------------
Execution time of tests is a big problem but that’s primarily IMO because
streams-runtime-local and streams-monitoring aren’t high quality and do a lot
of sleeping and catching exceptions before they terminate, and that slows down
test execution substantially.
I’m all for making tests finish faster, but i’m not sure they can all be run
parallel without forking and still pass.
The StreamsConfiguration and various component configurations are often made
available to the code via typesafe library / JVM properties - so what can
happen is if two tests use two different configurations, if they are in two
JVMs it’s all good but if they aren’t the test code has to get more complicated
to put their respective configuration under different jvm property namespaces.
Also the JMX beans used by streams-monitoring don't have any namespacing so
running two streams in the same JVM can cause problems.
That said, by all means let's try some different configuration, perhaps certain
modules can be made more parallel / faster.
> Add maven-surefire-plugin and modify POM to be able to run unit tests in
> parallel
> ---------------------------------------------------------------------------------
>
> Key: STREAMS-424
> URL: https://issues.apache.org/jira/browse/STREAMS-424
> Project: Streams
> Issue Type: Improvement
> Affects Versions: 0.3
> Reporter: Suneel Marthi
> Assignee: Suneel Marthi
> Fix For: 0.4
>
>
> Add maven-surefire-plugin and modify POM to be able to run unit tests in
> parallel. Presently the tests are run sequentially and the build takes a very
> long time to complete.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
