Not sure what do you mean by correct object is not getting passed. You would need to ensure that you build the synchronization between your classes.
TestNG provides you with the following methods to help you share data.
From within any test method, you can get access to both these objects via
Thanks & Regards
Krishnan Mahadevan
"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/
My Technical Scribbings @ http://rationaleemotions.wordpress.com/
--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.
To post to this group, send email to testng...@googlegroups.com.
Visit this group at https://groups.google.com/group/testng-users.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users+unsubscribe@googlegroups.com.
<
suite
name
=
"Suite"
parallel
=
"methods"
>
meantime will modify the design to try out your solution.
Thanks,
Vikram
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users+unsubscribe@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users+unsubscribe@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to testng-users+unsubscribe@googlegroups.com.
>>>> 3. I remember you were working on https://github.com/paypal/SeLion, does this framework takes care of distribution logic per your earlier answer ?
No. SeLion wouldn’t do it either. Please understand that you are talking about two different JVMs trying to co-ordinate on the number of threads.
There’s a JVM #1 which is created when you launch your tests. Here you can manage your thread pool etc., using a TestRunner such as TestNG.
There’s a JVM #2 which is a standalone jar running as Hub. The distribution logic (which is again dependent on the number of slots available in JVM #3 (node1), JVM #4(node2) and so on) cannot be controlled from JVM #1