Yes, this was an issue and is now solved - here is the new code:
http://www.nabble.com/file/p17870603/CamelTest.java CamelTest.java
When using the multi threaded feature of TestNG (pom.xml)
(...)
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<groups>unit,performance</groups>
<parallel>methods</parallel>
<threadCount>1</threadCount>
</configuration>
</plugin>
(...)
If <threadCount/> is greater than 1 (multiple threads one per each test
method, executing in parallel) the test again fails occasionally.. The only
shared component across those two methods are Camel classes.
Apologies if I am posting in the wrong group...
James.Strachan wrote:
>
> 2008/6/16 jmfj <[EMAIL PROTECTED]>:
>>
>> Yes, dead on -- worked for single threaded tests - however, should
>> testOne()
>> and testTwo() affect each other if executed on separate threads?
>
> Sorry I mean is the bug in the test case - namely ExceptionThrower not
> being thread safe?
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
>
--
View this message in context:
http://www.nabble.com/Unit-Test---Non-Deterministic-Results-tp17867803s22882p17870603.html
Sent from the Camel - Development mailing list archive at Nabble.com.
